VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: What do I do when I receive an abuse report from AWS about my resources?

AWS notified me that my account's resources were reported for abusive activity. What does this mean, and what do I need to do?Short descriptionThe AWS Trust & Safety Team sends abuse reports to the security contact on your account. If there is no security contact listed, then the AWS Trust & Safety Team contacts you using the email address listed on your account.If you require more information, reply to the email from the AWS Trust & Safety Team. The team will request additional information from the reporter.If you observe unauthorized activity, or if you believe that an unauthorized party has accessed your AWS account, see What do I do if I notice unauthorized activity in my AWS account? Make sure that your instances and applications are properly secured by following the shared responsibility model.You can use AWS services, such as Amazon GuardDuty and AWS Trusted Advisor, to help you identify opportunities to secure your resources.

ResolutionIf you receive an abuse notice from AWS, do the following:Review the abuse notice to see what content or activity was reported. Logs that implicate abuse are included along with the abuse report, as provided by the reporter.Reply directly to the abuse report and explain how you're preventing the abusive activity from recurring in the future.  Note: If you don't respond to an abuse notice within 24 hours, AWS might block your resources or suspend your AWS account.The AWS Trust & Safety Team doesn't provide technical support. If you need technical help and have a Developer or Business AWS Support plan, see How do I get technical support from AWS? For additional resources, see How do I get help with my AWS account and resources?Related informationHow do I report abuse of AWS resources?
Question: "I am unable to connect to an EC2 Windows instance using RDP and receive an error, "The remote session was disconnected because there are no Remote Desktop License Servers available." How can I resolve this?"

When connecting to an Amazon Elastic Compute Cloud (Amazon EC2) Windows instance using Remote Desktop Protocol (RDP), I receive this error message: "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator." How can I resolve this?ResolutionThe error indicates there is an issue with the Remote Desktop Services host settings on your Amazon EC2 Windows instance.If you don't need to run more than two concurrent RDP sessions, uninstall the Remote Desktop Service.Troubleshooting CALsIf you installed the Remote Desktop services host settings on your Amazon EC2 Windows instance to allow more than 2 concurrent RDP client sessions, then you must purchase Client Access Licenses (CALs). RDS provides a licensing grace period of 120 days. After the grace period expires, you must purchase CALs to allow more than two concurrent RDP user sessions.For assistance with purchasing and installing CALs, contact your VAR or Microsoft Partner.If you purchased CALs and receive the error, then the server might not be reachable by the instance that you're connecting to. For more information, see Cannot connect to RDS because no RD Licensing servers are available.Uninstall Remote Desktop ServicesOpen Remote Desktop client using below command and connect to the Windows server:mstsc /adminRun the following Windows PowerShell command as an administrator:Uninstall-WindowsFeature -name Remote-Desktop-Services -includemanagementtools -confirmReboot the machine.Note: If you still can't connect to a Windows instance using RDP, you might have to perform additional troubleshooting. For more information, see How do I troubleshoot Remote Desktop connection issues to my Amazon EC2 Windows instance?Related informationConnect to your Windows instanceCommand-line reference mstscRDP displays a black screen instead of the desktop
Question: My static website hosted on Amazon S3 and served through CloudFront is down. Why?

I'm using Amazon Simple Storage Service (Amazon S3) to host a static website, and I'm using Amazon CloudFront to serve the website. However, the website is down. How can I fix this?ResolutionBefore you begin, confirm the following:You have internet access.The origin domain name that's specified on your CloudFront distribution points to the correct S3 bucket with no typos or other errors.If you have internet access and the origin domain name is correct, then check the error response that you get from trying to access your website:403 Access Denied errorA 403 Access Denied error indicates that there's a permissions problem that's causing your website to appear down. For troubleshooting instructions, see I’m using an S3 website endpoint as the origin of my CloudFront distribution. Why am I getting 403 Access Denied errors?Important: Be sure to check the Block Public Access settings for your website's S3 bucket. These settings can block anonymous requests to your website. Block Public Access settings can apply to AWS accounts or individual buckets.404 Not Found errorA 404 Not Found error indicates that the request is pointing to a website object that doesn't exist. Check the following:Verify that the URL to the website object doesn't have any typos.Verify that the website object exists on the S3 bucket that's hosting your website. You can check the bucket using the Amazon S3 console. Or, you can run the list-objects command using the AWS Command Line Interface (AWS CLI).Internal errorIf the response indicates there's an internal error, then there might be an internal service issue that's affecting your website. Check the AWS Service Health Dashboard for possible issues.

Related informationWeb distribution diagnostic
Question: How do I use customer profiles in Amazon Connect?

In Amazon Connect, I want to start using customer profiles.

