VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I create a new Windows WorkSpace image with a client language other than English?

I set the source WorkSpace language settings in Amazon WorkSpaces to a language other than English. Then, I created an image from that WorkSpace. When I launch a new WorkSpace from the resulting image bundle, the language reverts to English (US). How can I set the client language for my WorkSpace to use a different language?ResolutionWorkSpaces bundles that provide the Windows 10 desktop experience support English (US), French (Canadian), Korean, and Japanese. You can also download and install language packs for Windows directly from Microsoft. WorkSpaces client applications support English (US), German, Chinese (Simplified), Japanese, French (Canadian), Korean, and Portuguese.To successfully configure a different language for a WorkSpace image, you must modify the Sysprep language parameters before you create the image.From the source WorkSpace, modify the language parameters in a specified XML file. For a WorkSpace without bring your own license (BYOL), the file path is C:\ProgramData\Amazon\EC2-Windows\Launch\Sysprep\unattend.xml. For a BYOL WorkSpace, the file path is C:\Program Files\Amazon\Ec2ConfigService\sysprep2008.xml.The language parameters are:<InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale>Replace en-US with the language/region tag for your chosen language. (For example, enter de-DE for German). For a complete list of available languages and the associated language/region tag, see Available languages for Windows on the Microsoft website.Create a custom WorkSpace image and bundle from the source WorkSpace. When you launch a new WorkSpace from the resulting image bundle, the WorkSpace is set to your chosen language.

Related informationRequirements to create Windows custom imagesAmazon WorkSpaces FAQs
Question: What should I do if I didn't receive a call from AWS to verify my new account or the PIN I entered doesn't work?

I'm trying to open a new AWS account. When I reach the phone verification step, I don't receive an SMS message or call from AWS, or the PIN I entered was rejected. What do I do?ResolutionVerify the following:You've entered your telephone number and selected your country code correctly during the sign-up process.If you're using a mobile phone, then be sure that you have a cellular signal to receive SMS messages or calls.The information that you entered for your payment method is correct. A valid payment method is required to complete the account activation.Double-check to be sure that the PIN that you entered is correct.If you entered the number into your phone's keypad, try speaking the numbers instead.Retry the phone verification.If you're still not able to complete the verification process, then AWS Support can help you to activate your account manually:Be sure that you can be reached at the telephone number that you provided for your AWS account.Open the AWS Support console, and then choose Create case.Choose Account and billing support.For Type, select Account.For Category, select Activation.In the Description section, provide a date and time when you can be reached.In the Contact options section, select Chat for Contact methods.Choose Submit.Note: You can create a case with AWS Support even if your account isn't yet activated.

Related informationHow do I create and activate a new AWS account?How do I resolve the "maximum number of failed attempts" error when I try to verify my AWS account by phone?
Question: Why does my EBS volume have a status of "error"?

My Amazon Elastic Block Store (Amazon EBS) volume has a status of error. Why is this, and what can I do to fix it?Short descriptionThe error status indicates that the underlying hardware related to your EBS volume has failed. The data associated with the volume is unrecoverable and Amazon EBS processes the volume as lost. A notification appears on your account's Personal Health Dashboard when a volume enters an error state.Note: AWS doesn't bill for volumes with a status of error.

ResolutionIt’s a best practice to keep backups of your EC2 resources, including EBS volumes. You can use Amazon Data Lifecycle Manager, AWS Backup, or regular EBS snapshots for maintaining regular backups of your critical volumes to avoid data loss. For more information, see Best practices for Amazon EC2.Although you can't recover a volume in an error state, you can restore the lost data from your backup:If you have an EBS snapshot of the volume, you can restore that volume from your snapshot.If you don't have an EBS snapshot of the volume, create a new EBS volume, and then restore the data to it using the manual backup solution you prefer.Note: If the volume in an error state is attached to an Amazon Elastic Compute Cloud (Amazon EC2), you might get an error when starting the instance.

Related informationAmazon EBS volumesDurability and availability
Question: Why can't I increase the Amazon EBS disk volume in my Amazon MSK cluster?

