VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: Why do I receive the error "You can only join an organization whose Seller of Record is same as your account" when I'm trying to join an organization?

When I try to join an AWS Organization, I receive the error "You can only join an organization whose Seller of Record is same as your account." What does this error mean?ResolutionThis error indicates that your seller of record or AWS partition is not the same as the management account in the AWS Organization.The seller of record refers to whether your account is with Amazon Web Services, Inc. (AWS Inc.), Amazon Web Services EMEA SARL (AWS Europe), Amazon Web Services India Private Limited (AWS India), or another seller of record. Due to billing constraints, AWS India accounts can't be in the same organization as accounts with other AWS sellers of record.An AWS partition is a group of Regions. The AWS supported partitions are AWS Regions, AWS China Regions, and AWS GovCloud (US) Regions. Due to legal and billing constraints, you can join an organization only if it's in the same partition as your account. Accounts in the AWS Regions partition can't be in an organization with accounts from the AWS China Regions partition or AWS GovCloud (US) Regions partition.For example, in an AWS Europe organization, you can have both an AWS Inc. and an Amazon Web Services Canada, Inc. (AWS Canada) account.If you're not sure the seller of record that your account is with, see Determining which company your account is with.If you're not sure the seller of record that the management account of the organization is with, contact the owner of the management account. To see the contact details of the management account:Sign in to the AWS Management Console.On the navigation bar, choose your account name, and then choose My Organization.

Related informationWhy can't I join an organization in AWS Organizations?AWS GovCloud (US) compared to standard AWS Regions
Question: How can I update database parameters in a Lightsail MySQL or PostgreSQL database?

How can I update database parameters in an Amazon Lightsail MySQL or PostgreSQL database?Short descriptionWhen a Lightsail database is created, it is uses a custom parameter group that is named after the instance endpoint, unlike Amazon Relational Database Service (Amazon RDS) DB instances that use a default DB parameter group. To modify the database parameters for a Lightsail database instance, use the AWS Command Line Interface (AWS CLI).

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.    Install the AWS CLI in the same AWS Region as the Lightsail database.2.    Get a list of the available database parameters that can be modified.3.    After you identify the parameter that you want to change, update the parameter.Note: If you update a static parameter and the apply method is set to pending-reboot, then the parameter update is applied only after the instance is rebooted.The following is an example command for Lightsail Amazon RDS MySQL 5.7.26:aws lightsail update-relational-database-parameters --relational-database-name Lightsail-Database-Ireland-1 --parameters "parameterName=connect_timeout,parameterValue=30,applyMethod=immediate"See the following example output for this operation:{  "operations": [        {            "status": "Succeeded",             "resourceType": "RelationalDatabase",             "isTerminal": true,             "statusChangedAt": 1579868316.024,             "location": {                "availabilityZone": "eu-west-1a",                 "regionName": "eu-west-1"             },             "operationType": "UpdateRelationalDatabaseParameters",             "resourceName": "Lightsail-Database-Ireland-1",             "id": "23a7de77-aa6c-4831-8525-8c6d97921676",             "createdAt": 1579868316.024         }    ]}The following is an example command for Lightsail Amazon RDS PostgreSQL 10.10:aws lightsail update-relational-database-parameters --relational-database-name lightsail-postgres --parameters "parameterName=deadlock_timeout,parameterValue=30,applyMethod=immediate"See the following example output for this operation:{    "operations": [        {            "status": "Succeeded",            "resourceType": "RelationalDatabase",            "isTerminal": true,            "statusChangedAt": 1579869403.669,            "location": {                "availabilityZone": "eu-west-1a",                "regionName": "eu-west-1"            },            "operationType": "UpdateRelationalDatabaseParameters",            "resourceName": "lightsail-postgres",            "id": "e18a2827-b140-4872-b90c-ab7850a7b6df",            "createdAt": 1579869403.669        }    ]}Related informationCreating a database in Amazon Lightsail
Question: Why was my credit card declined when I tried to pay my AWS bill?