ResolutionTo start using customer profiles, it's a best practice to begin with the Amazon Connect customer profiles workshop.Frequently asked questionsHow do I see the customer profiles for a specific customer?You can see specific customer profiles by changing the instance URL for your Contact Control Panel (CCP) to replace ccp-v2 with agent-app-v2.For example, if your URL is instance-test.my.connect.aws, then the URLs look similar to the following:To access the CCP for calls, chats, and tasks, the URL is: https://instance-test.my.connect.aws/ccp-v2/To access the CCP for calls, chats, tasks, and to use customer profiles and the Voice ID feature, the URL is: https://instance-test.my.connect.aws/agent-app-v2/How do I know when a specific profile was created?When a profile is created, the CreateProfile API is logged in AWS CloudTrail. For more information, see Amazon Connect information in CloudTrail.Tip: You can configure an Amazon EventBridge rule to notify you when the CreateProfile API is logged. For more information, see Getting started with Amazon EventBridge.How do I associate, create, and update a customer profile during a call flow using a contact flow block?To change a customer profile during a call flow, use the Customer Profiles flow block. The Customer Profiles flow block lets you retrieve, update, and create a customer profile.How do I use a customer profiles contact flow block to validate an inbound call?You can create customer profiles to validate every inbound call using a customer's phone number. Use the customer's phone number from System Attributes to perform a profile search with the field _phone. Be sure to perform this search within the same block. If the search returns a profile, then you have validated that the customer's phone number is from an existing customer.How do I see custom attributes in the customer profile in the agent application?Custom attributes aren't visible in the agent application by default. To see custom attributes in the agent application, you must design a custom agent application panel.How can I run the Identity Resolution manually?You can use the JobSchedule API to schedule the Identity Resolution to run at a specific time.Troubleshooting the "Conflict executing request: Duplicate key" error messageThis error message occurs when configuring Amazon Simple Storage Service (Amazon S3) data mapping on your customer profile. This error happens because the CSV file isn't formatted correctly, such as when it contains empty columns or extra data.To resolve this error, make sure that there isn't extra data in the file when formatting the CSV. Refer to the sample CSV file for an example of the correct format.

Related informationActivate customer profiles for your instance
Question: How do I port my phone number that's not registered in the US or Canada (non +1 country code) in Amazon Connect?

I am trying to port my non-US (non +1 country code) numbers in Amazon Connect, but I am not sure how I can do this. How do I start the process for porting my numbers?ResolutionCreate a support case to port your telephone numbers into Amazon Connect. Submit the port request only when you are prepared to port the telephone number because it can be difficult to cancel or change the request after it has started.Note: This process is for phone numbers not registered in the US or Canada. For all other numbers, see How do I port my phone number registered in the US or Canada (+1 country code) in Amazon Connect?Include the following information when submitting your case to AWS Support:Telephone number, including all digits and any leading zerosNumber type (local/DID, toll-free, ITFS, UIFN, and so on)Country that the number is registered inName of the current carrierAccount number with current carrier, as well as any PIN or billing telephone number informationCopy of an invoice or bill with current carrier, with sensitive information redactedAmazon Connect target instance ARNExact name of the contact flow where the numbers must be mapped to after receiving porting approvalNote: Specifying the contact flow information allows AWS Support to map the number to a contact flow when adding the telephone number to the Amazon Connect instance. This helps to avoid downtime during the porting process.Preferred porting window timeframeNote: AWS Support will attempt to meet the window timeframe, but can't guarantee to meet it.After submitting the port request, it takes up to five business days to check telephone number portability with our carriers. If the number is portable, then AWS Support will reach out for more information.Note: AWS Support notifies you if there is a cost to port an international number before submitting the port to the current carrier.After AWS Support collects all additional information and completed forms from you, the information is submitted to our partner carrier. Then, the partner carrier submits the port request to the current carrier. If the current carrier accepts the request to port, they propose a porting date. This is known as the mutual acceptance of a port. Mutual port acceptance takes from five to fifteen business days to complete after all correct and completed forms are submitted. At this point, your preferred porting window timeframe is considered. The international number porting process varies by country, carrier, and local regulations. The porting process is completed on the scheduled date and time provided to you by AWS Support.AWS Support informs you when the process is complete and successful porting has been verified. It's best practice for you to test the ported numbers by placing test calls to make sure that the attached contact flow is initiated.
Question: How do I resolve the error "Timeout waiting for connection from pool" in Amazon EMR?

My Apache Hadoop job in Amazon EMR fails with the error message "Timeout waiting for connection from pool".

