VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How can I check the amount of backup storage being used by my Aurora PostgreSQL-Compatible DB instances?

I want to check the amount of storage used by the backup of my Amazon Aurora PostgreSQL-Compatible Edition DB instances.

ResolutionNote: If you receive errors when running AWS Command Line Interface commands, make sure that you’re using the most recent version of the AWS CLI.To check the storage usage of your Aurora DB instances backup, you can use these Amazon CloudWatch metrics:BackupRetentionPeriodStorageUsed - the amount of backup storage used for continuous backups at a given time.SnapshotStorageUsed - the amount of backup storage used for storing manual snapshots beyond the backup retention period.TotalBackupStorageBilled - the sum of BackupRetentionPeriodStorageUsed and SnapshotStorageUsed minus the mount of free backup storage.For more information on using these metrics, see Understanding Amazon Aurora backup storage usage.For more information on accessing these metrics using Amazon CloudWatch, see Monitoring Amazon Aurora metrics with Amazon CloudWatch.You can also using the AWS CLI to view Amazon CloudWatch metrics about your Aurora instances. For instructions on how to view these metrics in the AWS CLI, see Viewing DB cluster metrics in the CloudWatch console and AWS CLI.Note: Aurora databases don't have the FreeStorageSpace metric.Preformatted code block (delete if article contains no code)

Related informationOther considerations for Aurora backup storage and pricing
Question: How do I check if resource record sets in my Route 53 public hosted zone are accessible from the internet?

I created a public hosted zone in Amazon Route 53 and added resource record sets in it. How do I verify that my resource record sets are reachable from the internet?Short descriptionCheck whether your resource record sets are accessible from the internet using one of the following methods:The Route 53 checking toolThe dig tool (for Linux, Unix, or Mac)The nslookup tool (for Windows)Note: The steps in this article verify that the public hosted zone is created successfully and accessible. If you want your entire domain resolvable, then verify the following:Update the domain registration to use Amazon Route 53 name serversUpdate the NS records to use Route 53 name servers

ResolutionMethod 1: Use the Route 53 checking toolUse the Route 53 checking tool to see how Route 53 responds to DNS queries.Method 2: Use the dig tool (for Linux, Unix, or Mac)1.    Find the four authoritative name servers for your public hosted zone.2.    In your resource record set’s configuration, find the associated domain name (Name), record type (Type), and value (Value).3.    Query one of the authoritative name servers. In your command line argument, specify the authoritative name server and the resource record set's domain name and record type. For example:$ dig @ns-###.awsdns-##.com  mailserver1.example.com  MX$ dig @ns-###.awsdns-##.com  _text_.example.com  TXT$ dig @ns-###.awsdns-##.com  cname.example.com  CNAME$ dig @ns-###.awsdns-##.com  subdomain.example.com  NS$ dig @ns-###.awsdns-##.com  www.example.com  ANote: The syntax for dig varies between Linux distributions. Use man dig to find the correct syntax for your particular distribution.4.    Review the output and verify that the ANSWER SECTION matches your resource record set.For example, if:Record name = mailserver1.example.comType = MXValue = inbound-smtp.mailserver1.example.comthen the correct dig output is:;; ANSWER SECTION:MAILSERVER1.EXAMPLE.COM    300    IN    MX    10    inbound-smtp.mailserver1.example.com.Method 3: Use the nslookup tool (for Windows)1.    Open the Windows Command Prompt.2.    Run the following command: nslookup. The output looks similar to this:C:\Users\Administrator>nslookupDefault Server: ip-172-31-0-2.ap-southeast-2.compute.internalAddress: 172.31.0.23.    Specify the resource record set type using set type=A:Note: You can also add any other required resource record type.set type=A4.    Specify one of the Route 53 name servers (NS) from the hosted zone (HZ) to query. In this example, enter server ns-1276.awsdns-31.org. The output looks similar to this:server ns-1276.awsdns-31.orgDefault Server: ns-1276.awsdns-31.orgAddresses: 2600:9000:5304:fc00::1205.251.196.2525.    Enter the record to query. For example, "aws.amazondomains.com". The query is done against the server specified earlier:aws.amazondomains.comServer: ns-1276.awsdns-31.orgAddresses: 2600:9000:5304:fc00::1205.251.196.2526.    The response is returned by the Route 53 NS:Name: aws.amazondomains.comAddress: 1.1.1.1Related informationChecking DNS responses from Route 53
Question: How do I edit my Amazon SNS topic's access policy?

