SOA-C02 Exam Dumps : AWS Certified SysOps Administrator - Associate (SOA-C02)

Amazon EFS supports two forms of encryption for file systems, encryption of data in transit and encryption at rest. You can enable encryption of data at rest when creating an Amazon EFS file system. You can enable encryption of data in transit when you mount the file system.

To enable AWS Config in all accounts and all regions within an AWS Organization, the most operationally efficient method is to use AWS CloudFormation StackSets. This allows you to deploy CloudFormation stacks across multiple AWS accounts and regions from a single CloudFormation template.

Create CloudFormation Template:

The template should include the necessary resources to enable AWS Config, such as the AWS::Config::ConfigurationRecorder, AWS::Config::DeliveryChannel, and AWS::Config::ConfigurationAggregator resources.

Create StackSet:

Open the AWS CloudFormation console at AWS CloudFormation Console.

Choose Create StackSet and upload your CloudFormation template.

Configure StackSet:

Specify the AWS accounts and regions where you want to deploy the stacks.

Set the deployment options, including the execution role and administrator role.

Deploy Stack Instances:

Deploy the stack instances to all specified accounts and regions. This will automatically enable AWS Config in each account and region.

AWS CloudFormation StackSets

Managing AWS Config Across Multiple Accounts

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.