VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: What do I need to know if my Free Tier period with AWS is expiring?

I received an email notifying me that the Free Tier period for my account is expiring.

ResolutionWhen your Free Tier period with AWS expires, you can continue to use services or stop using services.If you continue using AWS services, then all resources on your account are billed at On-Demand rates.If you stop using AWS services, then you must take additional actions to avoid incurring charges.Continue using AWS servicesReview the resources that you're using on a monthly basis.To view your monthly charges, do the following:Sign in to the AWS Management Console, and then open the AWS Billing and Cost Management console.In the navigation pane, on the left hand side, choose Bills.For Date, choose a month.Then, check the AWS Pricing for any resources that you're using to decide what to keep. If you accept that the resources on your account are billed at On-Demand rates, you don't need to take any action.You can use the AWS Pricing Calculator to estimate your monthly bill when AWS Free Tier has expired.Stop using AWS servicesIf you don't want to incur charges, do the following:Check for active resources.Delete, stop, or terminate the resources on your account.(Optional) If you want, you can then close your account. However, if you have no active resources or subscriptions, you can keep your account active without being billed.

Related informationAWS Free Tier FAQsHow do I view past or current AWS payments?Avoiding unexpected charges
Question: How do I perform common DBA tasks for Amazon RDS DB instances?

How do I perform common DBA tasks for Amazon Relational Database Service (Amazon RDS)?Short descriptionBecause Amazon RDS delivers a managed service experience, it does not provide shell access to DB instances. For this reason, RDS restricts access to certain system procedures and tables that require advanced privileges. See the following examples of some common tasks that you can't run in RDS by using standard commands:Bringing a database online when using Amazon RDS for SQL Server.Dropping a DB in a mirrored instance when using Amazon RDS for SQL Server.Killing an active session or query when using Amazon RDS for MySQL, Amazon Aurora MySQL, or MariaDB.Switching online log files when using Amazon RDS for Oracle.

ResolutionIf you receive a permission or privilege error message when running a command or when modifying a DB instance, see the following engine-specific resources:Common DBA tasks for Oracle DB instancesCommon DBA tasks for MySQL DB instancesCommon DBA tasks for MariaDBCommon DBA tasks for Microsoft SQL ServerCommon DBA tasks for PostgreSQLRelated informationGetting started with Amazon RDS
Question: How do I troubleshoot errors when running Amazon SageMaker training jobs?

I want to troubleshoot errors when running Amazon SageMaker training jobs.

ResolutionYour SageMaker training job might fail due to multiple reasons. To identify the reason for the failure, check the failure reason on the SageMaker console or through the DescribeTrainingJob API call. Use the following troubleshooting steps based on the error that you get when your training job fails.Internal Server ErrorIf your SageMaker training job failed with the Internal Server Error, retry the job to make sure that the job didn't fail due to a transient issue. If the job fails when you retry, then review the logs for training jobs on Amazon CloudWatch. You can find these logs in CloudWatch under the log group /aws/sagemaker/TrainingJobs in the log stream that looks similar to the following:example-training-job-name/algo-example-instance-number-in-cluster-example-epoch-timestampAlso, review job metrics, such as CPUUtilization, MemoryUtilization, and DiskUtilization to make sure that the failure didn't occur due to a resource crunch.You can access the training job logs and job metrics by doing the following:Open the SageMaker console.Choose Training jobs, and then choose the training job that you want to see the metrics for.Choose TrainingJobName.In the Monitor section, choose View logs.In the Monitor section, review the graphs of instance utilization.If you find that the job is using up all the resources, switch to a larger instance type, or attach a larger storage volume to the instance.For more information, see Monitoring training job metrics (SageMaker console).

Related informationMonitor and analyze training jobs using Amazon CloudWatch metricsLogs for built-in algorithms
Question: How can I troubleshoot the "entity already exists" error when an IAM user tries to create a new MFA device?