I want to allow other AWS Identity and Access Management (IAM) entities to access to my Amazon Simple Notification Service (Amazon SNS) topic. How do I edit my Amazon SNS topic's access policy to grant the required permissions?ResolutionTo edit your Amazon SNS topic's access policy using the Amazon SNS console1.    Open the Amazon SNS console.2.    In the left navigation pane, choose Topics.3.    Choose your Amazon SNS topic's name.4.    Choose the Edit button.5.    Expand the Access policy - optional section.6.    Edit the access policy to grant the required permissions for your use case.Note: For more information on how to write access policies, see Overview of managing access in Amazon SNS.7.    Choose Save Changes.To edit your Amazon SNS topic's access policy using the AWS CLINote: 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.To modify, add, or remove permissions, run the following SetTopicAttributes command:Important: Replace <TopicARN> with your topic's Amazon Resource Name (ARN). Replace testpolicy.json with the path to your policy document.aws sns set-topic-attributes --topic-arn '<TopicARN>' --attribute-name 'Policy' --attribute-value file://testpolicy.json-or-To add permissions only, run the following AddPermission command:Important: Replace <TopicARN> with your topic's ARN. Replace AllowProdAccountsXXX with a unique identifier for the new policy statement. Replace AWS Account ID with the account IDs of the IAM entities that you want to allow access to specific actions. Replace Publish and Subscribe with the list of actions that you want to allow for the specified IAM entities.sns add-permission  --topic-arn '<TopicARN>' --label 'AllowProdAccountsXXX' --aws-account-id 'AWS Account ID' --action-name 'Publish' 'Subscribe'Related informationExample cases for Amazon SNS access controlActions, resources, and condition keys for Amazon SNS
Question: Why can't I delete an AWS Config rule?

I can't delete my AWS Config rule, or I receive an error similar to the following:"An error has occurred with AWS Config."ResolutionTo troubleshoot this issue, check the following:The AWS Identity and Access Management (IAM) entity has permissions for the DeleteConfigRule API actionOpen the IAM console, and then in the navigation pane choose Users or Roles.Choose the user or role that you used to delete the AWS Config rule, and expand Permissions policies.In the Permissions tab, choose JSON.In the JSON preview pane, confirm that the IAM policy allows permissions for the DeleteConfigRule API action.The IAM entity permission boundary allows the DeleteConfigRule API actionIf the IAM entity has a permissions boundary, be sure that it allows the DeleteConfigRule API action.Open the IAM console, and then in the navigation pane choose Users or Roles.Choose the user or role that you used to delete the AWS Config rule, expand Permissions boundary, and then choose JSON.In the JSON preview pane, confirm that the IAM policy allows permissions for the DeleteConfigRule API action.The service control policy (SCP) allows the DeleteConfigRule API actionOpen the AWS Organizations console using the management account for the organization.In Account name, choose the AWS account.In Policies, expand Service control policies and note the SCP policies that are attached.At the top of the page, choose Policies.Select the policy, and then choose View details.In the JSON preview pane, confirm that the policy allows the DeleteConfigRule API action.The rule isn't a service-linked ruleWhen you enable a security standard, AWS Security Hub creates AWS Config service-linked rules for you. You can't delete these service-linked rules using AWS Config, so the delete button is grayed out. To remove the AWS Config service-linked rules, see Disabling a security standard.No remediation actions are in progressYou can't delete AWS Config rules that have remediation actions in progress. Follow the instructions to delete the remediation action that is associated with that rule. Then, try deleting the AWS Config rule again.Important: Delete only remediation actions that are in failed or successful states.If the remediation action fails to delete, see How can I resolve the error "NoSuchRemediationConfigurationException" or "unexpected internal error" when trying to delete a remediation action in AWS Config?Related informationPermissions boundaries for IAM entitiesWhat's the difference between an AWS Organizations service control policy and an IAM policy?Service-linked AWS Config rulesManaging your AWS Config rules
Question: Why is my Reserved Instance showing as "Retired" in the console?

