VishaalY/solutions-architect-hf-dataset huggingface dataset:
Question: "Can I recover the public IP address or Elastic IP address associated with an EC2 instance, and how can I avoid these being changed in the future?"

I stopped and started my Amazon Elastic Compute Cloud (Amazon EC2) instance, and then the public IP address associated with the instance changed. Or, I accidentally released the Elastic IP address associated with my instance. Are IP addresses recoverable, and how can I avoid this happening in the future?ResolutionPublic IP addressesYou can't manually associate or disassociate a public IP address from your instance. An instance's public IP address changes in the following scenarios:Stopped or hibernated instances receive a new public IP address when started again.If an instance's associated Elastic IP address is disassociated from the instance, then it receives a new public IP address.When a public IP address is no longer associated with an instance, that address is returned to the public IP pool. You can't recover the same public IP address for your stopped instance.Elastic IP addressesIt's a best practice to use an Elastic IP address. Elastic IP addresses are allocated to your account, instead of to the instance. You can associate your Elastic IP addresses to and from instances as needed.If you release the Elastic IP address that was allocated to your account, you might be able to recover it. For more information, see Recovering an Elastic IP address.All instances retain their associated Elastic IP addresses when stopped. AWS continues to bill for Elastic IP addresses associated with a stopped instance.Note: You can't convert an auto-assigned dynamic public IP address to an Elastic IP address.

Related informationStop and start your instanceAllocateAddress
Question: How can I recover an accidentally deleted AMI?

I accidentally deleted my Amazon Machine Image (AMI). How can I recover it?Short descriptionIt isn't possible to restore or recover a deleted or deregistered AMI. However, you can create a new, identical AMI using one of the following:Amazon Elastic Block Store (Amazon EBS) snapshots that were created as backups.Amazon Elastic Compute Cloud (Amazon EC2) instances that were launched from the deleted AMI.Note: For security and privacy reasons, AWS Support doesn't have visibility or access to customer data. If you don't have backups of your deleted AMI, AWS Support can't recover it for you. For more information on the security of customer data, see Shared responsibility model.

ResolutionRestore the AMI from an EBS snapshotWhen you delete or deregister an Amazon EBS-backed AMI, any snapshots created for the volume of the instance during the AMI creation process are retained. If you accidentally delete the AMI, you can launch an identical AMI using one of the retained snapshots.For instructions on how to create an AMI from a snapshot, see Creating a Linux AMI from a snapshot.Restore the AMI from an EC2 instanceIf both the AMI and the snapshots are deleted, you can recover the AMI from any EC2 instance that launched using the deleted AMI.Note: Unless you have selected the No reboot option on the instance, performing the following procedure reboots the instance. For more information on the No reboot option, see step 6 in Creating a Linux AMI from an instance.Open the Amazon EC2 console.Choose Instances, and then select the instance that you want to use to create the AMI.Select Actions, Image, Create Image.For more information on how to create an AMI from an instance, see Creating a Linux AMI from an instance.

Related informationHow do I re-create a terminated EC2 instance?How do I protect my data against accidental EC2 instance termination?
Question: "Why isn’t the Start menu, Action Center, or Cortana Search responding after I rebuilt my Windows 10 BYOL WorkSpace?"

My Start menu, Action Center, or Windows Search isn't working after rebuilding my Amazon WorkSpaces Windows 10 Bring Your Own License (BYOL) WorkSpace. How can I fix this?Short descriptionWhen you rebuild a WorkSpace, a new WorkSpace is created from the custom bundle. However, the D:\ drive, which contains the user profile, restores from the latest Amazon Elastic Block Store (Amazon EBS) snapshot of the volume.The user profile's TileDataLayer database is closely integrated with the Start menu, Action Center, and Cortana Search. A WorkSpace rebuild can create a mismatch between the information that the new Operating System has and the modified database within the user profile.This issue can affect WorkSpaces that are launched or rebuilt from a custom bundle created before May 2019.Your Windows 10 WorkSpace might exhibit one of the following symptoms because of the information mismatch:Choosing the Windows Start menu doesn’t produce any effect.Choosing Windows Action Center doesn’t produce any effect.Windows Search doesn’t open from the taskbar.

ResolutionNote: The following steps are applicable for BYOL WorkSpaces only.Rebuild the WorkSpace from an image created after May 2019. If you don't have an image built after May 2019, see Why isn’t the Start menu, Action Center, or Cortana Search responding after I rebuilt my Windows 10 WorkSpace?Install the most recent Windows Update on a WorkSpace based on the existing bundle.Create an image from the WorkSpace, and then update the bundle with the new image. For instructions, see Update a custom WorkSpaces bundle.Rebuild the WorkSpace.
Question: How do I download my Amazon RDS DB instance logs?

