VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I optimize costs with Amazon DynamoDB?

I want to optimize the cost of my Amazon DynamoDB workloads.

Short descriptionUse these methods to optimize the cost of your DynamoDB workloads:Use the AWS Pricing Calculator to estimate DynamoDB costs, in advance.Optimize read/write costs by selecting the correct capacity mode.Optimize storage costs by selecting the correct table class.Use cost allocation tags.

ResolutionUse the AWS Pricing Calculator to estimate DynamoDB costsUse the AWS Pricing Calculator for DynamoDB to estimate the cost of your DynamoDB workloads before you build them. This includes the cost of features such as on-demand capacity mode, backup and restore, Amazon DynamoDB Streams, and Amazon DynamoDB Accelerator (DAX).Optimize read/write cost by choosing the correct capacity mode for your DynamoDB tableOn-demand capacity modeOn-demand capacity mode is a good option if you have unpredictable application traffic. With on-demand mode, you pay only for what you use.If you configured a table as provisioned capacity mode, then you're charged for provisioned capacities even if you haven't consumed any I/O. So, if you have unused DynamoDB tables in your account, reduce the cost of your unused tables using on-demand mode.Provisioned capacity modeProvisioned capacity mode is a good option if you have predictable application traffic that is consistent or ramps gradually. Use this mode to forecast capacity requirements and control costs.Reserved capacityIf you can predict your need for DynamoDB read and write throughput in a given AWS Region, then use DynamoDB reserved capacity to reduce costs. DynamoDB reserved capacity allows you to make an upfront commitment on your base level of provisioned capacity. Reserved capacity isn't available for tables that use the DynamoDB Standard-Infrequent Access (DynamoDB Standard-IA) table class, or on-demand capacity.For more information on DynamoDB capacity modes, see Read/write capacity mode.Optimize storage cost by choosing the right table class for your DynamoDB tableUsing the DynamoDB Standard-IA table class can reduce costs for tables that store data that you don't access regularly. This is a good option if you require long-term storage of data that you don't use often, such as application logs, or old social media posts. But, be aware that DynamoDB reads and writes for this table class are priced higher than standard tables.For more information on DynamoDB table classes, see Table classes.Use cost allocation tags for DynamoDBTagging for DynamoDB provides fine-grained visibility into your DynamoDB bill. You can assign tags to your tables, and see cost breakouts per tab to help with cost optimization by usage. To learn more about cost allocation reports for DynamoDB, see Introducing cost allocation tags for Amazon DynamoDB .For information on Cost Allocation Tags, see Using cost allocation tags.For additional optimizing methods, see Optimizing costs on DynamoDB tables.

Related informationAmazon DynamoDB pricing
Question: How do I change my AWS Support plan?

I want to change my AWS Support plan.

ResolutionTo access the AWS Support Center, sign in with either of the following steps:Use your AWS account root user credentials-or-Use your AWS Identity and Access Management (IAM) user credentials with access permissions for AWS Support plans. For more information, see Manage access for AWS Support plans.To change your Support plan, do the following:1.    Open the AWS Support Center.You can view your current Support plan in the navigation pane.2.    Choose Change next to your current AWS Support plan.3.    (Optional) On the AWS Support plans page, compare the Support plans. For pricing information, see AWS Support plan pricing.Under AWS Support pricing example, choose See examples, and then choose one of the Support plan options to see the estimated cost.4.    Choose Review downgrade or Review upgrade for the plan that you want. Important: If you have an Enterprise On-Ramp or Enterprise Support plan, on the Change plan confirmation dialog box, choose Contact us. Fill in the form, and then choose Submit.5.    For Change plan confirmation, expand the support items to see the features included with the plan.Under Pricing, you can view the projected one-time charges for the new Support plan.6.    Choose Accept and agree.The changes take effect within 15 minutes. You see your new plan reflected in the Billing and Cost Management console within a few hours.Your previous paid AWS Support plan remains valid up to the point when you switch to a new one. The terms and conditions of the new plan start applying to the usage of your account immediately. For more information, see AWS Support plan pricing.For an explanation of how AWS Support plans are billed, see How am I billed for AWS Support?Related informationAWS SupportCompare AWS Support plansHow do I cancel my AWS Support plan?How do AWS Support plans work in an organization in AWS Organizations?
Question: What's the most effective way as an AWS reseller to bill my end customers?

As a reseller of AWS products, I want to use AWS tools to calculate bills for my end users.

ResolutionAs a reseller, it's a best practice to design your own specialized reporting and invoicing structures that match your business needs.You can use the AWS Cost and Usage report to help calculate bills for end users. It's a best practice to use cost allocation tags to identify the source of your costs.When you calculate bills for your end customers, make sure to use unblended rates. Blended rates are averages and aren't meant to reflect actual billed rates.

