VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How is the pricing benefit of a Savings Plan applied across an organization's consolidated bill?

How is the pricing benefit of a Savings Plan applied in an organization's consolidated billing family?ResolutionSavings Plans can be purchased in any account within the organization's consolidated billing family.Savings Plans apply to accounts in an organization's consolidated billing family depending upon whether sharing is turned on or off for the accounts. By default, sharing for all accounts in an organization is turned on. The management account of an organization can change this setting by turning off sharing for an account.If Savings Plans sharing is turned on for an account in an organization, then:At least one account in the organization's consolidated billing family must have AWS compute usage for the plan type of the Savings Plans to apply to the management account's bill.Savings plans first apply to usage in the purchasing account. Then, if there is any unused hourly commitment, the Savings Plans apply towards other accounts in the organization that have sharing turned on. This happens automatically and is applied to usage with the largest calculated savings.Savings Plans purchased on a member account won't apply to the consolidated bill if the member account leaves the organization or is removed from the organization by the management account. For more information, see Before removing an account from an organization.If Savings Plans sharing is turned off for an account in an organization, then:Savings Plans apply only to the account that purchased the Savings Plans.Savings Plans from other accounts in the organization's consolidated billing family don't apply.The charges accrued on that account are still added to the organization's consolidated bill and are paid by the management account.Capacity reservations can be shared within an AWS organization at no additional cost. For more information, see Work with shared Capacity Reservations.Reserved instances can also be applied across an organization's consolidated bill. For more information, see How is the pricing benefit of a Reserved Instance applied across an organization's consolidated bill?Related informationConsolidated billing for AWS OrganizationsUnderstanding consolidated bills
Question: How can I tag my AWS resources to divide up my bill by cost center or project?

I want to track my Amazon Web Services (AWS) usage and spending across different projects, cost centers, or development environments.

ResolutionTags are key-value pairs that let you organize your AWS resources into groups.To locate and tag resources, use the Tag Editor console. For instructions on tagging, see Finding resources to tag.Note: Not all resources support tags. For the list of resources that can be tagged, see Supported resources.You can use tags to:Visualize information about tagged resources in one place in conjunction with AWS resource groups.View billing information using AWS Cost Explorer and AWS Cost and Usage Reports.Send notifications about spending limits by Configuring a budget action.Use logical groupings of your resources that make sense for your infrastructure or business.For example, you can organize your resources by:ProjectCost centerDevelopment environmentApplicationDepartmentUse user-defined cost allocation tags to create cost allocation tags for your use case.

Related informationUsing AWS cost allocation tags
Question: How do I sell an Amazon EC2 Reserved Instance on the Reserved Instance Marketplace?

I have an active Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instance (RI) that I no longer need and want to sell.

ResolutionIf you no longer need an RI, you can sell it to another Amazon EC2 user on the Amazon EC2 Reserved Instances Marketplace. The Reserved Instance Marketplace allows you to set a price for the remainder of the RI term. If another EC2 user purchases the instance, then you receive most of the proceeds from the purchase. The remainder of the term for the sold RI is transferred to the buyer's account.Note: You must have a US bank account to sell your RIs on the Reserved Instance Marketplace.For an overview of the Reserved Instance Marketplace, including details and limitations, see Reserved Instance Marketplace.For information about becoming a seller on the Reserved Instance Marketplace, see Register as a seller.

Related informationReserved Instances
Question: How do I grant an IAM user access to file support cases?

An AWS Identity and Access Management (IAM) user on my AWS account can't file support cases.

