VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I resolve the error "FAILED: ParseException line 1:X missing EOF at '-' near 'keyword'" in Athena?

When I run an MSCK REPAIR TABLE or SHOW CREATE TABLE statement in Amazon Athena, I get an error similar to the following: "FAILED: ParseException line 1:X missing EOF at '-' near 'keyword'".

ResolutionYou get this error when the database name specified in the DDL statement contains a hyphen ("-"). AWS Glue allows database names with hyphens. However, underscores (_) are the only special characters that Athena supports in database, table, view, and column names.In the following example, the database name is alb-database1. When you run MSCK REPAIR TABLE or SHOW CREATE TABLE, Athena returns a ParseException error:Your query has the following error(s):FAILED: ParseException line 1:7 missing EOF at '-' near 'alb'This query ran against the "alb-database1" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: cc5c1234-4c12-4dcb-a123-bff954b305eb.To resolve this issue, recreate the database with a name that doesn't contain any special characters other than underscore (_).

Related informationNames for tables, databases, and columns
Question: Why are the emails that I send using Amazon SES failing with the error message "Email rejected per DMARC policy"?

I'm sending emails from Amazon Simple Email Services (Amazon SES) using a verified email address. But the emails are failing with the error message "Email rejected per DMARC policy".

Short descriptionThe following are common reasons why you can receive a Domain-based Message Authentication and Conformance (DMARC) failure:You have a "reject" DMARC policy on your domain, and your email address isn't authenticated through Sender Policy Framework (SPF) or DomainKeys Identified Mail (DKIM). To comply with DMARC, you must authenticate your email messages through SPF or DKIM, or both.Your email address is verified, but your domain isn't. To resolve this issue, you must verify your domain using DKIM to comply with DMARC.

ResolutionAuthenticate your email messages through SPF or DKIMYou have a DMARC policy on your domain that's similar to the following:v=DMARC1; p=reject; rua=mailto:dmarcreports@example.com;When you have a DMARC policy that controls your domain's outbound email traffic and your email address isn't authenticated, your email is rejected.To resolve this issue, authenticate your email identity with DKIM or SPF, and comply with DMARC. For step-by-step instructions, see What do I do if my Amazon SES emails fail DMARC validation for SPF alignment or DKIM alignment?Verify your domain using DKIM to comply with DMARCIf you're sending email using an email address that's verified on a domain that's not verified, then your email fails DMARC with no DKIM authentication. Follow these instructions to verify your domain, Verifying a DKIM domain identity with your DNS provider. For methods on how to authenticate your email through DKIM see, Authenticating email with DKIM in Amazon SES.Note:You can't authenticate an email address that's on a domain that's not verified.When you send email using a separately verified email address on a DKIM-configured domain, Amazon SES automatically authenticates the message. However, if you turned off DKIM on a separately verified email address that's on a DKIM-configured domain, then your message isn't authenticated.

Related informationWhy are the emails that I send using Amazon SES getting marked as spam?How do I enable DKIM for Amazon SES?Why is DKIM domain failing to verify on Amazon SES?Troubleshooting DKIM problems in Amazon SES
Question: Why am I getting an HTTP 307 Temporary Redirect response from Amazon S3?

When I send requests to an Amazon Simple Storage Service (Amazon S3) bucket, Amazon S3 returns a 307 Temporary Redirect response. Why am I receiving this error?ResolutionAfter you create an Amazon S3 bucket, up to 24 hours can pass before the bucket name propagates across all AWS Regions. During this time, you might receive the 307 Temporary Redirect response for requests to Regional endpoints that aren't in the same Region as your bucket. For more information, see Temporary request redirection.To avoid the 307 Temporary Redirect response, send requests only to the Regional endpoint in the same Region as your S3 bucket:If you're using the AWS Command Line Interface (AWS CLI) to access the bucket, configure the AWS CLI. Your AWS CLI must reside in the same Region as your Amazon S3 bucket.Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent AWS CLI version.If you're using an Amazon CloudFront distribution with an Amazon S3 origin, CloudFront forwards requests to the default S3 endpoint ( s3.amazonaws.com). The default S3 endpoint is in the us-east-1 Region. If you must access Amazon S3 within the first 24 hours of creating the bucket, you can change the origin domain name of the distribution. The domain name must include the Regional endpoint of the bucket. For example, if the bucket is in us-west-2, you can change the origin domain name from awsexamplebucketname.s3.amazonaws.com to awsexamplebucket.s3.us-west-2.amazonaws.com.Tip: To reduce the number of DNS redirects and DNS propagation issues, specify the AWS Region of your bucket in all HTTP requests. For example, if you're using the AWS CLI, include the --region parameter in your request to specify the AWS Region.