I want to download the log files for my Amazon Relational Database Service (Amazon RDS) DB instance, but I can't locate the log files to download. How can I find and download the log files for my DB instance?Short descriptionYou can view and download logs for an RDS DB instance Amazon RDS console. You can also view, watch, download, or query the logs using the AWS Command Line Interface (AWS CLI) or API actions. However, the log output defaults for MySQL and MariaDB are to a table instead of to a file. You can't directly download the log data, because that data is stored in the mysql.general_log table or the mysql.slow_log table.

ResolutionNote: If you receive errors when running AWS CLI commands, make sure that you’re using the most recent version of the AWS CLI.To be sure that you can access and download MySQL or MariaDB log files, first, set the log_output parameter to file. Then, enable logging. For DB-engine-specific information about logging, see the following resources:MariaDB database log filesMicrosoft SQL Server database log filesMySQL database log filesOracle database log filesPostgreSQL database log files

Related informationAccessing the MariaDB slow query and general logsMariaDB documentation for Binary log formatsMariaDB documentation for mysqlbinlog utility
Question: How do I resolve the "failed to initialize logging driver: failed to create CloudWatch log stream status code: 400" error when I run an AWS Batch job?

My AWS Batch job failed, and I received the following error message: "CannotStartContainerError: Error response from daemon: failed to initialize logging driver: failed to create CloudWatch log stream: ThrottlingException: Rate exceeded status code: 400." How can I resolve this error?Short descriptionThis error means that you reached your Amazon CloudWatch service quota for API requests. When you reach this quota, your CreateLogStream API call is throttled.You can receive this error when using any of the following AWS Cloud services to programmatically submit multiple jobs at the same time:AWS Command Line Interface (AWS CLI)AWS SDKsAWS LambdaAWS Step Functions

ResolutionConsider implementing one or more of the following solutions:Apply a retry strategy to your jobs using a job definition.Use retries and an exponential backoff algorithm with Jitter, and then resubmit your job.Avoid throttling by using AWS Batch array jobs to submit jobs with a single SubmitJob API call (up to 10,000 copies of a job).
Question: How can I assign a static IP address to my Amazon EC2 Windows instance?

I use an Amazon Elastic Compute Cloud (Amazon EC2) Windows instance, and a private IP address is automatically assigned to the instance. Can I assign a static IP address to my Amazon EC2 Windows instance?ResolutionStatic private IP addresses aren't required for Amazon EC2 Windows instances. However, you can use two private IP addresses for your Windows network adapter. To assign a static private IP address for an Amazon EC2 Windows instance, follow these steps:Note: The network interface IP address and Windows adapter IP addresses must match for a successful network connection.Open the Amazon EC2 console, and then choose Instances from the navigation pane.Select your instance. From the Networking tab, Expand Network interfaces, and then choose the Interface ID.Select the Network interface ID, Choose Actions, and then choose Manage IP Addresses. The primary private IPv4 IP address is already listed.Expand the network interface ID, and then choose Assign new IP address.Do one of the following:For Auto-assign, enter a new IP address, and then choose Save.-or-Don't enter a new IP address, choose Save, and then choose Confirm to auto assign the new IP address to the network interface.Important: Note the primary private IPv4 address and the new IP address for a later step.Connect to your Amazon EC2 Windows instance using Remote Desktop Protocol (RDP).Open a command prompt window as an administrator, type ipconfig/all, and then press the enter key. Note the IP address, Subnet mask, and Default gateway.Open Network and Sharing Center, and then choose Change adapter settings.Open the context menu for the network connection, and then choose Properties.Select Internet Protocol Version 4 (TCP/IPv4), and then choose Properties.Choose Use the following IP address.For IP address, enter the primary private IPv4 address.For Subnet mask, enter the network mask for the subnet.For Default gateway, enter the gateway for the subnet.Choose Advanced.For IP addresses, choose Add. Enter the new private IP address and subnet mask, and then choose Add.(Optional) Choose the DNS tab, enter a DNS server address, and then choose OK.Note: For more information about finding your VPC DNS server settings, see Amazon DNS server. For information about reserved addresses, see Subnet sizing.To verify that the new IP address is successfully added, open a command prompt window as an administrator and ping both private IP addresses. You can also ping both addresses from another instance in the same subnet.

Related informationConfigure a secondary private IPv4 address for your Windows instanceElastic network interfacesHow do I associate a static public IP address with my EC2 Windows or Linux instance?
Question: How can I use EFS CloudWatch metrics to monitor my file system?

I want to use Amazon CloudWatch to monitor my Amazon Elastic File System (Amazon EFS) metrics. How can I do this?Short descriptionAmazon EFS automatically sends metric data to CloudWatch in one-minute intervals. The data is recorded for a 15-month period so that you can get a better insight on your application's file system usage.You can monitor the various CloudWatch metrics for bench-marking, scaling, and monitoring purposes.