ResolutionBy default, IAM users on an AWS account can't access services and functions unless the AWS account root user explicitly grants access. You can grant permission to IAM users to access the AWS Support Center by attaching a managed policy to the IAM user, group, or role.Follow the instructions to use a managed policy as a permissions policy for an identity (AWS Management Console), and then choose the AWSSupportAccess policy.The following example policy grants access to AWS Support but restricts the IAM user from resolving cases:{   "Version": "2012-10-17",   "Statement": [   {      "Effect": "Allow",      "Action": "support:*",      "Resource": "*"   },   {       "Effect": "Deny",       "Action": "support:ResolveCase",       "Resource": "*"    }]}For additional information, see Access permissions for AWS Support.Be sure that the IAM users have permissions to view and access AWS services before contacting AWS Support. For instructions on updating an existing IAM policy, see Managing IAM policies.Note: AWS Support is limited in what they can discuss with IAM users. However, they can speak with the AWS account root user about all the details related to an account and its resources.

Related informationControlling access to AWS resources using policiesPolicies and permissions in IAM
Question: How can I increase my ACM service quota?

I want to increase my service quota for AWS Certificate Manager (ACM). How can I do this?ResolutionYou can request an increase to ACM service quotas (formerly called service limits) by any of these options:AWS Support dashboardService Quotas dashboardAWS Command Line Interface (AWS CLI)Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.AWS Support dashboardOpen the AWS Support dashboard.Choose Service Limit Increase.In Case details, Choose the Limit type dropdown list, and then choose Certificate Manager.Important: ACM service quotas affect one Region at a time. You must request service quota increases in each AWS Region where you need more resources.(Optional) To request multiple service quota increases at the same time, complete one quota increase request in the Requests section, and then choose Add another request.Choose Submit.Service Quotas dashboardOpen the Service Quotas dashboard.In the navigation pane, choose AWS services.In AWS services, enter AWS Certificate Manager (ACM).In Quota name, choose the required service quota.Choose Request quota increase.In Change quota value, enter the value, and then choose Request.AWS CLIRun the get-service-quota command to check the applied quota value for the service you want to increase.Request a quota increase using the request-service-quota-increase command.Run the get-requested-service-quota-change command to check the status of a pending request.Note: It's a best practice to proactively monitor and manage your service quotas to be sure that you have enough quotas to support your usage requirements. Requests for service quota increases are subject to review by AWS engineering teams. Service quota increase requests aren't processed immediately after you submit a request. You receive an email after your request is processed.For more information, see Creating a service quota increase.

Related informationQuotasRequesting a quota increaseAWS Certificate Manager endpoints and quotas
Question: How do I delete a recovery point from a backup vault in AWS Backup?

I want to delete a recovery point from my backup vault in AWS Backup.

ResolutionPrerequisitesTo delete a recovery point from a backup vault in AWS Backup, you must have the following AWS Identity and Access Management (IAM) permission:backup:DeleteRecoveryPointVerify that there isn't an access policy configured on the backup vault that denies deletion of recovery points.The following is an example policy that restricts users from deleting any recovery point from the backup vault:{  "Version": "2012-10-17",  "Statement": [    {      "Sid": "statement ID",      "Effect": "Deny",      "Principal": "*",      "Action": "backup:DeleteRecoveryPoint",      "Resource": "*"    }  ]}Delete a recovery point using the consoleTo manually delete recovery points using AWS Backup console, do the following:Open the AWS Backup console.In the navigation pane, choose Backup vaults. Then, choose backup vault where you store the backups.Choose a recovery point.Choose the Actions dropdown, and then choose Delete.Note: You can select multiple recovery points if you want to delete multiple backups.To delete the recovery points, enter delete, and then choose Delete recovery points. AWS Backup submits your recovery points for deletion and displays a progress bar. Don't navigate away from this page during the submission process.Choose View progress to review the deletion status of each backup. If a deletion status is Failed or Expired, then you can choose that status to see the reason. You can also choose to Retry failed deletions.Delete a recovery point programmaticallyTo delete recovery points using an AWS Command Line Interface (AWS CLI) command, use the DeleteRecoveryPoint API.The following is an example of the DeleteRecoveryPoint command:Note: Replace name with your backup vault name and arn with the ARN of the recovery point that you want to delete.aws backup delete-recovery-point --backup-vault-name <name> --recovery-point-arn <arn>To delete all the recovery points from a backup vault, use the following command:Note: Replace name with your backup vault name.aws backup list-recovery-points-by-backup-vault  --backup-vault-name <name> --output json --query 'RecoveryPoints[].[RecoveryPointArn]' | jq -r '.[] | "--recovery-point-arn '\\\"'" + .[0] + "'\\\"'" + .[1]' |  xargs -L1 aws backup delete-recovery-point --backup-vault-name  <name>Related informationDeleting backups
Question: How are charges for Amazon EBS volumes calculated on my bill?