Related informationAWS OrganizationsConsolidated billing for AWS Organizations
Question: How do I change the email address for my registered domain in Route 53 if I lost access to my previous email account?

I can't access my previous email account. I want to update the email address for my registered domain in Amazon Route 53.

ResolutionOpen the Route 53 console.Choose Registered Domains.Select the name of the domain that you want to update the email address for.Choose Edit Contacts.Change the email address for only the registrant contact. Don't change the values for any of the domain contacts. You can change other values later in the process.Choose Save.If it's required for the top-level domain (TLD), then Amazon Route 53 sends a verification email to the new address. You must choose the link in the email to verify that the new email address is valid.If you don't verify the new email address, then Route 53 suspends the domain as required by ICANN. The domain status changes from OK to clientHold. For more information, see EPP Status Codes - clientHold on the ICANN website.Note: The email comes from one of the following email addresses based off of the TLD:.fr: nic@nic.fr.com.au and .net.au: noreply@emailverification.infoAll others: noreply@registrar.amazon.com or noreply@domainnameverification.net(Optional) To change other values for the registrant, administrative contacts, or technical contacts for the domain, return to step 1 and repeat the procedure.

Related informationUpdating contact information for a domainAmazon Route53 domain registration UpdateDomainContact (through API)
Question: My Auto Scaling API calls are getting throttled. What can I do to avoid this?

My application receives "Rate Exceeded" errors when calling to Amazon EC2 Auto Scaling, AWS Auto Scaling, or AWS Application Auto Scaling. What can I do to avoid this error?Short descriptionAll API calls can't exceed the maximum allowed API request rate per account and per Region. This includes API calls from the AWS Command Line Interface (AWS CLI) and the AWS Management Console. If API requests exceed the maximum rate, then you receive a "Rate Exceeded" error, and further API calls are throttled.Amazon EC2 Auto Scaling, AWS Auto Scaling, and AWS Application Auto Scaling each have their own API throttle buckets. This means that all Amazon EC2 Auto Scaling API calls have a single, shared API limit. Amazon EC2 Auto Scaling API calls don't affect the limit for AWS Application Auto Scaling APIs.To avoid the "Rate Exceeded" error and throttling, verify that your application is making only necessary calls.Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

ResolutionTo prevent or mitigate "Rate Exceeded" errors and throttling, try these solutions:Validate "describe" callsExcessive "describe" calls contribute to the total API requests measured against the allowed request rate. Verify your application to be sure that all "describe" calls are necessary, and consider solutions other than "describe" calls where possible. Consider using push notifications from Amazon EventBridge that are sent when instances change state, such as when they start a lifecycle hook.Check calls from third-party applicationsThird-party applications might make continuous calls to Auto Scaling in AWS. Verify your third-party applications to be sure that they're not making unnecessary calls.Implement error retries and exponential backoffsError retries and exponential backoffs can help limit the rate of API calls. Each AWS SDK implements automatic retry logic and exponential backoff algorithms. For more information, see Error Retries and exponential backoff in AWS.Request a service quota increase in the AWS Support CenterTo get a service quota increase, you must confirm that you validated your API call rate, as well as implemented error retries or exponential backoff methods. In your request, you must also provide the Region and timeframe related to the throttling issues.Avoid bursts of activityAvoid situations that cause bursts of API calls. For example, don't set all instances in an Amazon EC2 Auto Scaling group enable scale in protection when you launch them. Instead, enable this option by default on the group so that all instances have protection enabled by default.

Related informationExponential backoff and jitter
Question: How do I resolve "Execution failed due to configuration error: Illegal character in path" errors when creating an API Gateway API with a proxy resource?

I'm using an AWS CloudFormation template (or OpenAPI API definition) to create an Amazon API Gateway API with a proxy resource. When I try to create the API, I get the following error: "Execution failed due to configuration error: Illegal character in path." How do I resolve the error?Short descriptionIf a URL path parameter mapping for the proxy path parameter ({proxy+}) isn't defined, then API Gateway returns the following error:Execution failed due to configuration error: Illegal character in pathWithout a URL path parameter mapping defined for this parameter in the integration request, API Gateway evaluates the parameter as the literal string "{proxy+}". Because "{" isn't a valid character, API Gateway returns an error when this happens.To resolve the error, define the URL path parameter mapping for the proxy path parameter in the integration request by doing the following:Resolution1.    In the API Gateway console, choose the name of your API.2.    With the method selected in the Resources pane, choose Integration Request in the Method Execution pane.3.    In the Integration Request pane, verify that the Endpoint URL uses the correct proxy path parameter: {proxy}. (The greedy path variable without "+".) For example: http://example.com/{proxy}4.    Expand URL Path Parameters. Then, choose Add path and do the following:For Name, enter proxy. This corresponds to the parameter in the Endpoint URL.For Mapped from, enter method.request.path.proxy.Note: Here, proxy corresponds to the name of the request path as defined in the Method Request pane. This request path is added by creating a proxy resource named {proxy} or, for a greedy path variable, {proxy+}.5.    Choose the check mark icon (Create).Note: If you get an Invalid mapping expression specified error, update your AWS CloudFormation template or OpenAPI definition. Then, repeat the steps in this article.6.    Deploy your API.