I'm not getting the billing benefit of a Reserved Instance (RI), and the RI is displayed as "Retired" in the console.

ResolutionRIs appear as retired in the Billing and Cost Management console for the following reasons:The RI term expired. After the term expires, you no longer receive the billing benefit or capacity reservation, and the RI is marked as retired in the console.The upfront charge for the RI wasn't processed successfully, and a new billing period has started. If the upfront charge for the RI isn't processed successfully, the charge remains in the payment-pending state until it's retried successfully. If the charge is in the payment-pending state and a new billing period starts, then the RI moves to the retired state, and the upfront charge can't be retried.The RI was modified. When an RI is modified, the old RI is marked as retired in the console.You sold the RI on the RI Marketplace. After the RI is sold, it is marked as retired in the console.RIs in the retired state can't be activated, but you can purchase a new RI with the same configuration.

Related informationAmazon EC2 Reserved InstancesAmazon RDS Reserved Instances
Question: Why isn't CloudFront serving my domain name over HTTPS?

I associated an SSL certificate with my Amazon CloudFront distribution, but I can't access my domain name over HTTPS. Why?ResolutionTo resolve problems with accessing your domain name over HTTPS, check the following:Your SSL certificate's domain name must be added as an alternate domain name (CNAME) in your CloudFront distribution's settings. For more information, see Using custom URLs for files by adding alternate domain names (CNAMEs).The domain name of the SSL certificate must be consistent with the domain name associated with the CloudFront distribution. For example, if you issue an SSL certificate for *.example.com, then the CloudFront distribution will support domain names such as abc.example.com or 123.example.com. However, an SSL certificate for *.example.com won't support domain names such as abc.123.example.com. To use abc.123.example.com as a domain name, you need an SSL certificate for either *.123.example.com or abc.123.example.com.If you're getting cipher or TLS version mismatch errors, verify that your client is using supported SSL or TLS protocols and ciphers. This allows communication between viewers and CloudFront.Verify that the status of your CloudFront distribution is Deployed. If the status is still InProgress, then you might not be able to access the domain name because data is still propagating across edge locations.If you recently updated your SSL certificate on AWS Certificate Manager, then verify that the certificate renewal status is Success. It might take several hours for the certificate renewal process to complete. For more information, see I renewed my Amazon-issued SSL certificate or reimported my certificate to ACM. Why does CloudFront still show the old certificate?For more information on troubleshooting SSL errors, see SSL/TLS negotiation failure between CloudFront and a custom origin server.

Related informationUsing HTTPS with CloudFront
Question: How can I copy data to and from Amazon EFS in parallel to maximize performance on my EC2 instance?

I have a large number of files to copy or delete. How can I run these jobs in parallel on an Amazon Elastic File System (Amazon EFS) file system on my Amazon Elastic Compute Cloud (Amazon EC2) instance?Short descriptionUse one of the following tools to run jobs in parallel on an Amazon EFS file system:GNU parallel – For more information, see GNU Parallel on the GNU Operating System website.msrsync – For more information, see msrsync on the GitHub website.fpsync – For more information, see fpsyncon the Ubuntu manuals website.