I tried to create a new multi-factor authentication (MFA) device for an AWS Identity and Access Management (IAM) user. I received an error similar to the following:"MFA Device entity at the same path and name already exists."The IAM user doesn't have any MFA devices. How can I resolve this issue?Short descriptionThis error occurs because an MFA device was created but wasn't enabled for use with any IAM users.

ResolutionFirst, deactivate the MFA device. Then, delete it using the AWS Command Line Interface (AWS CLI). Finally, recreate the MFA device.Note: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.1.    Run the following AWS CLI command list-virtual-mfa-devices to list all virtual MFA devices created in your AWS account:$aws iam list-virtual-mfa-devices2.    Note the MFA device serial number similar to the following format for use with step 4:arn:aws:iam::<account-id>:mfa/<username-path>3.    Run the AWS CLI command deactivate-mfa-device to deactivate the MFA device similar to the following:$aws iam deactivate-mfa-device --user-name <username> --serial-number arn:aws:iam::<account-id>:mfa/<username>Note: If you receive an error similar to the following, disregard it:An error occurred (NoSuchEntity) when calling the DeactivateMFADevice operation: MFA Device with serial number arn:aws:iam::<account-id>:mfa/<username-path> doesn't exist.4.    Run the AWS CLI command delete-virtual-mfa-device to delete the MFA device similar to the following:$aws iam delete-virtual-mfa-device --serial-number arn:aws:iam::<account-id>:mfa/<username-path>5.    Create a new MFA device.Follow the instructions to enable a virtual MFA device for an IAM user (console).-or-Follow the instructions to enable a virtual MFA device for an IAM user (AWS CLI or AWS API).

Related informationHow can I enforce MFA authentication for IAM users that use the AWS CLI?Using multi-factor authenticationHow do I use an MFA token to authenticate access to my AWS resources through the AWS CLI?
Question: How can I migrate data from one OpenSearch Service domain to another?

I want to move data from one Amazon OpenSearch Service domain to another.

Short descriptionYou can use manual snapshots to migrate individual indices or entire OpenSearch Service domains. You can migrate data to a domain in the same AWS account or to a domain in a different account.

ResolutionPrerequisites:You meet the manual snapshot prerequisites.Your OpenSearch Service client can send signed HTTP requests to your domain's endpoint.The source domain is compatible with the Elasticsearch version of the destination domain. For more information, see Snapshot and restore on the Elasticsearch website.Complete the following steps:1.    Register the same manual snapshot repository on both the source and destination domains. Your destination is usually an Amazon Simple Storage Service (Amazon S3) bucket.Note: You can use server-side encryption with Amazon S3 managed keys (SSE-S3) to encrypt the S3 bucket that you use as the snapshot repository.2.    (Optional) If you're migrating to another account, then attach a policy to the source S3 bucket that grants cross-account permissions to the destination.3.    Take a manual snapshot of the source domain.4.    Use the _restore API to restore the snapshot to the destination domain.

Related informationHow do I resolve the "cannot restore index [.kibana]" error in Amazon OpenSearch Service?I get a "User: anonymous is not authorized" error when I try to access my Amazon OpenSearch Service clusterHow can I copy S3 objects from another AWS account?How can I provide cross-account access to objects that are in Amazon S3 buckets?
Question: How do I configure DNSSEC for my subdomain registered with Route 53 or another registrar?

I want to configure Domain Name System Security Extensions (DNSSEC) for my domain name registered with Amazon Route 53 or another registrar.

