VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: How do I resolve the error "SMTP server requires a secure connection or the client is not authenticated. The server response was: Authentication required" while sending an email through SES?

I want to send an email using Amazon Simple Email Service (SES). However, I receive the error, "SMTP server requires a secure connection or the client is not authenticated. The server response was: Authentication required".

Short descriptionThis error indicates that the sending application didn't attempt to authenticate when it connected to the Amazon SES SMTP interface. Usually this error is seen if the SES API call request was signed using AWS Signature version 2 (SigV2), instead of AWS Signature version 4 (SigV4).Note: If you created your SMTP credentials before January 10, 2019, your SMTP credentials were created using an older version of AWS SigV2. Credentials created after that date use AWS SigV4 by default.

ResolutionCheck the creation time of the SMTP user by following these steps:Sign in to the AWS Management Console, and then open the AWS Identity and Access Management (IAM) console.In the navigation pane, choose Users, and then choose the SMTP user name.A new page loads. You can find "creation time" under summary.If your SMTP user was created before January 10, 2019, then you receive an error because requests are signed using AWS SigV2.To resolve the issue, create a new SMTP user from the SES console, and then replace the older SMTP user from your sending application. You can also derive the AWS Sigv4 SMTP username and password from IAM user by converting existing AWS credentials.If the issue persists, or if your SMTP user was created after January 10, 2019, then open a case with SES support to investigate further.
Question: How do I troubleshoot black screen and white screen issues in WorkSpaces?

My Amazon WorkSpaces client connection fails after client authentication was successful with a black screen or a white screen. Why does this happen and how can I troubleshoot the issue?Short descriptionAfter authenticating your Amazon WorkSpaces client, problems with connectivity might cause the following issues:A white screen that appears along with a “Disconnected” message. This issue is typically the result of blocked inbound traffic between a WorkSpace and a client device.A black screen that appears while connecting. This typically indicates an interruption in the UDP stream from Amazon WorkSpaces to a client device. This often occurs when the outbound UDP stream on ports 50002 and 55002 is not allowed on the client side.

ResolutionTo resolve connectivity issues that result in a white screen or a black screen, perform the following steps.Verify inbound and outbound trafficMake sure that inbound and outbound streaming protocol traffic is allowed between the WorkSpaces streaming gateways and the client device.On your local device, validate your networking and access settings depending on your setup:PCoIP gateway serversWorkSpaces Streaming Protocol (WSP) gateway serversVerify local firewall settingsOn your local device, make sure that your firewall and any other security applications aren’t blocking the streaming protocol traffic.If your firewall uses stateless filtering, then open ephemeral ports 49152–65535 to allow for return communication. If your firewall uses stateful filtering, then the ephemeral ports 50002 and 55002 are automatically open to allow for return communication.Verify WorkSpace firewall settingsUse Remote Desktop Protocol (RDP) to sign in to your WorkSpace as a user or the domain administrator. In your WorkSpace, make sure that your firewall and security applications aren’t blocking the streaming protocol traffic that’s flowing through your management network’s network adapter.Verify WorkSpaces traffic settingsIn the WorkSpaces console, verify that your WorkSpaces security groups allow the necessary traffic. Customized security group rules might cause traffic interruptions.Verify WorkSpaces streaming traffic settingsUse RDP to sign in to the WorkSpace IP from another WorkSpace or from an Amazon Elastic Compute Cloud (Amazon EC2) instance in the WorkSpaces subnet.Note: You can find the WorkSpace IP in the WorkSpaces console.Confirm with your network team that streaming protocol traffic is allowed through the network devices and the infrastructure.Confirm communication between the client device and a streaming gateway by using a tool, such as WireShark, to capture traffic.

Related informationPorts for client applicationsControl traffic to resources using security groups
Question: How do I delete a Route 53 hosted zone?

I want to delete an Amazon Route 53 hosted zone.

