VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: Why isn't my credit or promotional code applying to my AWS bill?

I added a credit or promotional code to my account, but it hasn't applied to my AWS usage. Why?ResolutionTo view the active credits on your AWS account, do the following:Open the Billing and Cost Management console.Choose Credits in the navigation pane.Common reasons that credits don't seem to be applied to the usage on your account include the following:The code isn't active on your account.The code has expired.You added the code to your account after the current billing cycle ended. The billing cycle begins on the first day of each month. Check the start date of the promotional credit. AWS applies the credits to your usage starting from the calendar month of the credit start date.The code has been used up already. Check your bill for previous months to make sure that the credit hasn't already been used up.The code doesn't apply to services that you're being billed for. Each credit applies to specific AWS services. The Applicable Products line in the Credits pane shows you what services the code applies to.The code was applied recently. Recently added credit codes might take a few hours to be visible in the Billing and Cost Management console. Credits might take up to a week to be applied to your bill on the Bills page of the Billing and Cost Management console.You were recently added to a new organization, and the credits are still applying to your former organization. Credits can only apply to one account per billing cycle. For more information, see How are credits and promotions calculated in an organization in AWS Organizations?If you recently joined an organization, any credits applied the month you join won't apply to that month's bill. Credits applied in the month that you join will apply to the next month's bill.Example: If you joined an organization on March 15 and applied a credit the same day, then the credit has the start date of March 1. Because the credit start date is prior to the date you joined the organization, the credit is applied to your April bill.Credit sharing isn't turned on for your organization. To share credits among all the accounts in your consolidated billing family, make sure that credit sharing is turned on. For more information, see Sharing AWS credits.

Related informationAWS creditsRedeem your AWS Promotional Credit
Question: I want to stop using the CloudHSM Classic service

I don't want to use AWS CloudHSM Classic anymore. Or, my trial period expired and I've decided I don't want to use CloudHSM Classic. How do I stop using CloudHSM Classic and confirm that I'm not billed for further usage?Short descriptionTo stop using CloudHSM Classic and stop any charges associated with the CloudHSM Classic service:Delete any logs on the HSM appliance.Zeroize your HSM appliance.De-provision your HSM appliance.

ResolutionDelete the logs on your HSM applianceImportant:Deleting your AWS CloudFormation stack doesn't delete your CloudHSM Classic device. Don't delete the elastic network interface for the CloudHSM Classic device until after you confirm that the CloudHSM Classic device is no longer in your account.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.1.    From the Luna shell, rotate all logs by running the following command:lunash:> syslog rotate2.    Delete all logs by running the following command:lunash:> syslog cleanupZeroize your HSM appliance1.    Log in to the control (client) instance.2.    From the control instance, connect to your HSM appliance over SSH by using the following command, where private_key_file is your HSM's private key file and hsm_ip_address is the IP address of your HSM appliance:$ ssh -i private_key_file manager@hsm_ip_address3.    Run the following command:lunash:> hsm login4.    Intentionally enter an incorrect administrator password three times in a row. Attempting to log in as the administrator more than twice with the wrong password zeroizes your HSM appliance.De-provision your HSM applianceUse the delete-hsm command of the AWS CloudHSM CLI or the DeleteHsm AWS CloudHSM API command.To confirm that a device is successfully de-provisioned, run the DescribeHsm API call, and then verify that the device is in the TERMINATED state. A state other than TERMINATED indicates that the HSM appliance wasn't successfully zeroized before it was de-provisioned, and billing for CloudHSM Classic will continue.Note: The ListHsms API call might return a de-provisioned HSM device for up to 24 hours.For more information about de-provisioning unused CloudHSM Classic HSMs, see the CloudHSM migration guide section in the AWS CloudHSM FAQs.

Related informationBacking up and restoring HSM data to a Luna SA backup HSMTroubleshooting AWS CloudHSM
Question: How do I troubleshoot timeout errors when writing from Flink to Kinesis Data Streams?