Related informationAWS service endpoints
Question: How do I perform Git operations on an AWS CodeCommit repository with an instance role on Amazon EC2 instances for Amazon Linux 2?

I want to perform Git operations on an AWS CodeCommit repository. And I want to use an instance role on Amazon Elastic Compute Cloud (Amazon EC2) instances for Amazon Linux 2.

Short descriptionUse the AWS Command Line Interface (AWS CLI) credential helper for Git operations on a CodeCommit repository using an instance role on your EC2 instance.Note: Using a credential helper is the only connection method for CodeCommit repositories that doesn't require an AWS Identity and Access Management (IAM) user.

ResolutionNote: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.1.    Create an IAM role for your EC2 instance, and then attach the following example IAM policy to the role. Replace arn:aws:codecommit:us-east-1:111111111111:testrepo with the ARN of your CodeCommit repository.{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Action": [        "codecommit:GitPull",        "codecommit:GitPush"      ],      "Resource": "arn:aws:codecommit:us-east-1:111111111111:testrepo"    }  ]}Note: The policy for step 1 allows the IAM role to perform Git pull and push actions on the CodeCommit repository. For more examples on using IAM policies for CodeCommit, see Using identity-based policies (IAM Policies) for CodeCommit.2.    Attach the IAM role that you created in step 1 to an EC2 instance.3.    Install Git on your EC2 instance.Note: For more information, see Downloads on the Git website.4.    To set up the credential helper on the EC2 instance, run the following commands:$ git config --global credential.helper '!aws codecommit credential-helper $@'         $ git config --global credential.UseHttpPath trueNote: The commands in step 4 specify the use of the Git credential helper with the AWS credential profile. The credential profile allows Git to authenticate with AWS to interact with CodeCommit repositories. To authenticate, Git uses HTTPS and a cryptographically signed version of your EC2 instance role.5.    To configure your name and email address explicitly, run the following commands:$ git config --global user.email "testuser@example.com"$ git config --global user.name "testuser"Note: Your name and email address are automatically configured based on your user name and hostname.6.    To clone the repository to the EC2 instance, run the following command:$ git clone https://git-codecommit.us-east-1.amazonaws.com/v1/repos/testrepo7.    Create a commit in your CodeCommit repository.Note: If you're using Windows, see Setup steps for HTTPS connections to AWS CodeCommit repositories on Windows with the AWS CLI credential helper.

Related informationSetup steps for HTTPS connections to AWS CodeCommit repositories on Linux, macOS, or Unix with the AWS CLI credential helperHow do I perform Git operations on an AWS CodeCommit repository with an instance role on Amazon EC2 instances for Windows?
Question: How do I create an Amazon RDS event subscription?

I want to be notified when there's an event (for example, creation, failure, or low storage) on my Amazon Relational Database Service (Amazon RDS) resources. How do I subscribe to Amazon RDS event notifications?ResolutionTo subscribe to Amazon RDS event notifications, see Subscribing to Amazon RDS event notification. For a list of event categories and messages that you can subscribe to, see Amazon RDS event categories and event messages.It's a best practice to test your event subscription after its status becomes active. You can test your subscription by initiating one action in the Amazon RDS resources that you specify in the subscription that triggers the event. For example, you can test a subscription with a Multi-AZ failover or a reboot. If your subscription works as expected, you receive a notification message about the event.

Related informationUsing Amazon RDS event notification
Question: How can I reactivate my suspended AWS account?

My AWS account is suspended, and I want to regain access to my account and its services.

ResolutionNote: If you closed your AWS account within the past 90 days and you want to reopen it, see Can I reopen my closed AWS account? If the suspended account is a member account in an organization, then contact the owner of the management account.If your account is suspended due to outstanding charges, you can reinstate your account by paying all past due charges. You can pay your past due charges in the Billing and Cost Management console.Here are a few important things to keep in mind if your account is suspended due to outstanding charges:Resources on the account can be deleted at any time while your account is suspended.If your account isn't reactivated within 30 days of suspension, then your account will be closed.If your account isn't reactivated within 90 days of closure, then your account is terminated.Terminated accounts can't be reopened, and all resources on the account are lost.To pay the past due charges on an account, first verify that your current payment information is accurate:Check Payment methods to confirm that the information associated with your payment method is correct.If your default payment method is no longer valid, add a new payment method, and then set it as the default payment method.Then, follow these steps to pay your outstanding charges:Open the Billing and Cost Management console.On the navigation pane, choose Payments.You can view your outstanding invoices on the Payments Due tab.On the Payments Due tab, select the invoice that you want to pay, and then choose Complete payment.On the Complete a payment page, confirm that the summary matches what you want to pay, and then choose Verify and Pay.If you paid your past due charges in full with a credit card, then services automatically reactivate within a few minutes.If you paid your past due charges in full with a different payment method, then contact AWS Support to reactivate your account.Sometimes account services can take up to 24 hours to reactivate an account. If you have paid your past due charges in full and your account isn't reactivated within 24 hours, then contact AWS Support.If your account was suspended by AWS, then you might need to provide additional information so AWS can review your reinstatement request. Check your email and spam folder to see if AWS needs any information from you to complete the reactivation process. Then, respond with the requested information and your account will be reviewed for reinstatement.If you have additional questions, or can't provide the requested information, then contact AWS Support. If you can't sign in to your account, then contact the AWS Account Verification team using the AWS Account Verification support form.

Related informationManaging your paymentsMaking payments, checking unapplied funds, and viewing your payment historyClosing an accountWhat do I do if I'm having trouble signing in to or accessing my AWS account?
Question: How do I resolve the error "An error occurred (TargetNotConnectedException) when calling the ExecuteCommand operation" in Amazon ECS?

When I try to run the AWS Command Line Interface (AWS CLI) command execute-command in Amazon Elastic Container Service (Amazon ECS), I get the following error:"An error occurred (TargetNotConnectedException) when calling the ExecuteCommand operation: The execute command failed due to an internal error. Try again later"Short descriptionYou might get this error due to the following reasons:The Amazon ECS task role doesn't have the required permissions to run the execute-command command.The AWS Identity and Access Management (IAM) role or user that's running the command doesn't have the required permissions.Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

ResolutionCheck the Amazon ECS task role permissionsYou get this error when the Amazon ECS task role doesn't have the required permissions. You might resolve this error by creating an IAM policy with the required permissions and then attaching the policy to the Amazon ECS task role.1.    Create the following IAM policy:{   "Version": "2012-10-17",   "Statement": [       {       "Effect": "Allow",       "Action": [            "ssmmessages:CreateControlChannel",            "ssmmessages:CreateDataChannel",            "ssmmessages:OpenControlChannel",            "ssmmessages:OpenDataChannel"       ],      "Resource": "*"      }   ]}Note: Be sure that these permissions are not denied at the AWS Organizations level.2.    Attach the policy to the Amazon ECS task role.There might be delays in propagating these changes at the task level. Therefore, wait for some time after attaching the policy to the task role, and then try running the execute-command command.Check the IAM user or role permissionsBe sure that the IAM user or role that's running the execute-command command has the following permissions:{    "Version": "2012-10-17",    "Statement": [        {            "Effect": "Allow",            "Action": "ecs:ExecuteCommand",            "Resource": "arn:aws:ecs:example-region:example-arn:cluster/example-cluster/*"        }    ]}If you're still getting the error, run the amazon-ecs-exec-checker script. This script allows you to check and validate your AWS CLI environment and the Amazon ECS cluster or task. The script also notifies you about the prerequisite that's not met.

Related informationEnabling and using ECS Exec
Question: Why aren't my EMR Spot Instances being provisioned during a cluster resize?

My Amazon EMR Spot Instances aren't being provisioned during a resize of my EMR cluster.

ResolutionAmazon Elastic Compute Cloud (Amazon EC2) might interrupt your Spot Instance at any time for the following reasons:Lack of Spot capacity.The request constraints can't be met.The Spot Price is higher than the designated maximum price.Your Spot account quota is exhausted. If this is the case, then you can request an increase.For more information, see Why did Amazon EC2 terminate my Spot Instance?Note: It's a best practice to use Spot Instances for workloads that are stateless, fault-tolerant, and flexible enough to withstand interruptions.Also, Spot Instances and On-Demand Instances might not be resized because the bootstrap scripts were modified or contain errors.Check the logs for the bootstrap script at /emr/instance-controller/log/bootstrap-actions or s3://cluster_id/node-failed/bootstrap-actions/stderr.gz. The logs show the error STARTUP_SCRIPT_FAILED_RET_CODE.For example, the following bootstrap action log shows that bootstrap action 1 (emr_bootstrap_actions.sh) failed:Another app is currently holding the yum lock; waiting for it to exit...  The other application is: yum    Memory : 125 M RSS (444 MB VSZ)    Started: Tue Jul 19 05:36:36 2022 - 00:03 ago    State  : Running, pid: 7914Error: Package: falcon-sensor-4.18.0-6403.amzn2.x86_64 (/falcon-sensor-4.18.0-6403.amzn2.x86_64)           Requires: systemdIf you see the preceding error, then the following actions happen:All of the new replacement nodes terminate.The node stops provisioning new replacement instances.The core node instance group goes into arrested mode as shown in the following example:"state": "ARRESTED",  "message": "Instance group ig-2JN5xxxxxxxx in Amazon EMR cluster j-37H4xxxxxxx (emr-xxxxx-spark-cluster) was arrested at  for the following reason: Error provisioning instances."=====Related informationSpot Instance interruptionsSpot request statusSpot Instance best practicesWhy is my Spot Instance terminating even though the maximum price is higher than the Spot price?
Question: How can I create a VPC peering connection between two VPCs?

How can I create an Amazon Virtual Private Cloud (Amazon VPC) peering connection between two VPCs?Short descriptionYou can create a VPC peering connection between two VPCs in the same or different AWS accounts and Regions. The VPC peering connection allows you to communicate between hosts using private IPv4 or the IPV6 addresses. VPC peering uses the AWS infrastructure. VPC peering isn't a gateway or a VPN connection, and doesn't rely on a separate piece of physical hardware.Important: Before proceeding, review the following:VPC peering scenariosUnsupported VPC peering configurationsVPC peering limitations

ResolutionCreate VPC peering from the Amazon VPC consoleOpen the Amazon VPC console.In the left navigation pane scroll down and click on peering connection.Click on Create peering connection.Once the peering connection is active we can proceed to update the route tables to enable traffic to traverse over the peering connection.Create VPC peering using AWS CLINote: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you're using the most recent version of the AWS CLI.Follow the AWS CLI command reference create-vpc-peering-connection for steps and examples of different scenarios.To accept the VPC peering connection use accept-vpc-peering-connection.

Related informationHow do I resolve Amazon VPC peering network connectivity issues?Why can't I create an Amazon VPC peering connection with a VPC in another AWS account?Amazon VPC FAQs
Question: When will my AWS bill be ready?

I want to know when I'll receive my AWS bill.

ResolutionYour AWS bill for the previous month is finalized at the beginning of each new month. Shortly after, the bill is charged to your default payment method, usually between the third and the fifth day of the month.Note: The billing cycle is based in the UTC (+00:00) time zone.If you use the AWS Cost and Usage Report, then check the bill/InvoiceID column. This column is blank until your bill is finalized.

Related informationWhat payment methods does AWS accept?Can I use more than one payment method to pay my AWS charges?How do I view past or current AWS payments?
Question: Why is my EC2 Windows instance down with an instance status check failure?

How to troubleshoot your Amazon Elastic Compute Cloud (Amazon EC2) Windows instance going down due to an instance status check failure.

Short descriptionAmazon Web Services (AWS) monitors the health of each EC2 instance with two status checks. An EC2 instance becomes unreachable if a status check fails.An instance status check failure indicates a problem with the instance, such as:Networking or startup configuration issuesExhausted memoryFile system issuesFailure to boot the operating systemFailure to mount volumes correctlyIncompatible driversCPU exhaustionIf both the instance and system status checks fail, then see Why is my EC2 Windows instance down with a system status check failure or status check 0/2?ResolutionDue to instance status checks likely being caused by issues within the guest operating system, focus your troubleshooting on reviewing the following:Console outputSystem logsOperating system or application error messagesFor more information, see Troubleshooting EC2 Windows instances.Tip: You can also use EC2Rescue for Windows Server to diagnose and troubleshoot issues.

Related informationTroubleshoot an unreachable instanceTroubleshooting connecting to your Windows instanceWhy is my EC2 Linux instance unreachable and failing one or both of its status checks?How do I diagnose high CPU utilization on my EC2 Windows instance when my CPU is not being throttled?
Question: How do I retrieve my Windows administrator password after launching an instance?

I launched an Amazon Elastic Compute Cloud (Amazon EC2) instance, and now I need to retrieve my Windows administrator password.

ResolutionRetrieve your initial administrator password with the Amazon EC2 console or the AWS Command Line Interface (AWS CLI).Retrieve your initial administrator password using the Amazon EC2 consoleNote: This method requires an Amazon EC2 key pair.If you lost your key pair, then see How can I reset the administrator password on an EC2 Windows instance?If you need an Amazon EC2 key pair, then see Create a key pair using Amazon EC2.Follow these steps:1.    Open the Amazon EC2 console, and then choose Instances.2.    Select the check box for the instance, and then expand the Actions dropdown list. For the old console, choose Get Windows Password. For the new console, choose Security, and then choose Get Windows Password.Note: When you first launch a new instance, this option might not be available for a few minutes.3.    Choose Browse, select your key pair file, and then choose Open.-or-Paste the contents of your key pair into the text box.4.    Choose Decrypt Password.Retrieve your initial administrator password using the AWS CLINote: If you receive errors when running AWS CLI commands, make sure that you're using the most recent version of the AWS CLI.Use the get-password-data command. For example syntax, see Examples.

Related informationGetting started with Amazon EC2 Windows instancesConnect to your Windows instance