ResolutionThis error usually happens when you reach the Amazon EMR File System (EMRFS) connection limit for Amazon Simple Storage Service (Amazon S3). To resolve this error, increase the value of the fs.s3.maxConnections property. You can do this while your cluster is running or when you create a new cluster.1.    Connect to the master node using SSH.2.    Run the following command to open the emrfs-site.xml file as sudo. This file is located in the /usr/share/aws/emr/emrfs/conf directory.sudo vi /usr/share/aws/emr/emrfs/conf/emrfs-site.xml3.    Set the fs.s3.maxConnections property to a value above 50. In the following example, the value is set to 100. You might need to choose a higher value, depending on how many concurrent S3 connections that your applications need.Note: If you launch your cluster with Apache HBase, then the fs.s3.maxConnections value is set to 1000 by default. If increasing the fs.s3.maxConnections value doesn't resolve the timeout error, then check your applications for connection leaks.<property>  <name>fs.s3.maxConnections</name>  <value>100</value></property>4.    Repeat steps 2 and 3 on all core and task nodes. Use the same fs.s3.maxConnections value that you used on the master node.Note: With Amazon EMR version 5.21.0 and later, you can reconfigure cluster applications and specify additional configuration classifications for each instance group in a running cluster. For more information, see Reconfigure an instance group in a running cluster.5.    Run the Hadoop job again. Your application must use the new value for fs.s3.maxConnections without a service restart.To set the value of the fs.s3.maxConnections property on all nodes when you launch a new cluster, use a configuration object similar to the following. For more information, see Configure applications.[  {    "Classification": "emrfs-site",    "Properties": {      "fs.s3.maxConnections": "100"    }  }]Related informationWork with storage and file systems
Question: How can I troubleshoot "ERROR: null value in column violates not-null constraint" for my AWS DMS full load and CDC task?

I have an AWS Database Migration Service (AWS DMS) task that is both full load and change data capture (CDC). I received an error that says: "ERROR: null value in column violates not-null constraint." How do I resolve this issue?ResolutionIf you have large object (LOB) columns in your migration task, then you see a log entry similar to the following:MessagesE: Command failed to load data with exit error code 1, Command output: ERROR: null value in column ’xyz’ violates not-null constraintWhen AWS DMS migrates LOB columns, first all the data except for the LOB column is migrated into your target table, and AWS DMS inserts a NULL record in the LOB column. Then, AWS DMS updates the rows in the target table with the LOB column data.If the target isn't created by AWS DMS, check the target data description language (DDL) to see if a NOT NULL attribute is specified. If there is a NOT NULL attribute, alter the table to remove the NOT NULL constraint on LOB column datatypes. Then, resume your AWS DMS task.See the following table for AWS DMS task behavior for LOB modes and task phases:LOB ModeFull LoadChange Data CaptureFull LOB ModeNOT NULL constraint isn't allowedNOT NULL constraint isn't allowedLimited LOB ModeNULL constraint is allowedNOT NULL constraint isn't allowedRelated InformationMigrating Large Binary Objects (LOBs)
Question: How can I collect logs from the Windows instances in my Elastic Beanstalk environment?

I want to collect logs from the Windows instances in my AWS Elastic Beanstalk environment.

Short descriptionYou can use the AWSSupport-CollectElasticBeanstalkLogs automation to collect logs from the Windows instances in your Elastic Beanstalk environment. For Windows instances, you must collect logs one at a time by connecting to each individual Windows instance using the Remote Desktop Protocol (RDP). However, you can avoid this manual process by using the AWSSupport-CollectElasticBeanstalkLogs automation to collect logs from multiple Windows instances automatically.By default, the automation uploads the log bundles for your instances as .zip files to either of the following:The default Elastic Beanstalk bucket in the your accountAn Amazon Simple Storage Service (Amazon S3) bucket that you specifyThe automation collects log files from the following locations:C:\Program Files\Amazon\ElasticBeanstalk\HealthD\Logs\*C:\Program Files\Amazon\ElasticBeanstalk\logs\*C:\cfn\log\*C:\inetpub\logs\*Note: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent AWS CLI version.

ResolutionYou can run the automation using the AWS Systems Manager console or AWS CLI.Console:1.    Open the Systems Manager console.2.    On the navigation pane, in the Change Management section, choose Automation.3.    Choose Execute automation.4.    On the Owned by Amazon tab, search for and select the AWSSupport-CollectElasticBeanstalkLogs automation document, and then choose Next.5.    In the Input parameters section, enter the fields appropriate for your scenario.6.    Choose Execute.To monitor the progress of your automation:1.    On the navigation pane of the Systems Manager console, in the Change Management section, choose Automation.2.    From the Execution ID column, choose your automation.3.    Review the progress of your automation. The Execution steps section shows what stage the automation is currently in. The Outputs section includes logs that can help you troubleshoot issues if your automation fails.AWS CLI:1.    Collect bundle logs and upload them to the default S3 bucket for Elastic Beanstalk in your account:aws ssm start-automation-execution --document-name "AWSSupport-CollectElasticBeanstalkLogs"\        --parameters "InstanceId=INSTANCEID,\                               EnvironmentId=ENVIRONMENTID,\                               AutomationAssumeRole=AUTOMATIONROLE"2.    Collect bundle logs and upload them to your S3 bucket:aws ssm start-automation-execution --document-name "AWSSupport-CollectElasticBeanstalkLogs"\        --parameters "InstanceId=INSTANCEID,\                              EnvironmentId=ENVIRONMENTID,\                              S3BucketName=BUCKETNAME,\                              S3BucketPath=BUCKETPATH,\                              AutomationAssumeRole=AUTOMATIONROLE"3.    Retrieve the execution output:aws ssm get-automation-execution --automation-execution-id EXECUTIONID --output text --query 'AutomationExecution.Outputs'
Question: How do I move a Direct Connect connection from one AWS account to another?

