VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: Why is my domain suspended with the status ClientHold in Route 53?

My domain in Amazon Route 53 is suspended with the status ClientHold.

ResolutionConfirm the registrant email addressICANN requires email verification for several domain registration operations. To revoke the domain suspension, choose the link in the verification email to confirm the registrant email address. If you don't have access to the registered email for the account, then proceed to the following section: Change the registered email address.Amazon Route 53 sends the verification email to the registered email address from one of the following email addresses:noreply@registrar.amazon.com - for TLDs registered by the Amazon registrarnoreply@domainnameverification.net - for TLDs registered by the GandiNote: If you don't see the confirmation email in your primary mailbox, then check your spam or junk folder.Resend the confirmation emailIf you can't find or didn't receive the confirmation mail, then resend the email using the following steps:Open the Route 53 console.In the navigation pane, choose Registered domains.Select the name of the domain that you want to resend the email for.In the warning box with the heading Your domain might be suspended, choose Send email again.For more information, see Resending emails.Change the registered email addressIf you don't have access to the registered email address, then you can change the email address. See, How do I change the email address for my registered domain in Route 53 if I lost access to my previous email address?
Question: The available memory in my ElastiCache Redis node is less than the value listed on the Amazon ElastiCache pricing page. Why is this?

The available memory in my Amazon ElastiCache Redis node is always less than the value listed in Amazon ElastiCache pricing. Why is this?ResolutionThe ElastiCache pricing page shows the available memory in GiB for each supported node type. However, in the default parameter group, a percentage of the memory is reserved for backups and failover operations. For Redis versions before 2.8.22, it's a best practice to reserve 50% of the total memory. For Redis versions 2.8.22 and later it's a best practice to reserve 25% of the total memory. The parameter that regulates this is reserved-memory (for customers who started with ElastiCache before March 16, 2017) or reserved-memory-percent (for customers who started with ElastiCache on or after March 16, 2017).For example, a cluster using cache.t3.micro node type that is in the default parameter group has 0.5 GiB of total memory. Due to the reserved-memory-percent parameter, 25% of this memory is reserved. Therefore, the available memory in this node is 0.375 GiB.To see the available memory in an ElastiCache Redis node:1.    Connect to the cluster using the redis-cli tool or another tool of your choice. For information on using the redis-cli tool, see Connect to a Redis cluster or replication group (Linux).2.    Run the info memory command and check the maxmemory value. The following example output was generated using redis-cli connected to a Redis server with IP address 172.31.35.93.172.31.35.93:6379> info memory# Memorymaxmemory:402653184Note: The maxmemory value is in bytes. 402653184 bytes is equivalent to 0.375 GiB. The Redis engine uses bytes or MB to represent memory. The AWS documentation uses GiB to represent memory. Although the difference between these two units is marginal and makes almost no difference with small numbers, the difference grows exponentially based on the size of the node memory. You can use an online calculator of your choice to convert between these units.

Related informationManaging reserved memory
Question: How can I get customized email notifications when my EC2 instance changes states?

I want to receive email notifications when my Amazon Elastic Compute Cloud (Amazon EC2) instance changes states. How can I do this?Short descriptionTo receive email notifications when your EC2 instance changes states:1.    Create an Amazon Simple Notification Service (Amazon SNS) topic. The SNS topic sends messages to subscribing endpoints or clients.2.    Create an Amazon EventBridge using the EC2 Instance State-change Notification event type.