I want to know how Amazon Elastic Block Store (Amazon EBS) volumes that are associated with my account are charged on my bill.

ResolutionAmazon EBS volumes are billed by the gigabyte-month (GB-month). The GB-month is a measure of how many gigabytes of EBS storage that you provision to your account. It's also a measure of how long you provision the EBS storage to your account. A GB-month is 1 GB of storage for one month.In a 30-day month, you're billed for one GB-month in the following scenarios:You provision a 1-GB volume for 24 hours.You provision a 1-GB volume for 720 hours (the number of hours in 30 days).You're billed for the total amount of storage that you provision to your account, even if you don't use the storage. For example, if you provision a 100-GB EBS volume for a month, then you're billed for 100 GB-month of EBS storage. Even if you store only 10 GB of data on that volume, you're billed for 100 GB-month of EBS storage.For more information, see Amazon EBS pricing.To minimize the amount that you're billed for Amazon EBS storage, complete the following steps:Create snapshots of any volumes that you're not actively using.Delete snapshots that you no longer need.Audit your EBS volumes to see if you're using most of the storage in the volume. If you're not using most of your volume's storage, then migrate your data to smaller EBS volumes.

Related informationHow am I billed for my Amazon EBS snapshots?Why am I being charged for Amazon EC2 when all my instances are terminated?
Question: How do I associate a static public IP address with my EC2 Windows or Linux instance?

The auto-assigned public IP address associated with my Amazon Elastic Compute Cloud (Amazon EC2) instance changes every time I stop and start the instance. How can I assign a static public IP address to my Windows or Linux EC2 instance that doesn't change when I stop/start the instance?Short descriptionAn Elastic IP address is a static public IPv4 address associated with your AWS account in a specific Region. Unlike an auto-assigned public IP address, an Elastic IP address is preserved after you stop and start your instance in a virtual private cloud (VPC).You can associate an Elastic IP address with your EC2 instance at any time using one of the following tools:The Amazon EC2 consoleThe AWS Command Line Interface (AWS CLI)AWS Tools for Windows PowerShellKeep the following points in mind when working with static IP addresses:If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.You can't retain or reserve the current public IP address assigned to the instance using auto-assigned public IP address.You can't convert an auto-assigned public IP address to an Elastic IP address.There is a default limit of 5 Elastic IP addresses per Region per AWS account. For more information about limits and how to request an increase, see Elastic IP address limit.

ResolutionTo allocate and associate an Elastic IP address with your EC2 Windows or Linux instance, follow these steps:Allocate an Elastic IP address from either Amazon’s pool of public IPv4 addresses or a custom IP address pool that you bring to your AWS account.Associate the Elastic IP address with a running instance.You can also disassociate an existing Elastic IP address, and then re-associate it with a different instance.

Related informationElastic IP addressesAmazon EC2 instance IP addressingStop and start your instance
Question: How many resources can Shield Advanced protect?

I want to know how many resources AWS Shield Advanced can protect.

ResolutionShield Advanced protections are turned on only for resources that you explicitly specified in Shield Advanced. You can also protect resources through an AWS Firewall Manager Shield Advanced policy.By default, the maximum number of protected resources for each resource type that Shield Advanced can protect is 1000 per account. To request a quota increase, see Shield Advanced quotas.For more information, see AWS Shield Advanced protections by resource type.

Related informationAWS Shield Advanced capabilities and optionsHow can I simulate a DDoS attack to test Shield Advanced?
Question: Why can't I retrieve data points for CloudWatch metrics in the CloudWatch console?

