Amazon Web Services SOA-C02 Exam With Confidence Using Practice Dumps

Step-by-Step Explanation:

Understand the Problem:

Share an AMI with other AWS accounts while ensuring it is encrypted with AWS KMS keys and accessible only to authorized accounts.

Analyze the Requirements:

Encrypt the AMI with a customer-managed key (CMK).

Share the AMI securely with specific AWS accounts.

Evaluate the Options:

Option A: Create a CMK and modify the key policy but do not create a copy of the AMI.

This does not re-encrypt the AMI with the CMK.

Option B: Create a CMK, modify the key policy, create a copy of the AMI, and specify the CMK.

This ensures the AMI is encrypted with the CMK and shared securely.

Option C: Create a CMK, modify the key policy, create a copy of the AMI, and make it public.

Making the AMI public does not meet the requirement of sharing with specific accounts only.

Option D: Modify the key policy of the AWS managed key and share the AMI.

AWS managed keys cannot have their key policies modified to add permissions for other accounts.

Select the Best Solution:

Option B: Creating a CMK, modifying the key policy, creating a copy of the AMI with the CMK, and specifying the permissions ensures the AMI is securely shared with specific AWS accounts.

Copying an AMI

Creating and Managing Keys

Sharing AMIs

This solution ensures the AMI is encrypted with a customer-managed key and shared securely with the specified AWS accounts.

To resolve DNS names for on-premises resources from EC2 instances in a VPC, you use Amazon Route 53 Resolver outbound endpoints to forward DNS queries to on-premises DNS servers.

From the Route 53 Resolver documentation:

Resolver outbound endpoints allow DNS queries from resources in your VPC to be forwarded to DNS servers in your on-premises network over Direct Connect or VPN.

To host a static website using Amazon S3 for both a domain and its subdomain, you need to create two separate buckets and configure one bucket to redirect to the other.

Steps:

Create the Main Domain Bucket:

Open the Amazon S3 console.

Create a bucket named example.com.

Enable static website hosting for the bucket and configure the index document (e.g., index.html).

Create the Subdomain Bucket:

Create another bucket named

In the bucket properties, enable static website hosting.

Set the website hosting configuration to redirect all requests to example.com.

Update DNS Configuration:

Open the Amazon Route 53 console.

Create an A record for example.com and pointing to the S3 bucket.