ResolutionCreate an SNS topic1.    Open the Amazon SNS console, and then choose Topics from the navigation pane.2.    Select Create topic.3.    For Type, choose Standard.4.    For Name, enter a name for your topic.5.    For Display name, enter a display name for your topic.6.    Select Create topic.7.    On the Subscriptions tab, choose Create subscription.8.    For Protocol, choose Email.9.    For Endpoint, enter the email address where you want to receive the notifications.10.  Select Create subscription.A subscription confirmation email is sent to the address that you entered. Choose Confirm subscription in the email. Note the SNS topic that you created. You use this topic when creating the EventBridge rule.Create an EventBridge event1.    Open the EventBridge console.2.    Select Create rule from the homepage. Or, choose Rules under Events in the sidebar, and then select Create rule.3.    Enter a Name for your rule. You can optionally enter a Description.4.    Keep the default Event bus and Rule type settings, and then select Next.5.    In Event pattern, keep the Event source as AWS services. For the AWS service, choose EC2.6.    For Event type, choose EC2 Instance State-change Notification.7.    Keep Any state and Any instance as the default settings, and then select Next.8.    For Select a target, choose SNS topic.9.    For Topic, choose the topic name that you created earlier, and then select Next.10.  Expand the Additional settings section. For Configure target input, choose Input transformer.11.  Select Configure input transformer, and then enter the following text:        For Input path, enter the following:{"instance-id":"$.detail.instance-id", "state":"$.detail.state", "time":"$.time", "region":"$.region", "account":"$.account"}        For Template, enter the following:"At <time>, the status of your EC2 instance <instance-id> on account <account> in the AWS Region <region> has changed to <state>."        Note: The Input Template also allows custom inputs.12.  Select Next.13.  Leave the optional Tags empty, and select Next. Then, select Create rule.        Note: The rule that you created applies to a single AWS Region.You can test the rule by starting or stopping an instance. This rule generates an email notification every time an instance changes to any state, including stopped.
Question: Can I migrate my Amazon Connect instance from a test environment to a production environment?

I have a test Amazon Connect contact center instance with resources that I want to migrate to my production instance. Can I migrate my test Amazon Connect instance to a production environment? If so, what resources can I migrate?ResolutionYou can migrate the following resources between Amazon Connect contact center instances:Contact flowsIf you want to migrate a small number of contact flows, see Import/export contact flows. To migrate hundreds of contact flows, see Migrate flows to a different instance.Phone numbersTo migrate phone numbers from an Amazon Connect instance to another instance in same AWS Region, see How do I migrate phone numbers from one Amazon Connect instance to another?To migrate phone numbers from an Amazon Connect instance to another instance in a different AWS Region, create an AWS Support case and ask for assistance with Phone Number migration in different region.UsersFor more information, see CreateUser, DeleteUser, and ListUsers in the Amazon Connect API Reference.Note: If you added users in bulk using the CSV template, you can upload the same file to add those users to another instance.QueuesFor more information, see CreateQueue, DescribeQueue, and ListQueues in the Amazon Connect API Reference.Quick connectsFor more information, see CreateQuickConnect, DeleteQuickConnect, and AssociateQueueQuickConnects in the Amazon Connect API Reference.Routing profilesFor more information, see CreateRoutingProfile, AssociateRoutingProfileQueues, and DescribeRoutingProfile in the Amazon Connect API Reference.Hours of operationFor more information, see CreateHoursOfOperation in the Amazon Connect API Reference.Agent statusFor more information, see CreateAgentStatus in the Amazon Connect API Reference.Security profilesFor more information, see CreateSecurityProfile in the Amazon Connect API Reference.

Related informationWhat information should I include in my AWS Support case?
Question: Why is my Amazon EBS volume stuck in the "attaching" state?

I attached my Amazon Elastic Block Store (Amazon EBS) to my Amazon Elastic Compute Cloud (Amazon EC2) instance, but it’s still in the "attaching" state after 10-15 minutes.

