Replicated Secrets in Multiple Regions

Correct Answers: B and E.

AWS Secrets Manager can be configured to replicate secrets across multiple regions.

With this feature, multi-region applications like Amazon RDS can retrieve secrets locally within the region instead of retrieving secrets across the regions.

Following are features when AWS Secrets Manager is configured to replicate secrets in multiple regions.

Replicated Secrets will have a common name across all regions.

Secrets Manager replicates all encrypted secrets and metadata.

Option A is incorrect as Secrets Manager not just encrypts secrets and resource policies but also replicates all the metadata such as tags, resource policies, rotation policies across the specified region.

Option C is incorrect as Secrets Manager not just encrypts secrets and resource policies but also replicates all the metadata such as tags, resource policies, rotation policies across the specified region.

Option D is incorrect as secrets have a common name across all regions and not a different name in each region.

For more information on multi-region replication with AWS Secrets Manager, refer to the following URL,

https://aws.amazon.com/blogs/security/how-to-replicate-secrets-aws-secrets-manager-multiple-regions/

Sure, I'd be happy to provide a detailed explanation of AWS Secret Manager replication in multiple regions.

First, let's define what AWS Secrets Manager is. AWS Secrets Manager is a service that helps you protect access to your applications, services, and IT resources. It enables you to easily rotate, manage, and retrieve database credentials, API keys, and other secrets throughout their lifecycle. AWS Secrets Manager eliminates the need to hard-code credentials in your code or configuration files, and helps you comply with security and compliance standards.

When you create a secret in AWS Secrets Manager, the secret is encrypted and stored securely in AWS infrastructure. AWS Secrets Manager also provides automatic rotation of secrets, which helps you to manage the lifecycle of your secrets.

Now, let's discuss how AWS Secrets Manager replication works in multiple regions.

When you create a secret in AWS Secrets Manager, the secret is stored in the region where you created it. If you want to use the same secret in another region, you can replicate the secret to that region. This is useful for disaster recovery scenarios or for ensuring low-latency access to secrets in different regions.

When you replicate a secret to another region, AWS Secrets Manager creates a copy of the encrypted secret in the destination region. The copy is encrypted with a different AWS KMS key, and the metadata associated with the secret, such as its name, description, and tags, are also copied. The resource policies attached to the secret are also replicated.

However, it's important to note that replicated secrets will have different names in each region. This is because the name of the secret includes the region where it was created. For example, if you create a secret called "mysecret" in the us-west-2 region and replicate it to the us-east-1 region, the replicated secret will be named "mysecret" in the us-east-1 region, but it will have a different Amazon Resource Name (ARN) than the original secret.

In summary, the correct statements about AWS Secret Manager replication in multiple regions are:

A. Secrets Manager replicates all encrypted secrets and resource policies. C. Secrets Manager replicates only encrypted secrets.

And the incorrect statements are:

B. Replicated secrets will have common names across all regions. D. Replicated secrets will have different names in each region. E. Secrets Manager replicates all encrypted secrets and metadata.