Short descriptionTo turn on DNSSEC signing for your domain, you must: first on DNSSEC signing and create a key-signing key (KSK). Then, establish a chain of trust by registering the Delegation Signer (DS) record with the parent hosted zone in Route 53.Important: For top-level domains (TLD), see How do I turn on DNSSEC on my domain with Amazon Route 53 and register a DS record?ResolutionNote: 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.    Follow the steps to turn on DNSSEC signing, and then create a KSK.2.    Confirm that your parent hosted zone is in the SIGNING status.3.    Follow the steps to establish a chain of trust.Note: In the AWS CLI, you can use the get-dnssec command to get the DS record of your parent hosted zone. Example output from the get-dnssec command:$ aws route53 get-dnssec --hosted-zone-id Zyyyyyyyyyyyyyyyyyyyy{    "Status": {        "ServeSignature": "SIGNING"    },    "KeySigningKeys": [        {            "Name": "forKnowledgeCenter",            "KmsArn": "arn:aws:kms:us-east-1:nnnnnnnnnnnn:key/4a7a9720-91b5-49d5-8069-79634593a1b9",            "Flag": 257,            "SigningAlgorithmMnemonic": "ECDSAP256SHA256",            "SigningAlgorithmType": 13,            "DigestAlgorithmMnemonic": "SHA-256",            "DigestAlgorithmType": 2,            "KeyTag": 1101,            "DigestValue": "57BB41C3E5F8606F64D6926D4EA80A2D5139FCD029828CDE00E94D78882819DE",            "PublicKey": "ELfupc8RXEcoLl8AZiDX6LOInJMc1h7MDnuIEAWzJIG6vOB0QAOfRzFHT15WwGzXPZKqrTkSSTm+CSQlIfCWbg==",            "DSRecord": "1101 13 2 57BB41C3E5F8606F64D6926D4EA80A2D5139FCD029828CDE00E94D78882819DE",            "DNSKEYRecord": "257 3 13 ELfupc8RXEcoLl8AZiDX6LOInJMc1h7MDnuIEAWzJIG6vOB0QAOfRzFHT15WwGzXPZKqrTkSSTm+CSQlIfCWbg==",            "Status": "ACTIVE",            "CreatedDate": "2020-12-21T13:58:49.719000+00:00",            "LastModifiedDate": "2020-12-21T13:58:49.719000+00:00"        }    ]}4.    Complete the following steps to register the DS record with your parent hosted zone:Open the Route 53 console.In the navigation pane, choose Hosted zones.Select the name of your parent hosted zone.Choose Create record.For Routing policy, choose Simple routing.For Record type, choose DS - Delegation Signer.For Record name, enter the name of the domain or subdomain that you want to route traffic for. The default value is the name of the hosted zone.For Value, specify the DS Record value obtained from step 3. The format is [key tag] [signing algorithm type] [digest algorithm type] [digest].For TTL, specify 3600 seconds.

Related informationTroubleshooting DNSSEC signing
Question: Why did my ACM certificate request fail with additional verification required?

I tried to request an AWS Certificate Manager (ACM) certificate for my domain. The status is Failed with an error similar to the following:"Additional verification required to request certificates for one or more domain names in this request".

Short descriptionThis occurs as a fraud-protection measure if your domain ranks within the Alexa top 1000 websites. For more information, see Alexa Top Sites.

ResolutionUse the AWS Support Center to contact AWS Support. AWS Support will assist you with adding your domains to an allow list. For more information, see Error message: Additional Verification Required.Note: You can't request a certificate for Amazon-owned domain names, such as those ending in amazonaws.com, cloudfront.net, or elasticbeanstalk.com.

Related informationCertificate request failsIssuing and managing certificates
Question: How do I troubleshoot ELB health checks with Elastic Beanstalk?

I want to troubleshoot failed Elastic Load Balancing (ELB) health checks for my Amazon Elastic Compute Cloud (Amazon EC2) instance in my AWS Elastic Beanstalk environment.