I can't increase the Amazon Elastic Block Store (Amazon EBS) disk volume in my Amazon Managed Streaming for Apache Kafka (Amazon MSK) cluster.

ResolutionThe most common causes for this issue are as follows:You don't have the required permissions to modify the Amazon EBS volume.Your cluster is in the optimizing state from a prior Amazon EBS volume upgrade.You don't have the required permissions to modify the Amazon EBS volumeMake sure that you have the required permissions to modify the EBS disk volume for your cluster. Make sure that you attached the AmazonMSKFullAccess or AmazonMSKClusterManagement policy to your AWS Identity and Access Management (IAM) user or role.Your cluster is in the optimizing state from a prior Amazon EBS volume upgradeIn this case, you get the error "An EBS volume in this cluster is under modification from a previous operation".When you increase the size of an EBS volume that's attached to your Amazon MSK broker node, the newly added storage is available to you immediately. However, it takes from 6 to 24 hours or more for the cluster to be optimized. The duration for cluster optimization is proportional to the size of the storage.When you increase the size of the EBS volume, make sure that the added volume is sufficient for the next 48 hours or more. During this period, you can't add more volumes to your cluster. You can't update the volume further until the cluster is optimized.Important: Suppose that your cluster is being optimized and you're already running out of disk space. In this case, be sure to turn off automatic scaling if you previously turned it on. Otherwise, when optimization is complete, the volume is increased only by 10% or 10 GB. This might be too low, causing similar issues with volume modification. After turning off automatic scaling, be sure to analyze your traffic patterns and increase your storage space accordingly.If your cluster is undergoing modification and the KafkaDataLogsDiskUsed metric is less than 94%, you can delete unused or old topics to free up space. Run the following command to determine the space occupied per topic:kafka-topics.sh --command-config /tmp/client.properties --bootstrap-server $bservers --list | xargs -I{} sh -c "echo -n '{} - ' && kafka-log-dirs.sh --command-config /tmp/client.properties --bootstrap-server $bservers --topic-list {} --describe | grep '^{'  | jq '[ ..|.size? | numbers ] | add' | numfmt --to iec " | tee /tmp/topics-by-size.listThen, delete the unused or old topics to free up disk space.Note: If KafkaDataLogsDiskUsed is higher than 94%, then this command might be unresponsive. In this case, you can't delete the topics.
Question: What is EFS One Zone and how do I convert my existing multi-zone EFS to EFS One Zone?

What is EFS One Zone and how to I convert existing multi-zone Amazon Elastic File System (Amazon EFS) to EFS One Zone?ResolutionAmazon EFS offers storage classes for different use cases, including the following:EFS Standard and EFS Standard–Infrequent Access (Standard-IA)EFS One Zone and EFS One Zone–Infrequent Access (EFS One Zone-IA)For more information on the difference between these storage classes, see Comparing Amazon EFS storage classes.How to convert existing multi-zone EFS to EFS One ZoneThere isn't a direct solution to convert the existing multi-zone EFS to EFS One Zone. To move to EFS One Zone, you can do one of the following:Create a new EFS One Zone and then copy the data from the existing EFS volumes. For more information, see Transferring data into and out of Amazon EFS.-or-Use AWS Backup to restore the entire file system with the EFS One Zone file system type. For more information, see How can I back up and restore my Amazon EFS file systems?
Question: How do I migrate my Elastic Beanstalk environment from one AWS account to another AWS account?

I want to migrate my AWS Elastic Beanstalk environment from one AWS account to another AWS account.