ResolutionGNU parallel1.    Install GNU parallel.For Amazon Linux and RHEL 6:$ sudo yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm$ sudo yum install parallel nload -yFor RHEL 7:$ sudo yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm$ sudo yum install parallel nload -yFor Amazon Linux 2:$ sudo amazon-linux-extras install epel$ sudo yum install nload sysstat parallel -yFor Ubuntu:$ sudo apt-get install parallel2.    Use rsync to copy the files to Amazon EFS.$ sudo time find -L /src -type f | parallel rsync -avR {} /dstor$ sudo time find /src -type f | parallel -j 32 cp {} /dst3.    Use the nload console application to monitor network traffic and bandwidth.$ sudo nload -u Mmsrsyncmsrsync is a Python wrapper for rsync that runs multiple rsync processes in parallel.Note: msrsync is compatible only with Python 2. You must run the msrsync script using Python version 2.7.14 or later.1.    Install msrsync.$ sudo curl -s https://raw.githubusercontent.com/jbd/msrsync/master/msrsync -o /usr/local/bin/msrsync && sudo chmod +x /usr/local/bin/msrsync2.    Use the-p option to specify the number of rsync processes that you want to run in parallel. ReplaceX with the number of rsync processes. The P option shows the progress of each job.$ sudo time /usr/local/bin/msrsync -P -p X --stats --rsync "-artuv" /src/ /dst/fpsyncThe fpsync tool synchronizes directories in parallel using fpart and rsync. It can run several rsync processes locally or launch rsync transfers on several nodes (workers) through SSH.For more information on fpart, see fpart on the Ubuntu manuals website.1.    Enable the EPEL repository, and then install the fpart package.For Amazon Linux and RHEL 6:$ sudo yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm$ sudo yum install fpart -yFor RHEL 7:$ sudo yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm$ sudo yum install fpart -yFor Amazon Linux 2:$ sudo amazon-linux-extras install epel$ sudo yum install fpart -yFor Ubuntu:$ sudo apt-get install fpartNote: In Ubuntu, fpsync is part of the fpart package.2.    Use fpsync to synchronize the /dst and /src directories. Replace X with the number of rsync processes that you want to run in parallel.$ sudo fpsync -n X /src /dst
Question: Why are my mobile text message (SMS) charges higher than expected from Amazon SNS and Amazon Pinpoint?

I was charged more than I expected for mobile text messaging (SMS) through Amazon Simple Notification Service (Amazon SNS) and Amazon Pinpoint. Why are my SMS charges higher than expected? Also, what's the best way to calculate my required SMS spending quota for Amazon SNS and Amazon Pinpoint?ResolutionAmazon SNS and Amazon Pinpoint SMS charges can be higher than expected if messages exceed the message parts per second (MPS) limits.For more information, see SMS character limits in Amazon Pinpoint. Also, Publishing to a mobile phone in the Amazon SNS Developer Guide.To calculate your required SMS spending quota for Amazon SNS and Amazon PinpointFollow the instructions in the Calculate your required SMS spending quota section of the following article: How do I request a spending limit increase for SMS messages in Amazon SNS?Note: For Amazon SNS, you can subscribe to daily SMS usage reports to monitor your SMS deliveries. For Amazon Pinpoint, you can activate event streams to Amazon Kinesis to monitor your SMS deliveries. For more information, see SMS events in the Amazon Pinpoint Developer Guide.

Related informationAmazon Pinpoint pricingWorldwide SMS pricing
Question: How do I resolve "EC2 is out of capacity" or "The requested number of instances exceeds your EC2 quota" errors in Amazon EMR?