I want to move an AWS Direct Connect connection from one AWS account to another.

Short descriptionTo move a Direct Connect connection between AWS accounts, you must transfer ownership of that connection. The source (current owner) and destination (new owner) AWS accounts must each open separate AWS Support cases to transfer ownership of the Direct Connect connection. This process confirms that both the source and the destination AWS accounts agree to the transfer.The transfer of a Direct Connect connection changes ownership and billing of the connection to the transferred account. No changes are made to the Direct Connect connection during the transfer. No network outages occur during the transfer of ownership also.Before beginning an ownership transfer, understand the following:Transfer of ownership is only available for Direct Connect dedicated connections. If you have a hosted connection from an AWS partner, then transfer of  ownership isn't possible. Reach out to your Direct Connect partner and inform them to order a new connection in the required account and to delete the previous account.Virtual interfaces associated with the Direct Connect connection aren't part of the transfer. They remain associated with the AWS account where they were created.Direct Connect gateways can't be moved from one AWS account to another.

ResolutionImportant: Make sure that the current owner and new owner agree to the Direct Connect connection transfer before opening an AWS Support case to start the ownership transfer.1.    Open an AWS Support case from the source account (the current owner of the Direct Connect connection) containing the below information:Direct Connect connection IDCurrent owner account IDNew owner account IDThis statement or similar: I would like to migrate my Direct Connect connection (connection name/ID) from account (account number) to account (account number).2.    Open an AWS Support case from the destination account (the new owner of the Direct Connect connection) containing the below information:Direct Connect connection IDCurrent owner account IDNew owner account IDThis statement or similar: I would like to migrate my Direct Connect connection (connection name/ID) from account (account number) to account (account number).3.    Copy and save the case number/ID of the AWS Support case created in step 2.4.    Update the source account's case with the destination account's case number/ID.5.    Wait for AWS Support to review both cases and process the ownership transfer.6.    When you receive confirmation of the migration completion, verify that the Direct Connect connection has moved to the new account. If you have any issues, reach out to AWS support on the support case ticket.

Related informationAWS Direct Connect connections
Question: How do I assign a static source IP address for all instances in a load-balanced Elastic Beanstalk environment?

I want to assign a single static IP address to my load balanced AWS Elastic Beanstalk environment to identify traffic coming from it.

Short descriptionYou can use a network address translation (NAT) gateway to map multiple IP addresses into a single, publicly exposed IP address. When your Elastic Beanstalk environment uses a NAT gateway, the backend instances in your environment are launched in private subnets. Elastic Beanstalk routes outbound traffic through the NAT gateway. You can identify the source of the outbound traffic from the backend instances by the Elastic IP address. The Elastic IP address is a static IP address required by the NAT gateway.

ResolutionElastic Beanstalk launches your Amazon Elastic Compute Cloud (Amazon EC2) instances into private subnets. These private subnets use a NAT gateway with an attached Elastic IP address as a default route. The load balancer is in public subnets. Elastic Beanstalk routes all external traffic to and from the load balancer through an internet gateway.Important: Before getting started, set up a NAT gateway.Open the Elastic Beanstalk console.Choose Create New Application, and then complete the steps to create your application.Note: If you're using an existing application, then skip to step 3 and configure your environment.Choose Actions, and then choose Create environment.Choose Web server environment, and then choose Select.Choose the options in the Environment information and rest of the Platform and Application Code sections based on the needs of your environment.Choose Configure more options.For Configuration presets, choose High availability. This sets your environment to a load-balanced environment.For the Network card, choose Edit, and then edit as follows:For VPC, choose your VPC.In the Load balancer settings section, for Visibility, choose Public.In the Load balancer subnets table, choose the public subnets.In the Instance settings section, clear Public IP address.In the Instance subnets table, choose only private subnets with the NAT gateway that you set up earlierChoose Save.Choose Create environment.The Elastic Beanstalk environment that you created now has all outbound traffic originating from a single Elastic IP address.