Why can't I retrieve data points for Amazon CloudWatch metrics in the CloudWatch console?ResolutionThere are several reasons that a data point retrieved from the default or custom metric might be missing or incorrect.To troubleshoot missing data points, follow these steps:Confirm that the metric namespace, metric name, and key-value pairs for the dimension used to retrieve the metric are correct.If the data points to a metric are pushed with a specific unit, confirm that the unit for retrieving the metric is the same. Optionally, you can leave the unit blank.If the metric is a high-resolution metric (pushed at a sub one-minute interval), confirm that the data points to the metric are pushed with the --storage resolution parameter set to 1. Without this configuration, CloudWatch doesn't store the sub-minute data points and aggregates them into one-minute data points. In these cases, data points for a sub-minute period aren't retrievable.Remember that the frequency of pushing the data points to the metric determines the highest granularity of the metric. For example, setting the period as one minute for a metric where the data point is pushed every five minutes doesn't retrieve the data point every minute. The value of the data point still represents the five-minute duration.If the data to an event-driven metric is pushed by an AWS service, check the source service's documentation. Confirm when the service pushes data points to the metric and whether it's expected for the metric to have missing data points.For custom metrics, check the source (the unified CloudWatch agent or the custom script that pushed the metric) logs. Confirm if the source is operating as expected for the specific duration. For more information, see Troubleshooting the CloudWatch agent.Check the metric retention periods while retrieving the data points from CloudWatch. If the data points to a metric are pushed at a sub-minute interval, these data points can be retrieved only as-is for three hours. After three hours, the sub-minute data points are aggregated into one-minute data points that can be retrieved for 15 days. After 15 days from the data ingestion time, these one-minute data points are aggregated into five-minute data points that can be retrieved for 63 days. After 63 days from the data ingestion time, these five-minute data points are aggregated into one-hour data points that are stored for 455 days. After 455 days (15 months), older data is deleted from CloudWatch and is no longer retrievable.For example, consider a scenario where a single value was pushed to the metric every minute as follows:TimestampValue1:0031:0141:0221:0311:045For 15 days, these one-minute values are retrievable. After 15 days, these values are aggregated into one data point for a five-minute period. The value displayed depends on the statistic. For example, for the previous example values:Statistic selected for 1:00-1:05 data point (five-minute period)ValueSum15Average3Minimum1Sample count5Maximum5
Question: How can I use Route 53 to access an internal version of my website using the same domain name which is also used publicly?

How can I use Amazon Route 53 to access an internal version of my website using the same domain name that is used publicly?Short descriptionYou can use Route 53 to configure split-view DNS, also known as split-horizon DNS. You can use this feature when you want to maintain internal and external versions of the same website or application.

ResolutionYou can maintain both a private and public hosted zone with the same domain name for split-view DNS with Route 53. The following instructions assume you already own a domain and have the rights to make changes to the NS records for that domain. Route 53 private hosted zones require DNS queries sourced from the Amazon Virtual Private Cloud (Amazon VPC) DNS server rather than a custom DNS server.Make sure that DNS resolution and DNS hostnames are turned on for the source Amazon VPC.Note: DNS hostnames are turned on for default VPCs and VPCs that you create using the VPC wizard in the VPC console.Create a public hosted zone that matches the name of the domain that you purchased.Populate the public hosted zone with the required records.Update your registrar's NS records with the name servers provided in your public hosted zone.Create a private hosted zone that matches the name of the public hosted zone. Attach the private hosted zone to the Amazon VPC where you want to resolve the domain internally.Note: The private zone lookup takes place within the VPC.Populate the private hosted zone with the required records.Note: The public zone isn't queried if a record doesn't exist in the private zone.DNS queries respond with answers based on the source of the request. From within the Amazon VPC, answers come from the private hosted zone, while public queries return answers from the public hosted zone.

Related informationConfiguring Amazon Route 53 as your DNS service
Question: Why am I being charged for AWS KMS keys?