ResolutionCheck that the device name you specified when you attempted to attach the EBS volume isn't already in use. If the specified device name is already being used by the block device driver of the EC2 instance, the operation fails.When attaching an EBS volume to an Amazon EC2 instance, you can specify a device name for the volume (by default, one is filled in for you). The block device driver of the EC2 instance mounts the volume and assigns a name. The volume name can be different from the name that you assign.For more details on device naming, see Device naming on Linux instances or Device naming on Windows instances.If you specify a device name that's not in use by Amazon EC2, but is used by the block device driver within the EC2 instance, the attachment of the Amazon EBS volume fails. Instead, the EBS volume is stuck in the attaching state. This is usually due to one of the following reasons:The block device driver is remapping the specified device nameOn an HVM EC2 instance, /dev/sda1 remaps to /dev/xvda. If you attempt to attach a secondary Amazon EBS volume to /dev/xvda, the secondary EBS volume can't successfully attach to the instance. This can cause the EBS volume to be stuck in the attaching state.The block device driver didn't release the device nameIf a user has initiated a forced detach of an Amazon EBS volume, the block device driver of the Amazon EC2 instance might not immediately release the device name for reuse. Attempting to use that device name when attaching a volume causes the volume to be stuck in the attaching state. You must either choose a different device name or reboot the instance.You can resolve most issues with volumes stuck in the attaching state by following these steps:Important: Before you begin, back up your data. For more information, see Best practices for Amazon EC2.In the Volumes pane of the Amazon EC2 console, select the volume.Open the Actions menu and then choose Force Detach Volumes.Attempt to attach the volume to the instance, again, but use a different device name. For example, use /dev/sdg instead of /dev/sdf.Note: The instance must be in the running state.If these steps don’t resolve the issue, or if you must use the device name that isn't working, try the following procedures:Reboot the instance.Stop and start the instance to migrate it to new underlying hardware. Keep in mind that instance store data is lost when you stop and start an instance. If your instance is instance store-backed or has instance store volumes containing data, the data is lost when you stop the instance. For more information, see Determining the root device type of your instance.

Related informationAttaching an Amazon EBS volume to an instanceMapping disks to volumes on your Windows instance
Question: How do I estimate the cost of my planned AWS resource configurations?

I want to provision AWS resources. How can I estimate how much my AWS resources will cost?ResolutionUnderstand the principles of AWS cloud pricingMost AWS services offer pay-as-you-go pricing, so you pay for only what you use each month. For more information, see AWS pricing.Each AWS service has its own pricing model. For more information, see Cloud Services pricing.Estimate your AWS billingIf you plan to migrate significant infrastructure to AWS, use the AWS Sales & Business Development contact form, and then choose I need to speak to someone in sales.To estimate a bill, use the AWS Pricing Calculator. Choose Create estimate, and then choose your planned resources by service. The AWS Pricing Calculator provides an estimated cost per month. For more information, see What is AWS Pricing Calculator?To forecast your costs, use the AWS Cost Explorer. Use cost allocation tags to divide your resources into groups, and then estimate the costs for each group.Note: AWS Support can't estimate your costs for migrating infrastructure to AWS.
Question: Why am I receiving a "no Spot capacity available" error when trying to launch an Amazon EC2 Spot Instance?

I get an error message when I try to launch an Amazon Elastic Compute Cloud (Amazon EC2) Spot Instance. The error reads, "There is no Spot capacity available that matches your request."ResolutionThe "no Spot capacity available" error occurs when Amazon EC2 doesn't have enough Spot capacity to fulfill a Spot Instance or Spot Fleet request. Spot capacity is the amount of spare, unused EC2 compute capacity that's available to customers at a lower price than On-Demand Instances.To troubleshoot this error, do one of the following:Keep the request as it is. The Spot request continues to automatically make the launch request until capacity becomes available. When capacity becomes available, Amazon EC2 fulfills the Spot request. If you encounter the "no Spot capacity available" error frequently, then consider using the next workaround.Be flexible about the instance types that you request and the Availability Zones that you deploy when setting up your workload. For example, instead of requesting an m5.large in us-east-1a, request an m4.large, c5.large, r5.large, or t3.xlarge in multiple Availability Zones. This type of request increases the chances of Amazon Web Services (AWS) finding and allocating your required amount of compute capacity.Use the price and capacity optimized allocation strategy (best practice). This allocation strategy looks at both price and capacity to select the Spot Instance pools. The Spot Instance pools that are selected are the least likely to be interrupted and have the lowest possible price. The price and capacity optimized strategy maintains an interruption rate that's comparable to the capacity-optimized allocation strategy. Also, with this strategy, the total price of your Spot Instances is typically lower than the capacity-optimized strategy. For more information, see Allocation strategies for Spot Instances.Use the capacity-optimized allocation strategy. This allocation strategy analyses real-time capacity data to launch your Spot Instances into pools with the most available capacity. The capacity-optimized allocation strategy reduces your chances of receiving "no Spot capacity available" errors.You might implement the preceding solutions when provisioning a Spot Instance through Amazon EC2 Auto Scaling, EC2 Fleet, and Spot Fleet. For a complete list of best practices when using Spot Instances, see Spot Instance best practices.