Short descriptionYou must use saved configurations to migrate an Elastic Beanstalk environment between AWS accounts.Saved configurations are stored in the Amazon Simple Storage Service (Amazon S3) bucket for Elastic Beanstalk in a folder named after your application. For example, the location of a saved configuration for an application named my-app in the us-east-1 AWS Region for account 01234567890 looks like this:s3://elasticbeanstalk-us-east-1-01234567890/resources/templates/my-app/ResolutionIn the following steps, Account A is the account where you have your Elastic Beanstalk environment. Account B is the account that you want to migrate your Elastic Beanstalk Environment to.Note: In this example, both Account A and Account B have Elastic Beanstalk environments already created. The saved configuration is created by Elastic Beanstalk when you create the environment. This environment is uploaded to Account B's Amazon S3 bucket.Create a saved configuration for Account A1.    Create a saved configuration in Account A.2.    Download the saved configuration to your local machine from the following:s3://elasticbeanstalk-us-east-1-account-a-id/resources/templates/application-a-name/Note: In your saved configuration, us-east-1 is the AWS Region where the Elastic Beanstalk environment is located in Account A. The account-a-id is your account ID for Account A. The application-a-name is the application name of the Elastic Beanstalk application in Account A.3.    Change your account-specific parameters in the downloaded configuration file, and then save the changes. For example, change the key pair name, subnet ID, or application name (such as application-b-name).Create an Elastic Beanstalk environment using the saved configuration in Account B1.    Log in to Account B.2.    Upload the saved configuration from your local machine to an S3 bucket in Account B.The S3 path looks similar to the following:s3://elasticbeanstalk-us-east-2-account-b-id/resources/templates/application-b-name/3.    Open the Elastic Beanstalk console.4.    From the Regions list, select your AWS Region.5.    From the navigation pane, choose Applications, and then choose Create a new application.6.    For Application name, enter the name of your new application  (for example, application-b-name).7.    From the left navigation pane, in the section for your new application, choose Saved configurations.Now you can see all the saved configurations that you have in the S3 bucket in a given Region for your account.8.    Choose the saved configuration that you previously uploaded to the S3 bucket in the following account:s3://elasticbeanstalk-us-east-2-account-b-id/resources/templates/application-b-name/9.    Launch your Elastic Beanstalk environment.
Question: How do I share an Amazon Machine Image (AMI) privately with another AWS account?

I want to make an Amazon Machine Image (AMI) that I've created available to another AWS account.

ResolutionIf you know the account IDs of the AWS accounts that you want to share the AMI with, follow the instructions at Share an AMI with specific AWS accounts.To copy the shared AMI, see Cross-account copying.Note: Sharing an AMI from different Regions isn't available. You can copy the AMI and then share it or launch it in a new Region. For more information, see How do I create and copy an Amazon Machine Image (AMI) from one AWS Region to another?Related informationShared AMIs
Question: Why is my Amazon Redshift snapshot missing some tables?

I restored a snapshot from an Amazon Redshift cluster, but the snapshot is missing some tables. How do I back up my missing tables?Short descriptionTables created as no-backup tables are excluded from Amazon Redshift snapshots. Verify whether Amazon Redshift excluded your table because it was created using the BACKUP NO parameter. Then, perform a deep copy.

ResolutionTo back up missing tables from your Amazon Redshift snapshot, perform the following steps:1.    Check the Data Definition Language (DDL) of the tables that are missing from the snapshot.2.    If the table's DDL is unavailable, then run the following query as a superuser:SELECT DISTINCT Rtrim(n.nspname) AS schema_name,                Rtrim(name)      AS table_name,                backupFROM   stv_tbl_perm t       join pg_class c         ON t.id = c.oid       join pg_namespace n         ON n.oid = c.relnamespaceORDER  BY 1,2;The query above identifies tables in the connected database that aren't backed up in the snapshot. It queries STV_TBL_PERM, the system table that is only visible to superuser accounts. For more information about views that are only available to superusers, see Visibility of data in system tables and views.Note: A value of 0 for the backup column indicates that the table was created using the BACKUP NO parameter. You cannot alter an existing table in Amazon Redshift using the BACKUP YES parameter.3.    If your table was created as a no-backup table, then recreate the table without the BACKUP NO parameter.4.    Perform a deep copy of your missing tables.