I tried to pay an AWS bill or purchase a subscription, such as an Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instance, but the charge was unsuccessful. How do I fix this?ResolutionIf your payment method is declined when you try to pay your AWS bill, check the following:Account information associated with your payment methodCheck Payment Methods in the Billing and Cost Management console to confirm that your credit card number, expiration date, billing address, and phone number are correct. Important: Confirm that the billing address and phone number match the information on file with the institution that issued your credit card.Confirm that your credit card is accepted by the AWS seller providing services to you. The name of the AWS seller is noted on your invoice.Transaction and balance limits on your payment methodIf the information associated with your payment method is correct, contact your bank and check the following:Confirm that your credit card has enough available credit to pay your AWS invoice. If not, ask your bank to adjust your withdrawal or purchase limits.Confirm that you authorize the charge for AWS services. The charge descriptor ends in aws.amazon.com for AWS Inc. and AWS Europe accounts.Payment issuer verification or authenticationIf your card issuer requires payment verification or authentication, review the following:AWS doesn’t support card verification value (CVV). If your card issuer requires the use of CVV, then check with the card issuer to waive the requirement.AWS doesn't support 3D Secure authentication. If you're an Amazon Web Services India Private Limited (AWS India) customer, and your card issuer requires 3D Secure authentication, then check with the card issuer to waive the requirement.If you're an AWS Europe customer, you might need to verify your credit card payment with the card issuer. For more information, see Managing your AWS Europe credit card payment verification.Retry the paymentIf the issue is resolved retry the charges.If you're in the process of purchasing a subscription and the payment is declined, create a case with AWS Support and then select Account and billing support.When creating a case with AWS Support to retry your payment, keep the following in mind:AWS Support can retry the charges for a Reserved Instance or Savings Plans only during the month of purchase.AWS Support can't retry payments for Amazon Route 53 domain registration, renewal, or transfer. To resubmit the domain registration, renewal, or transfer, see Transferring registration for a domain to Amazon Route 53.

Related informationHow do I add a new payment method to my AWS account?How do I change the default payment method associated with my AWS account?How do I view past or current AWS payments?
Question: How do I create a new Direct Connect connection with physical redundancy?

I want to create a new AWS Direct Connect connection with physical redundancy.

Short descriptionDirect Connect offers the following physical redundancy (location, path, and device) options:Development and test - This option is for non-critical workloads or development workloads and uses separate connections that terminate on separate devices in one location. It provides resiliency against device failure, but doesn't provide resiliency against location failure.High resiliency - This option is for critical workloads and uses two single connections to multiple connections. It provides resiliency against connectivity failures caused by a fiber cut or a device failure and also prevents a complete location failure. With this option, you can order dedicated connections to achieve an SLA of 99.9%.Maximum resiliency - This option is for critical workloads and uses separate connections that terminate on separate devices in more than one location. It provides resiliency against device, connectivity, and complete location failures. With this option, you can order dedicated connections to achieve an SLA of 99.9%.Note: It's a best practice to use the Connection wizard in the Direct Connect Resiliency Toolkit to order the dedicated connections to achieve your SLA objective.

ResolutionNote: The following steps apply to dedicated connections. For hosted connections, contact an AWS Direct Connect Partner.1.    Sign in to the AWS Management Console, and then open your Direct Connect console.2.    Choose Create connection.3.    Under Connection ordering type, choose Connection wizard.4.    Under Resiliency level, select the option that you want, and then choose Next.5.    Under Connection settings, select the appropriate Bandwidth, Location, and Service provider.6.    (Optional) To configure MACsec support and Tags, choose Additional settings, and then configure the settings.7    Choose Next to go to the Review and create page. Review your order, and then choose Create.8.    Download your Letter of Authorization and Connecting Facility Assignment (LOA-CFA).