ResolutionImportant: You can't undo the deletion of a hosted zone. The assigned name servers stop responding to the domain name queries after zone deletion.To delete a Route 53 hosted zone:1.    If applicable, verify that DNSSEC signing is turned off on the hosted zone. For information, see Turn off DNSSEC signing.2.    Delete any records associated with the hosted zone, except for the default start of authority (SOA) and name server (NS) records.Note: Failing to delete the records before attempting to delete the hosted zones causes the following error:Error occurredBefore you can delete a hosted zone, you must first delete all resource record sets except the NS and SOA resource record sets for the zone apex.(HostedZoneNotEmpty 400: The specified hosted zone contains non-required resource record sets and so cannot be deleted.)3.    Delete your public hosted zone or delete your private hosted zone.If you created your hosted zone using service discovery, then you can't delete the zone using the Route 53 console. Delete hosted zones created using service discovery through the AWS Cloud Map console or a servicediscovery API call. For more information, see How do I delete a Route 53 hosted zone created by service discovery?Note: Deleted hosted zones no longer route traffic. If you create a new hosted zone for your domain later, update the NS record to route traffic to the new zone.

Related informationWorking with public hosted zonesWorking with private hosted zones
Question: How can I turn Service Broker on and off for Amazon RDS SQL Server?

How can I turn on and turn off Service Broker for Amazon Relational Database Service (Amazon RDS) SQL Server?Short descriptionService Broker is supported for Amazon RDS, but Service Broker endpoints aren't supported on Amazon RDS. For more information about Service Broker, see the Microsoft documentation for Service Broker.

ResolutionWhen you turn on Service Broker, Amazon RDS requests a database lock. Before turning on Service Broker, close all open connections to the database.1.    Check to see whether Service Broker is turned on:select name,is_broker_enabled from sys.databaseswhere name= [YourDB]2.    If Service Broker isn't turned on, then generate a new Service Broker:ALTER DATABASE [YourDB] SET NEW_BROKER;GO3.    Turn on Service Broker on an existing database:ALTER DATABASE [YourDB] SET ENABLE_BROKER;GOIf you run a Multi-AZ deployment, then run this command:ALTER DATABASE [YourDB] SET PARTNER OFF;GOThen, turn on Service Broker again in a Multi-AZ deployment:ALTER DATABASE [YourDB] SET ENABLE_BROKER WITH ROLLBACK IMMEDIATETo turn off Service Broker on an existing database, run this command:ALTER DATABASE [YourDB] SET DISABLE_BROKER;GOYou can't turn on Service Broker on a database that is already part of an availability group. If you run the above resolution on such a database, then you receive an error similar to the following:ALTER DATABASE [test] SET PARTNER OFF;<br>GO <br>Msg 1416, Level 16, State 1, Line 1<br>Database "test" is not configured for database mirroring.Instead, turn on Service Broker before adding it to the availability group. To do this, convert the RDS database to single AZ, and then turn on Service Broker.Convert your RDS database to Single AZ.Turn on Service Broker:<p>ALTER DATABASE [DBName ] SET NEW_BROKER;<br>GO</p><p>ALTER DATABASE [DBName ] SET ENABLE_BROKER;<br>GO</p>Verify that Service Broker is turned on:select name,is_broker_enabled from sys.databases<br> where name= [DBName ]Convert your RDS database back to Multi-AZ.

Related informationMicrosoft SQL Server on Amazon RDSMigrating Microsoft SQL Server databases to the AWS Cloud
Question: How can I revoke access to a Client VPN endpoint for a specific client?

I created an AWS Client VPN endpoint with certificate-based authentication for multiple clients. How can I revoke access to the Client VPN endpoint for a specific client?Short DescriptionYou can use certificate revocation lists to block specific client certificates. Blocking clients revokes their access to a Client VPN endpoint.To revoke a client certificate, you must:Generate a client certificate revocation listImport a client certificate revocation list(Optional) Export the client certificate revocation list