Related informationCREATE TABLE AS ParametersAmazon Redshift Snapshots
Question: How can I troubleshoot "429 Too Many Requests" or "Limit Exceeded" errors for my API Gateway API?

I received "429 Too Many Requests" or "Limit Exceeded" errors when sending requests to my Amazon API Gateway API. How do I troubleshoot these errors?Short descriptionAPI Gateway has account-level quotas, per Region. The throttle quota is 10,000 requests per second (RPS) with an additional burst capacity provided by the token bucket algorithm. The maximum bucket capacity is 5,000 requests per account and Region. API Gateway throttling-related settings are applied in the following order:Per-client or per-method throttling limits that you set for an API stage in a usage plan.Per-method throttling limits that you set for an API stage.Account-level throttling per Region.AWS Regional throttling.Exceeding the throttling limit or quota returns a "429 Too Many Requests" or "Limit Exceeded" error response.For more information, see How throttling limit settings are applied in API Gateway.

ResolutionBefore you begin, make sure that you have followed the instructions to turn on Amazon CloudWatch Logs for troubleshooting API Gateway. Make sure that you choose ERROR to generate execution logs only for requests to your API that result in an error. Then, view logged API requests and responses using the CloudWatch console."429 Too Many Requests" errorCheck the rate or burst limit for per-client or per-method throttling limits that you set for the API stage for your usage plan. When the rate or burst limits are exceeded, CloudWatch execution logs an exceeded throttle limit error similar to the following:(f277a0b4-2bcd-41b3-8e43-4de770663ffb) API Key **********************************F0yrv6 exceeded throttle limit for API Stage rohkz08x02/dev: Key throttle limit exceeded for Usage Plan ID nnpegc, RestApi rohkz08x02, Stage dev, Resource f646q2, HttpMethod GET. Limit: 5.00 Burst: 10To resolve this error, use retries and an exponential backoff algorithm with jitter, and then resubmit your API request.For more information, see exponential backoff and jitter."Limit Exceeded" errorThis error might indicate that the quota limit is exceeded for your API Gateway usage plan. When the quota limit is exceeded, then CloudWatch execution logs an exceeded quota limit error similar to the following:(7b819c41-e0a0-433a-883e-bc461fd70fd6) API Key **********************************F0yrv6 exceeded quota limit for API Stage rohkz08x02/dev: Key quota exhausted for Usage Plan ID nnpegc. QLimit: 500 Period: DAYTo resolve this error, follow the instructions to extend the remaining quota.

Related informationHow do I troubleshoot Lambda function throttling with "Rate exceeded" and 429 "TooManyRequestsException" errors?How do I find API Gateway REST API errors in my CloudWatch logs?
Question: How can I troubleshoot Pending Verification domain name issues for VPC endpoint services?

I'm configuring a private DNS name for my Amazon Virtual Private Cloud (Amazon VPC) endpoint service (AWS PrivateLink) and setting up a DNS TXT record. The domain verification status is stuck in Pending Verification. How can I troubleshoot this?Short descriptionThe following are common reasons for the domain verification status to be stuck in the Pending Verification status:You're using a domain name that isn't owned by you or your organization.You created a TXT record in private zone file instead of public zone file.The domain registrar has the wrong name servers for your domain.Note: For information on setting up a private DNS name for your VPC endpoint services, see How can I set up my VPC endpoint service to use a custom private DNS name?ResolutionYou're using a domain name that isn't owned by you or your organizationThe endpoint service provider can only use a domain name that's owned by you or your organization as a private DNS name. For example, you can't use “amazonaws.com“ as the private DNS name because that domain is owned by Amazon.You created a TXT record in a private zone instead of public zoneAWS verifies the ownership of the domain name provided under endpoint services. This is done by querying TXT records against the authorized public name server configured under the domain registrar. Verification fails if the user configured the TXT record on a private zone file because it can't be queried publicly.You can check whether the TXT record value is created in the publicly-verifiable domain or not by using the nslookup command. This command works in both Windows and Linux machines:nslookup -type=TXT _aksldja21i1.myexampleservice.comIf the TXT record was created in the publicly-verifiable domain, then you receive the domain verification value used while creating the TXT record as the output:_aksldja21i1.myexampleservice.com text = "vpce:asjdakjshd78126eu21”If the TXT record was created in the private hosted zone, then you receive output similar to the following:_aksldja21i1.myexampleservice.com = "v=spf1 -all”Note: You can also verify this information using any 3rd party websites, such as whatsmydns.The domain registrar has the wrong name servers for your domainFor private DNS verification, AWS queries the public name servers that are registered under the domain registrar. So, it's important to make sure that the name servers in your public zone file matches the name servers of your registered domain at the registrar.Note: If the verification status shows Pending Verification for a long time, then you can try manually starting the verification process. For more information, see Manage DNS names for VPC endpoint services.