Related informationSet up a proxy integration with a proxy resourceSet up request and response data mappings using the API Gateway consoleSet up an API integration request using the API Gateway console
Question: How do I associate multiple ACM SSL or TLS certificates with Application Load Balancer using CloudFormation?

I want to associate multiple AWS Certificate Manager SSL and TLS certificates with Application Load Balancer using AWS CloudFormation.

Short descriptionTo add a default SSL server for a secure listener, use the Certificates property for the resource AWS::ElasticLoadBalancingV2::Listener. This resource provides one certificate. To add more certificates, use AWS::ElasticLoadBalancingV2::ListenerCertificate. AWS::ElasticLoadBalancingV2::ListenerCertificate includes the Certificates parameter that accepts the list of certificates.

ResolutionUse the following CloudFormation template to create an Application Load Balancer listener with one default certificate:HTTPlistener:  Type: 'AWS::ElasticLoadBalancingV2::Listener'  DependsOn: ApplicationLoadBalancer  Properties:    DefaultActions:      - Type: fixed-response        FixedResponseConfig:          ContentType: text/plain          MessageBody: Success          StatusCode: '200'    LoadBalancerArn: >-      arn:aws:elasticloadbalancing:<Region>:<AccountID>:loadbalancer/app/TestACMELB/1032d48308c9b37f    Port: '443'    Protocol: HTTPS    Certificates:      - CertificateArn: >-          arn:aws:acm:<Region>:<AccountID>:certificate/cffb8a69-0817-4e04-bfb1-dac7426d6b90Use the following CloudFormation template to add multiple certificates to the Application Load Balancer listener:AdditionalCertificates:  Type: 'AWS::ElasticLoadBalancingV2::ListenerCertificate'  DependsOn: HTTPlistener  Properties:    Certificates:      - CertificateArn: >-          arn:aws:acm:<Region>:<AccountID>:certificate/c71a3c29-e79d-40e6-8834-650fe0d54a3f      - CertificateArn: >-          arn:aws:acm:<Region>:<AccountID>:certificate/fff1c1ba-3d97-4735-b3d5-9c5269b75db3    ListenerArn:      Ref: HTTPlistener
Question: How do I resolve the 403 "index_create_block_exception" or "cluster_block_exception" error in OpenSearch Service?

I tried to create an index or write data to my Amazon OpenSearch Service domain, but I received a "index_create_block_exception" or  "cluster_block_exception" error.

ResolutionFollow these troubleshooting steps for the type of ClusterBlockException error message that you received.index_create_block_exception{     "error": {          "root_cause": [{               "type": "index_create_block_exception",               "reason": "blocked by: [FORBIDDEN/10/cluster create-index blocked (api)];"          }],          "type": "index_create_block_exception",          "reason": "blocked by: [FORBIDDEN/10/cluster create-index blocked (api)];"     },     "status": 403}This error occurs because of a lack of storage space. To troubleshoot storage issues, see Lack of available storage space. This error also ocurrs because of a high JVM memory pressure. To troubleshoot high JVM memory pressure issues, see How do I troubleshoot high JVM memory pressure on my Amazon OpenSearch Service cluster?cluster_block_exception (cluster in read-only state){  "error" : {    "root_cause" : [      {        "type" : "cluster_block_exception",        "reason" : "blocked by: [FORBIDDEN/6/cluster read-only (api)];",      }    ],    "type" : "cluster_block_exception",    "reason" : "blocked by: [FORBIDDEN/6/cluster read-only (api)];",  },  "status" : 403}This error occurs when the read-only block is set to true. If quorum loss occurs and your cluster has more than one node, then OpenSearch restores quorum and places the cluster into a read-only state. You can use GET _cluster/settings to verify if the read-only state is set to true.For more information, see Cluster in read-only state.cluster_block_exception (warm indexes){ "error": {   "root_cause": [{      "type": "cluster_block_exception",      "reason": "blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"    }],    "type": "cluster_block_exception",    "reason": "blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"  },  "status": 403}This error occurs when you try to add, update, or delete individual documents in the warm indices. Warm indices are read-only unless you return them to hot storage. You can query the indices and delete them only if they're present in the UltraWarm storage. To update documents, you must migrate the index from UltraWarm storage to hot storage.For more information, see Returning warm indexes to hot storage.