Related informationDedicated connectionsHosted connectionsUsing the AWS Direct Connect Resiliency Toolkit to get startedAWS Direct Connect Service Level AgreementAWS Direct Connect Mac Security
Question: How do I assign an existing IAM role to an EC2 instance?

I have an AWS Identity and Access Management (IAM) role that I want to assign to an Amazon Elastic Compute Cloud (Amazon EC2) instance.

ResolutionUse either the Amazon EC2 console of the AWS Command Line Interface (AWS CLI) to assign a role. For more information, see Attach an IAM role to an instance.If you use AWS Systems Manager, then wait for AWS Systems Manager Agent (SSM Agent) to detect the new IAM role, or restart SSM Agent. For more information, see Setting up AWS Systems Manager.If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.

Related informationCreating IAM rolesTutorial: Get started with Amazon EC2 Linux instancesUsing an IAM role to grant permissions to applications running on Amazon EC2 instancesI created an IAM role, but the role doesn't appear in the dropdown list when I launch an instance. What do I do?
Question: My EC2 Linux instance failed its system status check. How do I troubleshoot this?

My Amazon Elastic Compute Cloud (Amazon EC2) instance failed its system status check and is no longer accessible. How do I troubleshoot system status check failures?Short descriptionSystem status check failures indicate that there is an issue with the hardware hosting your EC2 instance.

ResolutionThe instance must be migrated to a new, healthy host by stopping and starting the instance. You can wait for Amazon EC2 to perform the stop and start of your instance. Or, you can manually stop and start the instance to migrate it to a new, healthy host.Note: A stop and start isn't equivalent to a reboot. A start is required to migrate the instance to healthy hardware.Warning: Before stopping and starting your instance, be sure you understand the following:Instance store data is lost when you stop and start an instance. If your instance is instance store-backed or has instance store volumes containing data, the data is lost when you stop the instance. For more information, see Determining the root device type of your instance.If your instance is part of an Amazon EC2 Auto Scaling group, stopping the instance may terminate the instance. If you launched the instance with Amazon EMR, AWS CloudFormation, or AWS Elastic Beanstalk, your instance might be part of an AWS Auto Scaling group. Instance termination in this scenario depends on the instance scale-in protection settings for your Auto Scaling group. If your instance is part of an Auto Scaling group, then temporarily remove the instance from the Auto Scaling group before starting the resolution steps.Stopping and starting the instance changes the public IP address of your instance. It's a best practice to use an Elastic IP address instead of a public IP address when routing external traffic to your instance. If you are using Route 53, you might have to update the Route 53 DNS records when the public IP changes.If the shutdown behavior of the instance is set to Terminate, the instance is terminated if you shut down the instance from the operating system using the shutdown or poweroff command. To avoid this, change the instance shutdown behavior.In rare circumstances, the infrastructure-layer issue can prevent the underlying host from responding to the stop and start API calls. This causes the instance to be stuck in the stopping state. For instructions on how to force the instance to stop, see Troubleshooting stopping your instance.You can create an Amazon CloudWatch alarm that monitors and automatically recovers the EC2 instance from issues that involve underlying hardware failure.

Related informationWhy is my EC2 Linux instance unreachable and failing one or both of its status checks?I received a notice stating that Amazon EC2 detected degradation of the underlying hardware hosting my EC2 instance. What do I need to do?
Question: Why am I charged an early delete fee for Amazon S3 Glacier?

I deleted an Amazon Simple Storage Service (Amazon S3) Glacier archive and was charged a fee.

ResolutionAmazon S3 Glacier storage classes have a minimum storage duration charge. If you delete an archive before meeting the minimum storage duration, you are charged a prorated early deletion fee.Amazon S3 Glacier minimum storage duration depends on the storage class used. For a summary of minimum storage duration for each storage class, see Performance across the S3 storage classes.For information about Amazon S3 Glacier pricing and how early deletion fees are calculated, see Amazon S3 pricing.