Related informationSpot Instance interruptionsSpot request status
Question: How can I increase my IAM default quota?

I want to increase my AWS Identity and Access Management (IAM) default quota.

ResolutionYou can request an increase to default quotas for adjustable IAM quotas up to the maximum limit. Quota requests within the maximum limit are automatically approved.To view the default and maximum IAM quota limits, see IAM object quotas.Note:IAM quota increase requests are available only in the US East (N. Virginia) Region.You can't request an increase to default quotas that aren't adjustable.Follow these steps to request an increase for adjustable IAM quotas within the maximum limit:1.    Open the Service Quotas console in the us-east-1 Region.2.    In the navigation pane, choose AWS services.3.    In the AWS services search bar, enter IAM.4.    In Service, choose IAM.5.    In Quota name, choose the quota that you want to increase.Note: Make sure that the Adjustable value equals Yes.6.    Choose Request quota increase.7.    In Change quota value, enter the quota amount, and then choose Request.8.    In Recent quota increase requests, the Status is Pending.9.    After five minutes, refresh the page.If the quota request is below the maximum quota limit, the request is automatically approved and the Status is now Quota request approved.(Optional) To request an increase for adjustable IAM quotas above the maximum limit:1.    Follow the previous steps 1-9.2.    If the quota request is above the maximum quota limit, the Status is now Quota requested. Choose Quota requested to view the Support Center case number opened on your behalf.You can view the status of your quota increase request by choosing the Support case number.Note: Quota requests above the maximum default limit are not automatically approved.

Related informationRequesting a quota increase
Question: Do I need to specify the AWS KMS key when I download a KMS-encrypted object from Amazon S3?

I want to download stored objects from Amazon Simple Storage Service (Amazon S3) that use server-side encryption with AWS Key Management Service-managed keys (SSE-KMS).

ResolutionYou don't need to specify the AWS Key Management Service (AWS KMS) key ID when you download an SSE-KMS-encrypted object from an S3 bucket. Instead, you need the permission to decrypt the AWS KMS key.When a user sends a GET request, Amazon S3 must check for the appropriate authorization. Amazon S3 checks if the AWS Identity and Access Management (IAM) user or role that sent the request is authorized to decrypt the object's key. If the IAM user or role and key belong to the same AWS account, then decrypt permissions must be granted on the key policy.Note: When the IAM user or role and KMS key are in the same account, you can use IAM policies to control access to the key. However, you must modify the key policy to explicitly turn on IAM policies to allow access to the key. For more information, see Using IAM policies with AWS KMS.If the IAM user or role and key belong to different accounts, then you have to grant decrypt permissions on the IAM user's policy and the key's policy.The following is an example IAM policy that allows the user to both decrypt the AWS KMS key and also download from the S3 bucket:{  "Version": "2012-10-17",  "Statement": [    {      "Sid": "VisualEditor0",      "Effect": "Allow",      "Action": [        "kms:Decrypt",        "s3:GetObject"      ],      "Resource": [        "arn:aws:kms:example-region-1:123456789012:key/example-key-id",        "arn:aws:s3:::DOC-EXAMPLE-BUCKET/*"      ]    }  ]}The following is an example key policy statement that allows the user to decrypt the key:{  "Sid": "Allow decryption of the key",  "Effect": "Allow",  "Principal": {    "AWS": [      "arn:aws:iam::123456789012:user/Bob"    ]  },  "Action": [    "kms:Decrypt"  ],  "Resource": "*"}Note: For IAM users or roles that belong to a different account than the bucket, the bucket policy must also grant the user access to objects. For example, if the user needs to download from the bucket, then the user must have permission to the s3:GetObject action on the bucket policy.After you have the permission to decrypt the key, you can download S3 objects encrypted with the key using the AWS Command Line Interface (AWS CLI). Run a command similar to the following:aws s3api get-object --bucket DOC-EXAMPLE-BUCKET --key dir/example-object-name example-object-nameNote: If you receive errors when running AWS CLI commands, make sure that you're using the most recent version of the AWS CLI.