I have a charge for AWS KMS keys on my AWS bill.

ResolutionAWS KMS keys are used with the AWS Key Management Service (AWS KMS). You're billed for all active or deactivated KMS keys on your account. You're also charged for the API requests that are made to the AWS Key Management Service (AWS KMS) out of the AWS Free Tier usage.To see a list of KMS keys on your account, choose Customer-managed keys in the AWS KMS console. To stop the charges for the KMS key, delete the KMS key.Warning: If you delete the KMS key, then any services that you configure to use the KMS key as part of their function are affected.

Related informationAWS Key Management Service pricingAWS Key Management Service FAQs
Question: How are my connections handled when I reboot my Amazon for RDS instance with or without a failover?

I want to know how my connections are handled when I reboot my Amazon Relational Database Service (Amazon RDS) instance with or without a failover.

ResolutionYou might need to reboot your DB instance, usually for maintenance reasons. For example, if you make certain modifications or change the DB parameter group associated with the DB instance, then you must reboot the instance for the changes to take effect. Rebooting a DB instance restarts the database engine service. Rebooting results in a momentary outage of the instance, during which the instance status is set to rebooting. For more information, see Rebooting a DB instance.When you reboot your Amazon RDS instance, you see the following events in the Logs & Events section on the Amazon RDS console:Rebooting a Single-AZ Amazon RDS instance:October 05, 2021, 4:31:22 AM UTC                          DB instance restartedReboot a Multi-AZ RDS instance without a failover:October 18, 2021, 8:12:03 PM UTC                          DB instance restartedOctober 18, 2021, 8:11:52 PM UTC                          DB instance shutdownRebooting a Multi-AZ RDS instance with a failover:October 05, 2021, 2:15:33 PM UTC                          DB instance restartedOctober 05, 2021, 2:15:18 PM UTC                          The user requested a failover of the DB instanceOctober 05, 2021, 2:15:18 PM UTC                          Multi-AZ instance failover completedOctober 05, 2021, 2:13:18 PM UTC                          Multi-AZ instance failover startedRebooting a Single-AZ Amazon RDS for Microsoft SQL Server instance:October 05, 2021, 4:31:22 AM UTC                         DB instance restartedRebooting a Multi-AZ RDS for Microsoft SQL Server instance without a failover:October 05, 2021, 4:32:22 AM UTC                         DB instance restartedOctober 05, 2021, 4:32:20 AM UTC                         DB instance restartedRebooting a Multi-AZ RDS for Microsoft SQL Server instance with a failover:October 05, 2021, 2:49:18 PM UTC                         Multi-AZ failover to standby complete - DNS propagation may take a few minutesOctober 05, 2021, 2:49:11 PM UTC                         Multi-AZ instance failover completedOctober 05, 2021, 2:48:42 PM UTC                         Multi-AZ instance failover startedOctober 05, 2021, 2:48:33 PM UTC                         DB instance restartedWhen you reboot your DB instance either with or without a failover, the instance is shut down. Therefore, you must clean up and re-establish any existing connections to your DB instance. It's a best practice to implement database connection retry at the application layer. Rebooting with a failover is beneficial for simulating the failure of a DB instance for testing purposes or for restoring operations to the original Availability Zone after the failover.
Question: How do I resolve HTTP 400 “AccessDeniedException” errors from Amazon SNS?

When my Amazon Simple Notification Service (Amazon SNS) topic tries to publish messages to another AWS resource, I get an HTTP 400 "AccessDeniedException" error. How do I resolve the error?Resolution1.    Update your resource's AWS Identity and Access Management (IAM) resource-based policy to allow Amazon SNS access to the resource. For more information, see Editing IAM policies in the AWS IAM user guide.2.    Verify that your resource's IAM resource-based policy doesn’t include any Deny statements that explicitly deny your Amazon SNS topic access to the resource.Note: AWS Lambda function IAM resource-based policies don't include the option to add an explicit deny statement.

Related informationAccess management for AWS resourcesAmazon SNS event destinations