ResolutionGenerate a client certificate revocation list using OpenVPN easy-rsa1.    Clone the OpenVPN easy-rsa repository as a local repository on your local computer.$ git clone https://github.com/OpenVPN/easy-rsa.git2.    Open the easy-rsa/easyrsa3folder in your local repository.$ cd easy-rsa/easyrsa33.    Revoke the client certificate, and then generate the client revocation list.$ ./easyrsa revoke client_certificate_nameType yes when prompted.$ ./easyrsa gen-crlUsing SSL: openssl OpenSSL 1.0.2g  1 Mar 2016Using configuration from /home/easy-rsa/easyrsa3/pki/easy-rsa-31222.LsDpvT/tmp.t5FIi8An updated CRL has been created.CRL file: /home/easy-rsa/easyrsa3/pki/crl.pemThe certificate revocation list file is created at /easy-rsa/easyrsa3/pki/crl.pem.Import the certificate revocation list file to the client certificate revocation list**Important:**After importing the certificate revocation list file to the client certificate revocation list, your client's access to the Client VPN endpoint is permanently revoked.1.    Open the Amazon Virtual Private Cloud (Amazon VPC) console.2.    In the navigation pane, choose Client VPN Endpoints.3.    Select the Client VPN endpoint where you plan to import the client certificate revocation list.4.    Choose Actions, and then choose Import Client Certificate CRL.5.    Copy the contents of the client certificate revocation list file crl.pem.$ cat pki/crl.pem-----BEGIN X509 CRL-----Base64–encoded certificate-----END X509 CRL-----6.    For Certificate Revocation List, enter the content of the client certificate revocation list file. Then, choose Import CRL.Or, you can import the client certificate revocation list using the AWS Command Line Interface (AWS CLI):aws ec2 import-client-vpn-client-certificate-revocation-list --certificate-revocation-list file:path_to_CRL_file --client-vpn-endpoint-id endpoint_id --region region(Optional) Export the client certificate revocation list1.    Open the Amazon VPC console.2.     In the navigation pane, choose Client VPN Endpoints.3.    Select the Client VPN endpoint from where you plan to export the client certificate revocation list.4.    Choose Actions, and then choose Export Client Certificate CRL.5.    Choose Yes, and then choose Export.Or, you can export the client certificate revocation list using the AWS CLI:aws ec2 export-client-vpn-client-certificate-revocation-list --client-vpn-endpoint-id endpoint_idRelated InformationClient Certification Revocation Lists
Question: How can I get my CloudFormation stack to update if it's stuck in the UPDATE_ROLLBACK_FAILED state?

My AWS CloudFormation stack is stuck in the UPDATE_ROLLBACK_FAILED state.

Short descriptionIf your stack is stuck in the UPDATE_ROLLBACK_FAILED state after a failed update, then the only actions that you can perform on the stack are the ContinueUpdateRollback or DeleteStack operations. This is because CloudFormation requires further input from you to acknowledge that the stack is out of sync with the template that the stack is attempting to roll back to. To retry the rollback and resolve the error, you can use ContinueUpdateRollback.Tip: To resolve the error, you might need to raise limits, change permissions, or modify other settings. For information on common errors that cause update rollback failures, see Update rollback failed.In some cases, retrying the rollback doesn't resolve the error. In these cases, you must skip resources, and also acknowledge that these resources no longer reflect the desired state in the CloudFormation template. To skip the resources that caused the rollback failures, complete the following steps in the Resolution section.