Related informationYou recently transferred DNS service to Amazon Route 53, but you didn't update the name servers with the domain registrar
Question: How do I resolve the "Image does not exist" error when my tasks fail to start in my Amazon ECS cluster?

My Amazon Elastic Container Service (Amazon ECS) service fails to start tasks in my Amazon ECS cluster. Then, I receive an error similar to the following: "CannotPullContainerError: Error response from daemon: manifest for 1234567890.dkr.ecr.us-east-1.amazonaws.com/test:curlnginx1234 not found." How can I resolve this error?Short descriptionThe resolution for this error applies to pulling images from an Amazon Elastic Container Registry (Amazon ECR) repository.If you didn't receive the preceding error message, choose a resolution based on one of the following issues or errors:Your container is exiting due to application issues or resource constraints.The health checks for your Application Load Balancer are failing.Docker can't pull the container image.[AWS service] was unable to place a task because no container instance met all of its requirements.[AWS service] was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id has insufficient CPU units available.[AWS service] was unable to place a task because no container instance met all of its requirements. The closest matching container-instance container-instance-id encountered error "AGENT".Note: To troubleshoot Amazon ECS service issues, check for diagnostic information in the service event log.Resolution1.    Verify that the image is declared in your Amazon ECS task definition.2.    Verify that the Docker image exists in the Amazon ECR repository.Note: To view repository information, you can use the Amazon ECR console or run the following commands:To confirm that an image exists in an ECR repository, run the following list-images command:aws ecr list-images --repository-name "hello-world"  --region us-east-1To filter for images in an ECR repository, run the following describe-images command:aws ecr describe-images --repository-name "hello-world" --region us-east-1 --query 'sort_by(imageDetails,& imagePushedAt)[*]'Note: Be sure to update your commands with the name of your ECR repository and AWS Region.3.    Use the full URI for the image when you specify an Amazon ECR image in your task definition.Important: Verify that there are no leading or trailing character spaces in the URI for the image.
Question: How do I change the public IP address of my customer gateway for my AWS VPN connection?

The public IP address for my customer gateway has changed, and I need to update my AWS Virtual Private Network (AWS VPN) connection to reflect this change.

ResolutionFollow the instructions to create a customer gateway with the new public IP address assigned to your customer gateway. Then, follow the instructions to change the customer gateway for a Site-to-Site VPN connection.

Related informationHow do I create a certificate-based VPN using AWS Site-to-Site VPN?
Question: Why can't I connect to my Elastic Beanstalk instance using SSH?

I can't connect to the Amazon Elastic Compute Cloud (Amazon EC2) instances in my AWS Elastic Beanstalk environment using SSH. How do I troubleshoot this issue?ResolutionBefore you connect to your instance using SSH, confirm the following:Your Amazon EC2 instance is in a public subnet and has a public IP address.You have an inbound rule on port 22 on the security group of your instances that allows your IP address or range of IP addresses to connect to your instance.You meet all the general prerequisites for connecting to your instance.If you continue to experience timeout issues and still can't connect to your instance, then the SSH daemon on your instance could be crashing due to high memory utilization.To troubleshoot memory issues, monitor the memory metrics of your Elastic Beanstalk instances using Amazon CloudWatch metrics.