My Amazon EMR cluster fails to launch, and I get one of these error messages:"EC2 is out of capacity""The requested number of instances exceeds your EC2 quota"Resolution"EC2 is out of capacity"This error means that AWS doesn't have enough available On-Demand Instance capacity to create the Amazon Elastic Compute Cloud (Amazon EC2) instances that you specified for the EMR cluster. To resolve the issue, try the following:Specify a different instance type for the EMR cluster. A different instance type might have more available capacity.Launch your cluster in a different Availability Zone. Each Availability Zone has its own capacity.Wait a few minutes, and then try to launch the EMR cluster again. Capacity shifts frequently."The requested number of instances exceeds your EC2 quota"This error means that the number of instances that you specified for the EMR cluster exceeds a service quota. To view your Amazon EC2 service quotas, open the Amazon EC2 console and then choose Limits from the navigation pane. Keep the following in mind:Amazon EC2 service quotas are unique to each Region.Only running instances count toward your service quotas.In addition to the limit on the total number of running instances, each instance type has its own limit. For example, you might be limited to 10 running a1.4xlarge instances and 20 total running instances in US East (N. Virginia).If you need more Amazon EC2 resources, request a service quota increase. Requests are subject to review by AWS engineering teams.

Related informationInsufficient instance capacityHow do I increase the service quota of my Amazon EC2 resources?Configure Amazon EC2 instances
Question: Why did I get the error "The snapshot is currently in use by an AMI" when trying to delete my EBS snapshot?

When I try to delete an Amazon Elastic Block Store (EBS) snapshot, I receive an error similar to the following:"snap-xxxxxxxx: The snapshot snap-xxxxxxxx is currently in use by ami-xxxxxxxx"ResolutionNote: 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.EBS-backed Amazon Machine Images (AMIs) include EBS snapshots. If you try to delete an EBS snapshot associated with an active AMI, you receive this error.Note: Public snapshots can't be deleted. If you try to delete a public snapshot, you receive an "unknown error occurred" message.Before you attempt to delete an EBS snapshot, make sure that the AMI isn’t currently in use. You can use AMIs with a variety of AWS services, such as Amazon Elastic Compute Cloud (Amazon EC2), AWS Auto Scaling, AWS CloudFormation, and more. If you delete an AMI that’s used by another service or application, the function of that service or application might be affected.If you no longer need the EBS snapshot or its associated AMI, deregister the AMI. Then, delete the EBS snapshot in the Amazon EC2 console:Note the AMI ID in the error message.Open the Amazon EC2 console, and from the navigation pane, choose AMIs.Choose the AMI noted in the error message, and then choose Deregister from the Actions menu.Note: If you don’t see the AMI that you’re looking for, check any other AWS Regions that you might have used.Delete the EBS snapshot by using the EC2 console or the AWS CLI.

Related informationDeregister your AMIDelete an Amazon EBS snapshot
Question: Why aren’t my stack-level tags propagating to resources in my CloudFormation stack?

My stack-level tags aren't propagating to resources in my AWS CloudFormation stack.

Short descriptionPropagation of stack-level tags to resources can vary by resource. CloudFormation supports propagation of stack-level tags only for resources with the Tags property. For a list of AWS resources and their property types, see AWS resource and property types reference.The following examples demonstrate the difference in stack-level tag propagation between a resource that supports the Tags property, and one that doesn't.

ResolutionResource that supports the Tags propertyThe resourceAWS::S3::Bucket supports the Tags property.Create a stack with the AWS::S3::Bucket resource and specify stack-level tags.After the stack is created, the S3 bucket resource has the propagated stack-level tags with the aws: prefix.Resource that doesn't support the Tags propertyAlthough the PutRule API allows you to specify tags, the AWS::Events::Rule resource doesn't support the Tags property.Create a stack with the AWS::Events::Rule resource and specify stack-level tags.After the stack is created, the Events Rule resource doesn't have the propagated stack-level tags.Search for or create an issue through GitHubIf a stack-level tag isn't propagating for a resource that supports the Tags property, then check the cloudformation-coverage-roadmap on the GitHub website to see if it's a known issue. If it isn't submitted as an issue, then choose New issue to create one.