Related informationHow can I scale up or scale out an Amazon OpenSearch Service domain?
Question: Why is it taking a long time to scale up my ElastiCache for Redis cluster?

Why is it taking a long time to scale up my Amazon ElastiCache for Redis (Cluster Mode Disabled) cluster?ResolutionYou can scale your Redis cluster based on the current demand. When you scale up your cluster, a new node type is created. After the new node is created, the data is replicated from the existing node to the new node type. The time taken to complete the replication depends on the following factors:The amount of data in the cluster: If there's a lot of data in the cluster, then it takes more time to replicate the data to the new node.The node type of the cluster: If the existing node type doesn't have enough throughput, there might be an increase in the time it takes to scale the cluster.The ongoing traffic on the Redis cluster: If the existing node type is overwhelmed due to incoming traffic, then the time it takes to replicate the data increases. It's a best practice to scale when the Redis cluster isn't in heavy use so that the scaling process completes faster.

Related informationAuto Scaling ElastiCache for Redis clusters
Question: How do I troubleshoot audio and microphone issues in Amazon WorkSpaces for Windows?

I'm unable to hear the audio or use a microphone in PCoIP-based Amazon WorkSpaces for Windows.

ResolutionAudio issuesTo troubleshoot audio issues in your WorkSpaces application, do the following:Perform initial checksBe sure that you're running the latest WorkSpaces client application.Reboot your Workspace to check if the issue is resolved.Be sure that the round-trip time for your WorkSpace client is less than 100 ms. If the RTT is between 100 ms and 250 ms, then the user can access the WorkSpace, but the performance is degraded. To check the RTT to the various AWS Regions from your location, use the Amazon WorkSpaces Connection Health Check.Install Teradici Virtual Audio Driver on your WorkSpaceIf you still have audio issues after the initial checks, check if the Teradici Virtual Audio Driver is installed on the WorkSpace. To verify, open Device Manager on the WorkSpace where you have issues in your Windows PC. Then, choose (double-click) Sound, video and game controllers. The driver must be listed in this section. If the driver isn't listed in this section, then use these steps to install the driver:Open Device Manager on the WorkSpace.Choose Action, and then choose Add legacy hardware.In the Welcome to Add Hardware Wizard window, choose Next.Select Install the hardware that I manually select from a list (Advanced), and then choose Next.Choose Show All Devices, and then choose Next.Choose Have Disk.Under Copy manufacturer's files from, choose Browse, and select the following file: C:\Program Files\Teradici\PCoIP Agent\drivers\TeraAudio.Choose OK.Choose Teradici Virtual Audio Driver, and then choose Next.Choose Finish.Reboot the WorkSpace. The driver must be listed under the Sound, video and game controllers section in Device Manager.Configure Teradici Virtual Audio Driver as the active playback deviceVerify that the Teradici Virtual Audio Driver is configured as the active Playback device by following these steps:Connect to the WorkSpace.In the system tray, right-click on the speaker icon, and then choose Sounds.Choose the Playback tab.Check if Teradici Virtual Audio Driver has a green checkmark.If the driver doesn't have a green checkmark, then follow these steps:Right-click anywhere on the Playback tab, and then select Show disabled drivers.Right-click on Teradici Virtual Audio Driver, and then select Enable.You can now listen to the audio inside the WorkSpace.Microphone issuesWindows Server 2019-based WorkSpaces include new privacy settings that disable remote access to microphones, by default. Your applications can't detect an audio device unless you provide the required access in Windows Settings.In your Windows Workspace, Choose the Start menu, and then choose Settings.Choose (double-click) Privacy, and then under App permissions, choose Microphone.Under Allow apps to access your microphone, select On.Your microphone is now detected inside the WorkSpace. No reboot of WorkSpace is required.
Question: How can I confirm that my AWS infrastructure is GDPR-compliant?

I want to learn more about how the General Data Protection Regulation (GDPR) affects AWS customers.

ResolutionFor an overview of how the GDPR affects AWS customers, see All AWS services GDPR ready.For FAQs, whitepapers, and service-specific usage instructions that can help you comply with the GDPR, see General Data Protection Regulation (GDPR) center.To comply with GDPR contractual obligations, AWS offers a GDPR-compliant Data Processing Addendum (GDPR DPA). The AWS GDPR DPA is incorporated into the AWS Service Terms. The DPA applies automatically to all customers globally who require it to comply with the GDPR.If you have additional compliance questions about AWS or your AWS infrastructure, use the form at AWS Compliance contact us to request additional information.

Related informationAWS and the General Data Protection Regulation (GDPR)AWS Compliance