ResolutionConfirm that your EC2 instance security group allows all ingress traffic from your ELB security groupOpen the Elastic Beanstalk console.Select your environment.In the navigation pane, choose Configuration.In the Configuration overview section, for the Instances category, copy the value for EC2 security groups (for example: awseb-e-krkbukb3ww-stack-AWSEBSecurityGroup-IOXAVM).Open the Amazon Virtual Private Cloud (Amazon VPC) console.In the navigation pane, choose Security Groups.In the search bar, paste in the name of the security group that you copied in step 4. Then, select this security group.Choose the Inbound Rules tab and then confirm that your security group has a rule that allows all traffic from the ELB security group.Note: For more information, see Configure security groups for your Classic Load Balancer.Confirm that your ELB security group egress rule allows traffic on the application portOpen the Amazon EC2 console.In the navigation pane, in the LOAD BALANCING section, choose Load Balancers.On the Description tab for your load balancer, in the Security section, choose your security group.Choose the Outbound tab for your security group and then confirm that your security group has an egress rule that meets your requirements.Note: For more information on adding, updating, and/or deleting security group rules, see Work with security group rules-,Work%20with%20security%20group%20rules,-The%20following%20tasks).Confirm that your network access control list (ACL) allows the required ingress and egress trafficOpen the Amazon VPC console.In the navigation pane, in the Virtual Private Cloud section, choose Subnets.Select the subnet attached to your Elastic Beanstalk EC2 instance.Choose the Network ACL tab and then confirm that the inbound and outbound rules meet your traffic requirements.Note: For more information on adding and deleting rules from an ACL, see Add and delete rules.Confirm that the health check path is properly set for your applicationSet the health check path for your type of load balancer:Classic Load BalancerApplication Load BalancerNetwork Load BalancerConfirm that your web server logs show no errorsTo confirm that there are no errors, view the logs from the EC2 instances in your Elastic Beanstalk application.

Related informationControl traffic to subnets using Network ACLsSecurity groups
Question: How can I improve networking performance on my Amazon EC2 Windows instance?

I’m running an Amazon Elastic Compute Cloud (Amazon EC2) Windows instance, and I want to take advantage of improved networking enhancements.

Short descriptionYou can activate enhanced networking to achieve higher bandwidth, higher packet-per-second performance, and consistently lower latency. All current generation instance types except T2 instances support enhanced networking. Supported instance types use either the Elastic Network Adapter (ENA) or the Intel 82599 Virtual Function (VF) interface.

ResolutionFor supported instance types, first determine the enhanced networking mechanism that's available for your instance type. Then, use the ENA or the Intel 82599 VF interface to activate enhanced networking.For T2 instances, and as a best practice for all instance types, be sure to upgrade AWS PV drivers on Windows Server.Note: If the instance is a domain controller, then upgrade AWS PV drivers on the domain controller.

Related informationSummary of networking and storage features
Question: How do I troubleshoot the error "Cannot create a replica of table" when I try to add a replica to an Amazon DynamoDB global table?

I'm trying to add a replica to an Amazon DynamoDB global table. but the operation fails with the exception “LimitExceededException” and throws an error "Cannot create a replica of table".

ResolutionThis error occurs when the write throughput for the DynamoDB global table exceeds the default Regional quota of 40,000 at table level. In this case, you must request a service quota increase for add replica quota write capacity units (WCU). Global tables implement checks when you add a replica to be sure that the table has sufficient capacity to replicate writes.You can create a case in the AWS Support Center to request a quota increase for DynamoDB global tables. When you submit your quota increase request, be sure to provide the following information:Table names of the global tableAll Regions where you need the global table to have replicas, including existing RegionsSteady state WCU utilization of the global tablePeak WCU utilization of the global tableYou're notified through an email when your request is approved.

Related informationService, account, and table quotas in Amazon DynamoDB
Question: Can I change the environment variables in a published version of my Lambda function?

I want to change the environment variables in a published version of my AWS Lambda function. Can I do that?Short descriptionYou can't change the configuration (which includes environment variables) or function code in a  published Lambda function version.To change the environment variables of a published Lambda function version, you must first change the current, unpublished function version ($LATEST). Then, publish a new function version.Note: Consider creating a Lambda alias to point to a function version that's configured with the environment variables that you want to use. Using aliases allows you to avoid hard-coding a specific function version into your app.