ResolutionTo calculate the average throughput, IOPS, or throughput percentage of your file system, create a metric math expression using the TotalIOByte metric. To create the metric math expression, do the following:Open the CloudWatch console.Select Metric, All metrics.Select EFS file system metrics.Select the metric TotalIOBytes and then select Graphed metrics.Choose Sum from the Statistics drop down menu.Select Add math, Start with empty expression.Add one of the following formulas in the expression e1 to calculate throughput or IOPS:Calculate throughput in MiB/second:Formula for calculating throughput: TotalIOBytes ÷ 1,048,576 (to convert to MiB) ÷ seconds in the period.Enter the following expression: (m1/1048576)/PERIOD(m1).The expression appears as e1=(m1/1048576)/PERIOD(m1).e1 is throughput in **MiB/**s, m1 is TotalIOBytes. The TotalIObytes is divided by 1048576 to convert it to MiB.Note: To calculate read, write, or metadata throughput specifically, replace the TotalIOByte in the preceding expression with DataReadIOBytes, DataWriteIOBytes, or MetadataIOBytes.Calculate IOPS (average operations per second):Formula for calculating IOPS: TotalIOBytes ÷ seconds in the period.Enter the following expression: m1/PERIOD(m1).The expression appears as e1=m1/PERIOD(m1).e1 is IOPS, m1 is TotalIOBytes.Note: To calculate read, write, or metadata IOPS specifically, replace TotalIOByte in the preceding expression with DataReadIOBytes, DataWriteIOBytes, or MetadataIOBytes.For more information, see  Using metric math with Amazon EFS.

Related informationCloudWatch metrics for Amazon EFS
Question: Why aren't my Amazon S3 event notifications working with a wildcard in the prefix or suffix of the object name filter?

I configured Amazon Simple Storage Service (Amazon S3) event notifications with a filter on the object key name. I included a wildcard (*) in the prefix or suffix of the key name filter. Why aren't event notifications working?ResolutionThe wildcard asterisk character (*) is a valid character that can be used in object key names. Amazon S3 literally interprets the asterisk as a prefix or suffix filter.You can't use the wildcard character to represent multiple characters for the prefix or suffix object key name filter. Instead, you must configure multiple event notifications to match the object key names.

Related informationCreating object key namesAmazon S3 Event NotificationsConfiguring event notifications using object key name filtering
Question: Can I export my public ACM certificates to other AWS Regions or AWS accounts?

I requested a public AWS Certificate Manager (ACM) certificate. Can I export the certificate to another AWS Region or AWS account?Short descriptionYou can't export an ACM certificate from one AWS Region to another or from one AWS account to another. This is because the default AWS Key Management Service (AWS KMS) key used to encrypt the private key of the certificate is unique for each AWS Region and AWS account. For more information, see ACM private key security.

ResolutionYou can create multiple ACM certificates with the same domain name across different AWS Regions and accounts. You can then use these certificates with services that run on AWS Certificate Manager.For more information, see Requesting a public certificate.Note: ACM certificates must be requested or imported in the same AWS Region as your load balancer. Amazon CloudFront distributions must request the certificate in the US East (N. Virginia) Region.

Related informationACM certificate characteristicsHow do I configure my CloudFront distribution to use an SSL/TLS certificate?How can I associate an ACM SSL/TLS certificate with a Classic, Application, or Network Load Balancer?Exporting a private certificate
Question: Why is there a replication delay on my Amazon DynamoDB global table version 2017.11.29?

I want to reduce the replication latency for my Amazon DynamoDB global tables.

ResolutionNote: There are two versions of DynamoDB global tables: version 2019.11.21 and version 2017.11.29. To find out which version you're using, see Determining the version of global tables you are using. It's a best practice to use version 2019.11.21. This version is more efficient and consumes less write capacity than version 2017.11.29. To upgrade, see Updating global tables to version 2019.11.21 (current).Here are some common causes of high replication latency for global table version 2017.11.29:DynamoDB publishes the ReplicationLatency and PendingReplicationCount metrics to Amazon CloudWatch for each replica in the global table. If either of these metrics is elevated for an extended period, then check if write requests are throttled in the global table Regions. Make sure that you have enough provisioned capacity to perform replicated writes to all global table Regions. To verify, use DynamoDB auto scaling or on-demand capacity mode. For more information, see Best practices and requirements for managing global tables.ReplicationLatency might vary for different source and destination pairs, depending on how geographically far apart the tables are from each other. For example, ReplicationLatency is typically lower for global tables in the Europe (Ireland) and Europe (London) Regions than for tables in the Europe (Ireland) and Asia Pacific (Sydney) Regions.ReplicationLatency and PendingReplicationCount might increase when an AWS Region becomes degraded. Use the AWS Service Health Dashboard to check for events in the Regions where you have replica tables. If there's an event, then you can temporarily redirect your application's read and write activity to a different Region.When you upgrade from version 2017.11.21 to version 2019.11.29, you might see an increase in ReplicationLatency. This is expected. For more information, see Updating global tables to version 2019.11.21 (current).Note: PendingReplicationCount is available only for 2017.11.29 global tables, and not 2019.11.29.

Related informationCreating a global table
Question: How do I create a VPN connection with my own PSK values and inside tunnel IP addresses?

I want to create a virtual private network (VPN) connection with my own pre-shared key (PSK) value and inside tunnel IP addresses. How can I do this?ResolutionBefore you begin, consider the following:You can modify tunnel options after you create a Site-to-Site VPN connection.You can't configure tunnel options for an AWS Classic VPN connection. For more information, see Migrating from AWS Classic VPN to AWS VPN.To create a VPN connection with your own PSK value and inside tunnel IP addresses, do the following steps:1.    Open the Amazon Virtual Private Cloud (Amazon VPC) console.2.    Choose Site-to-Site VPN connections from the navigation pane.3.    Choose Create VPN Connection.4.    Under Tunnel Options, populate the following with your custom PSK value and inside tunnel IP addresses:Note: Inside tunnel IPv4 CIDR refers to the range of inside (internal) IPv4 addresses for the VPN tunnel. You can specify a size /30 CIDR block from the 169.254.0.0/16 range. The CIDR block must be unique across all Site-to-Site VPN connections that use the same virtual private gateway. The CIDR block doesn't need to be unique across all connections on a transit gateway. However, CIDR blocks aren't unique can create a conflict on your customer gateway. Proceed carefully when re-using the same CIDR block on multiple Site-to-Site VPN connections on a transit gateway.The following CIDR blocks are reserved and cannot be used:169.254.0.0/30169.254.1.0/30169.254.2.0/30169.254.3.0/30169.254.4.0/30169.254.5.0/30169.254.169.252/30Note: Inside tunnel IPv6 CIDR refers to the range of inside (internal) IPv6 addresses for the VPN tunnel. You can specify a size /126 CIDR block from the local fd00::/8 range. The CIDR block must be unique across all Site-to-Site VPN connections that use the same transit gateway.Inside IP CIDR for Tunnel 1Inside IP CIDR for Tunnel 2Note: The PSK must be between 8 and 64 characters in length and cannot start with zero (0). Allowed characters are alphanumeric characters, periods (.), and underscores (_).Pre-Shared Key for Tunnel 1Pre-Shared Key for Tunnel 25.    Choose Create VPN Connection.

Related informationTunnel options for your Site-to-Site VPN connectionAWS Site-to-Site VPN adds configurability of security algorithms and timer settings for VPN tunnels
Question: How can I configure backtrack on my Amazon Aurora MySQL-Compatible DB cluster?

I have an Amazon Aurora MySQL-Compatible Edition DB cluster, and I want to backtrack my instance to a time that I specify.

Short descriptionYou can choose to turn on backtrack when you create your Amazon Aurora DB cluster. If you have an existing cluster and you want to turn on backtrack, first create a new cluster from a snapshot of your Amazon Aurora cluster. Then, turn on backtrack during the cluster creation process.There are some limitations when you use the backtrack feature:Backtracking is supported for select Aurora MySQL-Compatible versions. You can't use backtrack with Amazon Aurora PostgreSQL-Compatible Edition instances.Backtracking isn't available in these AWS Regions: Africa (Cape Town), China (Ningxia), Asia Pacific (Hong Kong), Europe (Milan), Europe (Stockholm), Middle Easy (Bahrain), and South America (São Paulo).You can't use backtrack with Amazon Aurora multi-master clusters.Backtracking isn't supported with binary log (binlog) replication. This means that cross-Region replication must be turned off before you can configure or use backtracking.The maximum limit for a backtrack window is 72 hours.Backtracking is applied to the cluster as a whole. So, you can't use backtracking for a single data update or for specific tables. You must update the entire cluster.

ResolutionFollow these steps to turn on backtrack in your Aurora MySQL-Compatible DB cluster.1.    Create an Aurora MySQL-Compatible cluster.2.    In the Backtrack section of your cluster configuration, select the check box to Enable Backtrack.3.    For Target Backtrack window, choose the number of hours that you want to configure for your Backtrack window. This determines how far back in time you can backtrack the cluster. Enter a number in hours up to 72 hours.You can also modify the backtrack window at a later date, or turn backtrack off entirely by modifying your cluster.If you created an Aurora cluster without turning on the backtrack feature, you must first restore a snapshot of the Aurora cluster. Then, use the steps in this article to turn on backtrack during the snapshot restore/cluster creation process.

Related informationAmazon Aurora backtrack - turn back time