ResolutionYou can roll the stack back to a working state with either the CloudFormation console or 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 AWS CLI version.CloudFormation console1.    Open the CloudFormation console.2.    From the navigation pane, choose Stacks.3.    From the Stack name column, select the stack that's stuck in UPDATE_ROLLBACK_FAILED status.4.    If you don't want to skip resources, choose Stack Actions, and then choose Continue update rollback.-or-If you want to skip FAILED resources during rollback, complete the following:1.    From the Stack name column, select the stack that's stuck in UPDATE_ROLLBACK_FAILED status.2.    Choose Stack Actions, and then choose Continue update rollback.3.    In the Continue update rollback dialog box, expand Advanced troubleshooting.4.    In the Resources to skip - optional section, select the resources that you want to skip.5.    Choose Continue update rollback.AWS CLIIn the AWS CLI, run the continue-update-rollback command. For example:$ aws cloudformation continue-update-rollback --stack-name awsstackname123 --resources-to-skip awsfaultyresource123Note: Replace awsstackname123 with the name of your stack. Replace awsfaultyresource123 with the logical IDs of your resources.Important: CloudFormation sets the status of specified resources to UPDATE_COMPLETE. Then, CloudFormation continues to roll back the stack. After the rollback is complete, the state of the skipped resources is inconsistent with the state of the resources in the stack template. Before performing another stack update, update the stack or resources to be consistent with each other. If you don't do this, subsequent stack updates can fail, and the stack becomes unrecoverable.If you have nested stacks that must be rolled back to a working state, see Using ResourcesToSkip to recover a nested stacks hierarchy.
Question: What currencies does AWS currently support?

I want to pay my bill in a currency other than US dollars (USD). What currencies does AWS support?ResolutionAWS generates invoices in US dollars (USD) by default. For supported payment methods, see What payment methods does AWS accept?Important: Your seller of record information and location might impact your available local currencies. For location specific information see, Amazon Web Services Tax Help.AWS supports the following currencies:AUD – Australian DollarBRL – Brazilian RealCAD – Canadian DollarCHF – Swiss FrancCNY – Chinese Yuan (China UnionPay and Bank Redirect)DKK – Danish KroneEUR – EuroGBP – British PoundHKD – Hong Kong DollarJPY – Japanese YenKRW – South Korean WonMYR – Malaysian RinggitNOK – Norwegian KroneNZD – New Zealand DollarSEK – Swedish KronaSGD – Singapore DollarUSD – United States DollarZAR – South African RandNote:Only credit card payments are supported for NOK. Invoices with terms on NOK aren't supported.Only invoices with terms are supported for SGD. Credit card payments on SGD aren't supported for Amazon Web Services Inc. (AWS Inc.)Amazon Web Services Singapore Private Limited (AWS Singapore) supports only SGD for credit cards.For instructions on how to choose a different currency for your account, see Changing which currency you use to pay your bill.
Question: "How do I create, launch an instance from, or troubleshoot a custom Amazon Machine Image (AMI)?"

I want to create an Amazon Machine Image (AMI) of my existing Amazon Elastic Compute Cloud (Amazon EC2) instance. How do I create, launch an instance from, or troubleshoot an AMI?Short descriptionAMIs are archival copies of instances that you can use to launch other instances. You can use custom AMIs in multiple scenarios based on your specific use case.

ResolutionHow do I create a custom AMI?For information on creating a custom AMI, see the following:Create a custom Windows AMICreate an AMI (Linux)How do I create an AMI that's based on my Amazon Elastic Block Store (Amazon EBS)-backed EC2 instance?How to create a custom AMI with encrypted Amazon EBS snapshots and share it with other accounts and RegionsHow can I use Sysprep to create and install custom reusable Windows AMIs?How do I launch an instance from a custom AMI?For more information, see How do I launch an EC2 instance from a custom Amazon Machine Image (AMI)?How do I share a custom AMI?For information on sharing a custom AMI, see the following:How do I create and copy an Amazon Machine Image (AMI) from one AWS Region to another?How do I share an Amazon Machine Image (AMI) privately with another AWS account?How do I transfer an Amazon EC2 instance or AMI to a different AWS Account?How to share encrypted AMIs across accounts to launch encrypted EC2 instancesHow do I use VM Import/Export to export a VM based on my Amazon Machine Image (AMI)?How do I troubleshoot AMIs?For information on troubleshooting AMIs, see the following:Why can't I connect to my Amazon EC2 Windows instance that was launched from a custom AMI?Why is my EC2 AMI or EBS snapshot creation slow?Why can’t I launch EC2 instances from my copied AMI?How can I recover an accidentally deleted AMI?Why are some instance types disabled when I'm trying to launch an EC2 instance from an AMI?What can I do when the AMI that my EC2 instance uses is no longer public or when I see the error "Cannot load details for ami-xxxxxx. You may not be permitted to view it."?Related informationAWS Windows AMIsAmazon Machine Images (AMI)Linux
Question: How do I troubleshoot issues related to EC2 origins in CloudFront?