Related informationAmazon S3 Glacier FAQs
Question: How do I troubleshoot API Gateway REST API endpoint 403 "Missing Authentication Token" errors?

When I try to invoke my Amazon API Gateway REST API, I get 403 "Missing Authentication Token" error messages. How do I troubleshoot these errors?Short descriptionAPI Gateway REST API endpoints return Missing Authentication Token errors for the following reasons:The API request is made to a method or resource that doesn't exist.The API request isn't signed when the API method has AWS Identity and Access Management (IAM) authentication turned on.The API might be configured with a modified Gateway response or the response comes from a backend integration.To troubleshoot other 403 errors for API Gateway, see How do I troubleshoot HTTP 403 errors from API Gateway?ResolutionConfirm that there's a method and resource configured in the API Gateway resource pathFollow the instructions in Set up a method using the API Gateway console. For more information, see Set up API resources.Important: You must deploy the API for the changes to take effect.For APIs with proxy resource integration where the request method is sent to the root resource, verify that there's a method configured under the root resource.Confirm that the API Gateway responses haven't been modified or the backend integration isn't sending the responseMake sure that the gateway responses aren't modified in the API. Also, make sure that the error isn't coming from the integration backend. Check the API Gateway execution logs and backend logs.Confirm that the API request is signed if the API method has IAM authentication turned onFor more information, see Signing AWS API requests and Elements of an AWS API request signature.Confirm that you're sending the correct HTTP method request to the REST API endpointTesting a REST API endpoint from a web browser automatically sends a GET HTTP method request.To test a POST HTTP method request, use a different HTTP client. For example: Postman or curl.Example curl command that uses the POST HTTP method request$ curl -X POST  <API URL> -d <request body>Example sending request with JSON header$ curl --location -X POST 'https://1234WXYZ.execute-api.us-east-1.amazonaws.com/stage/lambda_proxy' --header 'Content-Type: application/json' --data-raw '{"x":"y"}'Examples sending curl POST request with AWS V4 signature authentication$ curl -X POST "<ENDPOINT>" -d <data> --user <AWS_ACCESS_KEY>:<AWS_SECRET_KEY> --aws-sigv4 "aws:amz:<REGION>:<SERVICE>"$ curl -X POST "https://1234WXYZ.execute-api.us-east-1.amazonaws.com/stage/lambda_proxy" -d '{"x":"y"}' --user ABCD:1234 --aws-sigv4 "aws:amz:us-east-1:execute-api"Related informationHow do I activate IAM authentication for API Gateway REST APIs?
Question: Why doesn't my MSCK REPAIR TABLE query add partitions to the AWS Glue Data Catalog?

When I run MSCK REPAIR TABLE, Amazon Athena returns a list of partitions, but then fails to add the partitions to the table in the AWS Glue Data Catalog.

Short descriptionHere are some common causes of this behavior:The AWS Identity and Access Management (IAM) user or role doesn't have a policy that allows the glue:BatchCreatePartition action.The Amazon Simple Storage Service (Amazon S3) path is in camel case instead of lower case (for example, userId instead of userid).

ResolutionAllow glue:BatchCreatePartition in the IAM policyReview the IAM policies attached to the user or role that you're using to run MSCK REPAIR TABLE. When you use the AWS Glue Data Catalog with Athena, the IAM policy must allow the glue:BatchCreatePartition action. If the policy doesn't allow that action, then Athena can't add partitions to the metastore. For an example of an IAM policy that allows the glue:BatchCreatePartition action, see AmazonAthenaFullAccess managed policy.Change the Amazon S3 path to lower caseThe Amazon S3 path name must be in lower case. If the path is in camel case, then MSCK REPAIR TABLE doesn't add the partitions to the AWS Glue Data Catalog. For example, if the Amazon S3 path is userId, the following partitions aren't added to the AWS Glue Data Catalog:s3://awsdoc-example-bucket/path/userId=1/s3://awsdoc-example-bucket/path/userId=2/s3://awsdoc-example-bucket/path/userId=3/To resolve this issue, use lower case instead of camel case:s3://awsdoc-example-bucket/path/userid=1/s3://awsdoc-example-bucket/path/userid=2/s3://awsdoc-example-bucket/path/userid=3/Related informationPartitioning data in AthenaActions, resources, and condition keys for Amazon AthenaActions, resources, and condition keys for AWS Glue
Question: How do I troubleshoot a failed step in Amazon EMR?