I'm trying to write data from Flink to Amazon Kinesis Data Streams, but I receive a timeout or exception error. Why is this happening and how do I troubleshoot these errors?Short DescriptionFlink applications that use FlinkKinesisProducer can produce one of the following error messages:Caused by: org.apache.flink.kinesis.shaded.org.apache.http.conn.ConnectTimeoutException: Connect to kinesis.us-east-1.amazonaws.com:443 [kinesis.us-east-1.amazonaws.com/xxx.xxx.xxxx.xxx] failed: connect timed out[AWS Log: ERROR](CurlHttpClient)Curl returned error code 28These two timeout errors are caused by network problems and a lack of system resources in the environment where the Flink application is running.

ResolutionUnable to connect to Kinesis Data Streams service endpointThe following error occurs when the Flink application is unable to connect to the Data Streams service endpoint:Caused by: org.apache.flink.kinesis.shaded.org.apache.http.conn.ConnectTimeoutException: Connect to kinesis.us-east-1.amazonaws.com: 443 [ kinesis.us-east-1.amazonaws.com/xxx.xxxx.xxx] failed:connect timed outIf this error repeatedly occurs, then there could be a problem with your network configuration.To resolve this issue, perform the following steps:1.    Verify that the Flink application can connect to the internet.2.    If your Flink application is running on AWS resources in a virtual private cloud (VPC), verify that the following VPC features are configured correctly:Route TableSecurity GroupsNetwork Access Control Lists (ACL)3.    (Optional) You can also use Data Stream's VPC endpoint to communicate within your VPC.Response for the submitted request wasn't returned within the configured timeout periodThe following Curl 28 error indicates that the response for the submitted request was not returned within the configured timeout period. Therefore, a timeout occurred:[AWS Log: ERROR](CurlHttpClient)Curl returned error code 28The timeout occurred because of a temporary network issue. The timeout might also be caused by too many pending requests to Data Streams, where records are sent to the Kinesis Producer Library (KPL) daemon. Records are sent to the KPL because FlinkKinesisProducer uses the KPL to send data from a Flink stream into an Amazon Kinesis stream.To resolve this issue, change the following configuration parameter of the FlinkKinesisProducer object:Request timeout period: producerConfig.put (“RequestTimeout”, “****”); IInternal Queue Size: FlinkKinesisProducer #setQueueLimit (queueLimit)It's also a best practice to update the following parameters to avoid data loss:Internal Queue Size: FlinkKinesisProducer #setQueueLimit (queueLimit)time-to-live on records: producerConfig.put("RecordTtl", "*****");For more information about calculating the value of setQueueLimit, see Backpressure on the Apache website.
Question: Does AWS provide support in languages other than English?

I want to know if the AWS Support team can speak in a language other than English.

ResolutionAWS Support is available in the following languages: Chinese, English, Japanese, and Korean. You can use one of the supported languages as your preferred contact language to access AWS Support.If you have an AWS Enterprise Support plan, we have Technical Account Managers who can speak and interact with you in these local languages:ChineseEnglishFrenchGermanItalianJapaneseKoreanPortugueseSpanishThaiAnd moreTo know if we can interact in your language, contact your account management team or contact AWS sales support for more information.
Question: How can I resolve the error "You have exceeded the allowed number of AWS accounts." for AWS Organizations?

I received the error message "You have exceeded the allowed number of AWS accounts." when inviting or creating accounts in AWS Organizations.

Short descriptionThis error indicates that you exceeded the default maximum number of AWS accounts for your AWS Organizations organization. The default maximum number of accounts allowed in an organization is 10.