I'm using an Amazon Elastic Compute Cloud (Amazon EC2) instance as the custom origin for my Amazon CloudFront distribution. CloudFront returns an error. Why is this happening and how can I troubleshoot this?ResolutionBased on the type of error that CloudFront returns, see the related section for troubleshooting steps.CloudFront returns 502 errorsThere are four reasons that CloudFront returns a 502 error when Amazon EC2 is configured as the custom origin. See the following guides for troubleshooting steps:SSL/TLS negotiation failure between CloudFront and custom EC2 origin serverSSL/TLS certificate on the origin is expired, invalid, self-signed, or the certificate chain is in the wrong orderOrigin is not responding on specified ports in origin settingsCloudFront was not able to resolve your origin domain due to DNS issuesCloudFront returns 503 errorsIf your CloudFront behavior has caching turned off, all requests are directed to the origin EC2 instance instead of being service from the CloudFront cache. In this case, the origin EC2 instance can become overwhelmed with large number of incoming requests, and then returns a 503 error.For troubleshooting 503 errors, see Origin server does not have enough capacity to support the request rate.If CloudFront can't route the request to the next best available edge location, and doesn't satisfy a request, then it returns a 503: Capacity exceeded error. For more information, see CloudFront caused the error due to resource constraints at the edge location.CloudFront returns 504 errorsThere are two reasons that CloudFront returns a 504 error when Amazon EC2 is configured as the custom origin for the CloudFront distribution:The origin returned an HTTP 504 status code to CloudFront.The origin didn’t respond before the request expired.For troubleshooting steps, seeHTTP 504 status code (Gateway Timeout).Redirect errorsIf you see a redirect error in your browser, check the network section in your browser developer tools. If you see multiple instances of the same request to the CloudFront distribution, then redirections are causing the browser error.To resolve redirect errors:Check for any location headers in the response header. A location header indicates that when the request is made the redirection is sent to the value in the location header. To troubleshoot this problem, check any redirection rules or configurations on the location where the redirections are sent.Check for the Server response header. For example, if the Server value is set to the HTTP server that your EC2 server is hosting the contents on, then there is a redirection configured on the EC2 origin. Check the server in the response header to troubleshoot.
Question: What's the difference between an instance store and an EBS volume?

I want to store data that's associated with my Amazon Elastic Compute Cloud (Amazon EC2) instance. I don't know whether I should use the instance store or an attached Amazon Elastic Block Store (Amazon EBS) volume.

ResolutionSome Amazon EC2 instance types come with a form of directly attached, block-device storage known as an instance store. Use the instance store for temporary storage. Data that's stored in instance store volumes isn't persistent through instance stops, terminations, or hardware failures.For data that you want to retain longer, or if you want to encrypt the data, use Amazon EBS volumes instead. EBS volumes have the following features:EBS volumes preserve their data through instance stops and terminations.You can back up EBS volumes with EBS snapshots.You can remove EBS volumes from one instance, and reattach them to another.EBS volumes support full-volume encryption.To prevent unintentional changes or data loss, it's a best practice to frequently create snapshots. You can use AWS Backup to automate snapshot creation.Note: In Amazon EBS, the DeleteOnTermination attribute for an instance's root volume is set to true by default. If you don't change this attribute, then the instance's root volume is deleted when the instance terminates. To change the DeleteOnTermination attribute to false, see How can I prevent my Amazon EBS volumes from being deleted when I terminate Amazon EC2 instances?Related informationStorageAmazon Elastic Block Store (EBS)Amazon EBS pricing