AWS Certified Associate SOA-C02 Passing Score

Reuse templates to replicate stacks in multiple environments After you have your stacks and resources set up, you can reuse your templates to replicate your infrastructure in multiple environments. For example, you can create environments for development, testing, and production so that you can test changes before implementing them into production. To make templates reusable, use the parameters, mappings, and conditions sections so that you can customize your stacks when you create them. For example, for your development environments, you can specify a lower-cost instance type compared to your production environment, but all other configurations and settings remain the same. SCloudFormation/latest/UserGuide/best-practices.html#reuse

To prevent accounts from leaving an AWS Organization, an SCP that denies the LeaveOrganization action should be applied to the root organizational unit (OU).

Service Control Policy (SCP): By denying LeaveOrganization, member accounts are restricted from leaving the organization.

Root OU Application: Applying this policy at the root level ensures that no account in the organization can bypass it.

The RemoveAccountFromOrganization action pertains to removing an account by the organization’s management account rather than preventing member accounts from leaving. AWS Config’s account-part-of-organizations rule does not enforce this restriction but only monitors it.

Understand the Problem:

A user attempts to deploy a CloudFormation template to create an S3 bucket but the stack creation fails.

The user authenticates using Active Directory credentials.

Analyze the Requirements:

Identify permissions required for successful CloudFormation stack creation.

Evaluate the Options:

Option A: The user's IAM policy does not allow the cloudformation:CreateStack action.

Without this permission, the user cannot create CloudFormation stacks.

Option B: The user's IAM policy does not allow the cloudformation:CreateStackSet action.

StackSet is used for managing stacks across multiple accounts and regions, not relevant for a single stack creation.

Option C: The user's IAM policy does not allow the s3:CreateBucket action.

This permission is required to create an S3 bucket as part of the stack.

Option D: The user's IAM policy explicitly denies the s3:ListBucket action.

This permission is not required for bucket creation but for listing existing buckets.

Option E: The user's IAM policy explicitly denies the s3:PutObject action.

This permission is required to put objects in a bucket, not to create the bucket.

Select the Best Solution:

Option A and C: The user must have permissions for cloudformation:CreateStack and s3:CreateBucket to successfully create the stack and the S3 bucket.

References:

AWS CloudFormation Permissions

IAM Policies and Permissions

Ensuring the user has the required permissions for cloudformation:CreateStack and s3:CreateBucket is crucial for successful stack creation.

To ensure high availability and that instances are placed on distinct underlying hardware, a spread placement group should be used. Spread placement groups place instances on distinct hardware, reducing the risk of simultaneous failures.

Create Spread Placement Group:

Open the EC2 console at Amazon EC2 Console.

Navigate to Placement Groups in the sidebar.

Click Create placement group and select Spread for the strategy.

Launch Instances:

When launching new instances, select the placement group you created.

Ensure the instances are in the same AWS Region but spread across distinct hardware.

Verify Placement:

After launching, verify that the instances are in the spread placement group by checking the instance details in the console.

References:

Placement Groups

Creating a Spread Placement Group