I want to troubleshoot a failed step in my Amazon EMR cluster.

Short descriptionAmazon EMR identifies and returns the root cause of step failures for steps submitted using the Step API operation. Amazon EMR 5.x and later also returns the name of the relevant log file and a portion of the application stack trace through API.Note: You can use the following information to troubleshoot an Amazon EMR step of any application. For information specific to failed Apache Spark steps, see How do I troubleshoot a failed Spark step in Amazon EMR?ResolutionNote: For descriptions of the types of step logs, see Check the step logs.View step logs using the AWS Management consoleFor more information, see To view failure details using the AWS console in Enhanced step debugging.View step details using the AWS CLINote: If you receive errors when running AWS Command Line Interface (AWS CLI) commands, make sure that you’re using the most recent version of the AWS CLI.Use the describe-step command as shown in the following example. In the following command, replace cluster-id and the step-id with the correct values for your use case.aws emr describe-step --cluster-id j-1K48XXXXXHCB --step-id s-3QM0XXXXXM1WFor more information, see To view failure details using the AWS CLI in Enhanced step debugging.View step log files on the master node using SSHFor more information, see View log files on the master node.View log files archived in Amazon S31.    Open the Amazon Simple Storage Service (Amazon S3) console.2.    Select the S3 bucket specified as the S3 log URI where log files are archived.3.    Navigate to the following path and download the log file object: cluster-id/steps/step-id/.For more information, see View log files archived to Amazon S3.View step logs in the debugging toolNote: The debugging tool isn't turned on automatically in Amazon EMR. For information on turning on the debugging tool, see Turn on the debugging tool.For information on viewing step logs in the debugging tool, see View log files in the debugging tool.

Related informationHow do I cancel an Amazon EMR step?
Question: How do I set special parameters in an AWS Glue job using AWS CloudFormation?

I want to enable special parameters, such as --enable-metrics, for my job in AWS Glue. However, I get a template validation or "null values" error from AWS CloudFormation when I try to run my job. How do I resolve these errors?Short descriptionTo set special parameters for your job in AWS Glue, you must supply a key-value pair for the DefaultArguments property of the AWS::Glue::Job resource in CloudFormation. If you supply a key only in your job definition, then CloudFormation returns a validation error.Resolution1.    In your CloudFormation template, set the value of your special parameter to an empty string for the DefaultArguments property of your job definition.JSON:"MyJob": {  "Type": "AWS::Glue::Job",  "Properties": {    "Command": {      "Name": "glueetl",      "ScriptLocation": "s3://my-test//test-job1"    },    "DefaultArguments": {      "--job-bookmark-option": "job-bookmark-enable",      "--enable-metrics": ""    },    "ExecutionProperty": {      "MaxConcurrentRuns": 2    },    "MaxRetries": 0,    "Name": "cf-job3",    "Role": {      "Ref": "MyJobRole"    }  }}YAML:MyJob:  Type: 'AWS::Glue::Job'  Properties:    Command:      Name: glueetl      ScriptLocation: 's3://my-test//test-job1'    DefaultArguments:      '--job-bookmark-option': job-bookmark-enable      '--enable-metrics': ''    ExecutionProperty:      MaxConcurrentRuns:     MaxRetries: 0    Name: cf-job3    Role: !Ref MyJobRoleNote: In the preceding example JSON and YAML templates, the value of --enable-metrics is set to an empty string. The empty string validates the template and launches the resource that's configured with the special parameter.2.    To activate your special parameter, run your job.