Related informationGetObjectget-objectProtecting data using server-side encryption with CMKs stored in AWS Key Management Service (SSE-KMS)
Question: Why is my Amazon EBS volume stuck in the "deleting" state?

My Amazon Elastic Block Store (Amazon EBS) volume is stuck in the "deleting" state, and I don't know why.

ResolutionGenerally, Amazon EBS volumes are immediately deleted when you use the Amazon Elastic Compute Cloud (Amazon EC2) console or AWS Command Line Interface (AWS CLI). However, the volume can get stuck in the "deleting" state when there's an active snapshot that's associated with your volume.If you make a CreateSnapshot API call immediately before making a DeleteVolume request, then volume deletion is postponed until snapshot creation completes. Before deleting a volume, check for any snapshot creations that are still in progress. For instructions on how to access snapshot information, see View Amazon EBS snapshot information.Note: Even after a snapshot creation is complete, volume deletion might still be delayed because volume workflows are asynchronous.
Question: Why is my instance terminating immediately after launching or starting an instance?

My Amazon Elastic Compute Cloud (Amazon EC2) instance state changes from pending to terminated immediately after launching a new instance, or after starting a stopped instance. How can I troubleshoot this issue?ResolutionFirst, determine the termination reason using the Amazon EC2 console or AWS Command Line Interface (AWS CLI). Then, follow the troubleshooting steps for that reason. For more information, see Instance terminates immediately.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.

Related informationInstance volume limitsdescribe-instancesUsing key policies in AWS KMSWhy am I unable to start or launch my EC2 instance?
Question: How can I create additional listeners for AWS Elastic Beanstalk environments that use a shared load balancer?

I want to create additional listeners for AWS Elastic Beanstalk environments that use a shared load balancer.

Short descriptionIf you're using a shared load balancer with Elastic Beanstalk, then you can't create additional listeners using the aws:elbv2:listener:listener_port option setting or the Elastic Beanstalk console. This is because the load balancer isn't managed by Elastic Beanstalk.You can use .ebextension custom resources to create additional listeners for an Elastic Beanstalk environment with a shared load balancer.Tip: It's a best practice to associate additional listeners with the lifecycle of the environment, and to remove the listeners if you terminate the environment.Resolution1.    Create an Application Load Balancer that includes a default listener and target group.2.    Create a configuration file called additional-listener.config file that includes the following:Resources:  AdditionalHttpListener:      Type: AWS::ElasticLoadBalancingV2::Listener      Properties:        LoadBalancerArn:          "Fn::GetOptionSetting":            Namespace: "aws:elbv2:loadbalancer"            OptionName: "SharedLoadBalancer"        DefaultActions:        - Type: forward          TargetGroupArn:            Ref: AWSEBV2LoadBalancerTargetGroup        Port: 8080        Protocol: HTTPNote: The YAML file in step 2 follows the AWS CloudFormation specification for the AWS::ElasticLoadBalancingV2::Listener resource.3.    Place the file from step 2 into the .ebextensions folder that's part of your application source bundle.4.    Create a ZIP file of your updated application source bundle.5.    Use the ZIP file from step 4 to create a new Elastic Beanstalk environment, or update an existing environment that's configured with the shared load balancer from step 1.The configuration file from step 2 creates an HTTP listener on port 8080 for the shared load balancer associated with your Elastic Beanstalk environment. Then, the listener forwards all traffic to the default process. You can further extend this configuration file to add additional rules to the listener using the AWS::ElasticLoadBalancingV2::ListenerRule resource definition of CloudFormation.Important: Because this listener is created as an additional resource as part of the Elastic Beanstalk environment, the listener is removed if the environment is terminated.Note: To learn more about shared load balancers and default listener rules, see Configuring a shared Application Load Balancer.