ResolutionYou can request an increase to the maximum number of accounts for Service Quotas allowed in your AWS Organizations organization. You can use either the Services Quota console or the AWS 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.Important: Organizations is a global service that is physically hosted in the US East (N. Virginia) (us-east-1) AWS Region. You must use the us-east-1 Region to access Organizations quotas using the Service Quotas console or AWS CLI.Services Quota console1.    Open the Service Quotas console in the us-east-1 Region.2.    In the navigation pane, expand Organization, and then choose Quota request template.3.    In Quota request template, choose Add quota.4.    Choose the Region dropdown list, and choose US East (N. Virginia).5.    Choose the Service dropdown list, and choose AWS Organizations.6.    Choose the Quota dropdown list, and choose Default maximum number of accounts.7.    In Desired quota value, enter your value.Note: The value must be larger than 10 and more than your current value.8.    Choose Add.For more information, see Requesting a quota increase.AWS CLIRequest a quota increase using the AWS CLI command request-service-quota-increase similar to the following:Note: Replace your-value with your value.$ aws service-quotas request-service-quota-increase --service-code organizations --quota-code L-29A0C5DF --desired-value your-valueFor more information, see How can I request, view, and manage service quota increase requests using AWS CLI commands?Related informationHow do I manage my AWS service quotas?
Question: How do I use the AWS CLI to view the contents of an S3 Glacier vault?

I want to check the contents of an Amazon Simple Storage Service (Amazon S3) Glacier vault.

ResolutionUse the following AWS Command Line Interface (AWS CLI) commands to check the contents of your Amazon S3 Glacier vaults.Before you begin, configure the AWS CLI. If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.To list the vaults in your AWS account, run the list-vaults command.Note: If you don't see any vaults listed, run the configure command. Confirm that the correct AWS Region is configured for the AWS CLI.To request an inventory of a specific vault, run the initiate-job command and include the option --job-parameters '{"Type": "inventory-retrieval"}'.Note: The job run time varies depending on the retrieval type. For more information, see Archive retrieval options.To view the status of a job, run the describe-job command.To download the output of a job, run the get-job-output command.For a list of all available commands, see the AWS CLI command reference for Amazon S3 Glacier.

Related informationUsing Amazon S3 Glacier with the AWS CLIAmazon S3 Glacier data retrieval policiesSet data retrieval policy (PUT policy)
Question: "How to troubleshoot 500, 502 and 503 errors caused by Lambda@Edge functions in CloudFront?"

I associated the AWS Lambda@Edge function with an Amazon CloudFront distribution. Now I'm getting 500, 502 or 503 errors. How do I troubleshoot the errors?Short descriptionLambda@Edge 500, 502 and 503 errors indicate the following:HTTP 500 status code indicates that the Lambda function returned a run error.HTTP 502 status code indicates that the Lambda function response was incorrectly formed or included content that is not valid.HTTP 503 status code indicates that CloudFront is throttled due to Lambda service quotas (formerly known as limits).See the following sections for the causes of the errors, and how to troubleshoot them.

ResolutionLambda@Edge function returns a 500 errorA 500 run error results when CloudFront doesn’t get a response from Lambda. This happens because there are unhandled exceptions in the function, there’s an error in the code, or it's an unsupported run environment.To resolve 500 error generated by Lambda@Edge, you must debug your code by adding logging statements for Lambda functions. To learn more, see Four Steps for Debugging your Content Delivery on AWS and review the information under I – Execution Errors. These logging statements write messages to CloudWatch log files that monitor the running of the CloudFront function. You can review those statements in the CloudWatch log files to verify that the function is working correctly.For more information, see Lambda function errors in Node.js and Lambda function errors in Python.Lambda@Edge function returns a 502 errorAfter the function runs, CloudFront receives a response from Lambda. A 502 error is returned if the object structure of the response doesn't conform to the Lambda@Edge event structure. A 502 error is also returned if the response contains not valid headers or other not valid fields.To resolve 502 error generated by Lambda@Edge, check the Lambda@Edge function for the following common issues:Returned JSON objectMissing required fieldsThe response has an object that is not validAdding or updating is disallowed or there are read-only headersExceeding the maximum body sizeCharacters or values are not validFor more information, see Testing and debugging Lambda@Edge functions and Restrictions on edge functions.Lambda@Edge function returns a 503 errorThe Lambda service throttles executions in each Region, and returns a 503 error if you exceed the quota.To resolve 503 error, check the Lambda@Edge CloudWatch metrics and log files for the following common issues:Concurrent executions on per Region basisFunctions quotas reachedFor more information, see Quotas on Lambda@Edge.Note: You must review CloudWatch log files in the correct Region to see the log files created when CloudFront executed the Lambda function.