ResolutionNote: 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.Change the unpublished function versionTo change environment variables in the $LATEST version of your Lambda function, use one of the following:The Lambda console.The update-function-configuration command in the AWS CLI.Lambda API calls in the AWS SDKs.Publish a new function versionAfter changing environment variables in the $LATEST version, publish your updated Lambda function using the Lambda console or the PublishVersion API. For more information, see Managing Versions with the Lambda API.

Related informationUpdateFunctionConfiguration (AWS Lambda Developer Guide API reference)Environment (AWS Lambda Developer Guide API reference)
Question: How do I delete a Route 53 hosted zone created by service discovery?

I'm trying to delete an Amazon Route 53 (Route 53) hosted zone created by service discovery in the AWS console. However, I'm receiving an error. How do I delete a Route 53 hosted zone created by service discovery?Short descriptionHosted zones that were created by service discovery can't be deleted from the Route 53 console. Hosted zones created by service discovery can be deleted only by using either the AWS Cloud Map console or a servicediscovery API call. Remember:Before you can delete a namespace, you must delete all services that were created in the namespace.Before you can delete a service, you must deregister all instances registered that were using the service.

ResolutionFind the namespace in AWS Cloud MapOpen the AWS Cloud Map console.Choose the Region where the namespace was created from the Region selector in the navigation bar.In the navigation pane, choose Namespaces.Select the namespace associated with the hosted zone that you want to delete.Remove all associated servicesSelect a service name from the Services section.Select each instance in the Service instances list, and then choose Deregister.After you've deregistered all instances from the service, choose Delete at the top right of the service page to delete the service.Repeat these steps for each associated service until all services are deleted.Delete the namespaceAfter all services are deleted, choose Delete at the top right of the namespace page to delete the namespace.Choose Delete in the confirmation window.When you delete the namespace, the associated Route 53 hosted zone is automatically deleted.
Question: How do I link an Amazon EMR notebook to a Git repository?

I want to link my Amazon EMR notebook with a Git repository.

ResolutionAssociating Git repositories with Amazon EMR notebooks allows you to save your notebooks in a version-controlled environment. You can associate up to three repositories with a notebook.To create a new EMR notebook and then associate it with an existing Git repository, do the following:1.    Create a private subnet in a virtual private cloud (VPC).2.    Create a NAT gateway.3.    Update the route table to point to the NAT gateway.4.    Launch an Amazon EMR cluster in the private subnet. In the Software configuration section, be sure that you select a configuration that includes Apache Spark, Apache Hadoop, and Apache Livy.5.    When you're waiting for the EMR cluster to reach the WAITING state, add the Git repository. For Git credentials, choose Create a new secret. Be sure that the Username is the alias of the Git account and not the email address. For more information, see Working with aliases.6.    Create a security group with the following outbound rules:Rule 1Type: Custom TCP ruleProtocol: TCPPort Range: 18888Destination: ElasticMapReduceEditors-LivyRule 2Type: HTTPSProtocol: TCPPort Range: 443Destination: 0.0.0.0/0This allows the notebook to reach the internet using the cluster. For more information, see Custom EC2 security group for EMR notebooks when associating notebooks with Git repositories.7.    Add an inbound rule to the ElasticMapReduceEditors-Livy security group:Type: Custom TCP ruleProtocol: TCPPort Range: 18888Destination: Enter the name of the security group that you created in the previous step.8.    Modify the service role for EMR notebooks (EMR_Notebooks_DefaultRole) to allow the secretsmanager:GetSecretValue action.9.    Create an EMR notebook with the following security group settings:In the Security groups section, select Choose security groups.For Security groups for master instance, choose ElasticMapReduceEditors-Livy.For Security groups for notebook instance, choose the security group that you created in step 6.The Git repository status changes to Linked. You can now use the Git repository in the notebook.

Related informationAssociating Git-based repositories with EMR notebooksEMR notebooks