Related informationLambda@Edge design best practices
Question: Why does the SELECT COUNT query in Amazon Athena return only one record even though the input JSON file has multiple records?

When I run SELECT COUNT(*) FROM TABLE, the output is "1," but the input file has multiple JSON records. I used org.openx.data.jsonserde.JsonSerDe to create the table.

ResolutionWhen records aren't separated by a newline character (\n), the SELECT COUNT(*) FROM TABLE query returns "1."Example:{"ID":"1","MYTIMESTAMP":"2020-06-09 17:50:46.267","Name":"John"}{"ID":"2","MYTIMESTAMP":"2020-06-10 17:50:46.267","Name":"Joel"}{"ID":"3","MYTIMESTAMP":"2020-06-10 17:50:46.267","Name":"Patrick"}To correct this problem, be sure that the records are delimited by \n, as shown in the following example:{"ID":"1","MYTIMESTAMP":"2020-06-09 17:50:46.267","Name":"John"}{"ID":"2","MYTIMESTAMP":"2020-06-10 17:50:46.267","Name":"Joel"}{"ID":"3","MYTIMESTAMP":"2020-06-10 17:50:46.267","Name":"Patrick"}In this case, SELECT COUNT(*) FROM TABLE returns "3."Note: The SerDE expects each JSON document to be on a single line of text with no line termination characters separating the fields in the record. For more information, see Best practices for reading JSON data.

Related informationSELECTCREATE TABLERunning SQL queries using Amazon Athena
Question: How do I migrate my DNS services from a third-party DNS provider to Amazon Lightsail?

I want to migrate my DNS services from a third-party DNS provider so that I can point my domain to an Amazon Lightsail instance? How do I do this?Short descriptionThere are three scenarios for transferring your DNS services:Scenario A: Move the entire name server setup of your domain from the third-party DNS provider to Amazon Lightsail.Scenario B: Move the entire name server setup of your sub domain from a third-party DNS provider to AWS and not the entire domain.Scenario C: Point your domain (for example: xyz.abc.com) to the Lightsail instance, but don't move the DNS servers.

ResolutionScenario A: Move the entire name server setup of your domain from the third-party DNS provider to Amazon Lightsail1.    Open the Amazon Lightsail console.2.    Select Networking, Create DNS Zone.Note: For more information on creating a DNS zone, see Create a DNS zone in the Lightsail console.3.    Enter the domain, and then select Create DNS Zone. An example domain is abc.com. You receive a set of four name servers.4.    Add more DNS records in the newly created DNS zone. Refer to the DNS record details in your current DNS provider. Copy all the records to your Lightsail DNS zone, one at a time.5.    After all the records are copied and you're ready to switch your domain's name server to Lightsail, go to your domain's current registrar portal. Replace the current name servers with the new servers you received in step 3. Replace the name servers in the name servers section in the domain's current registrar portal, not in the DNS zone of the current DNS provider.6.    Select Save.Note: Allow time for the name server change to propagate through the internet's DNS. This might take several hours.Scenario B: Move the entire name server setup of your sub domain from a third-party DNS provider to AWS and not the entire domain1.    Open the Amazon Lightsail console.2.    Select Networking, Create DNS Zone.Note: For more information on creating a DNS zone, see Create a DNS zone in the Lightsail console.3.    Enter the domain, and then select Create DNS Zone. An example domain is xyz.abc.com. You will receive a set of four name servers.4.    Open the DNS records at your third-party DNS provider. Create 4 new DNS records using NS as the record type. In this example, the record name is xyz and the value is each of the name servers you received in step 3.5.    Open the Amazon Lightsail console and then open the DNS zone. Create a DNS record pointing xyz.abc.com to the Lightsail instance. For more information see Add records to the DNS zone.Scenario C: Point your domain (for example: xyz.abc.com) to the Lightsail instance, but don't move the DNS serversIn this scenario, you don't need to create a Lightsail DNS zone. Create an A record in your third-party DNS provider for your domain (for example, xyz.abc.com). Then point it to the Lightsail instance's IP address. Now the website loads from the Lightsail instance.Note: It might take a few hours for DNS propagation.

Related informationPointing your domains to your Amazon Lightsail distributions
Question: Why do I need to add a payment method if my account is covered by the AWS Free Tier?

My account is covered by the AWS Free Tier. Why do I need to add a payment method to my account?ResolutionYou must add a valid credit card, debit card, or another payment method for your accounts covered under the AWS Free Tier for the following reasons:Accounts covered under the AWS Free Tier aren't restricted in what they can launch. As you ramp up with AWS, you might start using more than what's covered under the AWS Free Tier. Because these additional resources might incur charges, a payment method is required on the account.The AWS Free Tier doesn't cover all AWS services. For example, you might decide to purchase Reserved Instances, Amazon Route 53 domains, or an AWS Support subscription. These services require a valid payment method for activation.For more information, see How do I make sure that I don't incur charges when using the AWS Free Tier?Related informationAWS Free TierUsing the AWS Free Tier
Question: Why is the RefreshCache operation taking a long time on my file gateway?

I initiated the RefreshCache operation on my file gateway in AWS Storage Gateway. However, the operation is taking a long time to complete. What's the reason for this delay?ResolutionThe RefreshCache operation identifies the changes (updates, uploads, or deletes) of Amazon Simple Storage Service (Amazon S3) objects since the last time the gateway identified and cached the objects. To do this operation, the file gateway runs a recursive LIST operation on the S3 bucket, and then runs a HEAD object operation on every object that comes back from the LIST operation. The HEAD operation grabs the metadata, which is then stored in the file gateway cache.The following factors can impact how long it takes for a RefreshCache operation to complete:If there's a large number of objects in the S3 bucket, then the run time of RefreshCache increases. This is because the file gateway runs a HEAD object against all objects in the bucket.RefreshCache operations are specific to individual file shares within a file gateway. One file share supports two RefreshCache API operations at any given time. If you send more requests to initiate a cache refresh, then more operations are triggered even before the completion of operations that are in progress. This can result in an InvalidGatewayRequestException error.S3 buckets can support 3,500 PUT/COPY/POST/DELETE or 5,500 GET/HEAD requests per second per prefix. These supported requests rates also apply to the requests made by the file gateway to your S3 buckets, which impacts how quickly a RefreshCache operation can be completed. The run time of RefreshCache can increase if the S3 bucket is also being used by services other than the file gateway.Consider the following ways you can decrease the run time of a RefreshCache operation:You can reduce the number of objects in the bucket.You can deploy multiple file shares that correspond to separate prefixes in the S3 bucket, instead of having one file share for the entire bucket.Note: You can create up to 10 file shares for an individual file gateway. Because the RefreshCache operations are run per file share, this approach can help reduce the time it takes to complete individual RefreshCache operations.If you're using one file share for an entire S3 bucket, consider focusing the RefreshCache operations on specific prefixes or folders of the bucket that are being updated with new objects. This reduces the scope of the operation, which can help reduce the run time. You can target RefreshCache operations to specific folders when you run the operation using the AWS Command Line Interface (AWS CLI) or the Storage Gateway API. This option is currently not available in the Storage Gateway console.Note: 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 run the RefreshCache operation during off-peak times for other requests to the S3 bucket. You can use AWS Lambda and Amazon CloudWatch to trigger the operation on a timer.

Related informationAutomating cache refresh process for File Gateway on AWS Storage Gateway