AWS Certified Associate SOA-C02 Passing Score

If the MFA device for the root user is lost, you can regain access to the AWS account by using email and phone verification. AWS Support provides a process to recover root account access.

Recover Root Account Access:

Go to the AWS sign-in page and choose Root user.

Enter the root user email address.

On the MFA prompt page, choose Troubleshoot MFA.

Follow the prompts for email and phone verification to verify your identity.

Set Up a New MFA Device:

Once you regain access, navigate to the IAM console at IAM Console.

Go to the Users section and select the root user.

Set up a new MFA device.

Change the Root User Password:

It is recommended to change the root user password after recovering access for security reasons.

Enabling and Managing Virtual MFA Devices (AWS Management Console)

Troubleshooting Multi-Factor Authentication

Applying SCPs to an Organizational Unit:

Service Control Policies (SCPs) allow you to manage permissions for multiple AWS accounts within an organization.

Steps:

Go to the AWS Management Console.

Navigate to AWS Organizations.

Create an Organizational Unit (OU) if not already created.

Move the target accounts into the OU.

Create an SCP that denies the use of the specific EC2 instance family.

Attach the SCP to the OU.

This approach ensures that the policy is applied consistently across all accounts in the OU.

AWS Organizations SCPs

To view the cost details of each project in an AWS account using Cost Explorer, you need to activate cost allocation tags and tag the resources with a project identifier.

Activate Cost Allocation Tags:

Navigate to the AWS Billing and Cost Management console.

In the navigation pane, choose "Cost allocation tags".

Select the tags you want to activate (e.g., "Project") and click "Activate".

Tag Resources with Project Identifier:

Go to the AWS Management Console for each service where resources are deployed (e.g., EC2, S3, RDS).

For each resource, add a tag with the key "Project" and a value that identifies the project (e.g., "ProjectA").

Ensure that all relevant resources are tagged appropriately.

View Cost Allocation in Cost Explorer:

Navigate to the Cost Explorer console.

Use the "Group by" option to group costs by the "Project" tag.

Review the cost details for each project based on the tags applied to the resources.

Using Cost Allocation Tags

Analyzing Your Costs with Cost Explorer

Scaling Policies in Auto Scaling:

When multiple scaling policies trigger at the same time, each policy is executed independently.

If both policies are set to add 5 instances when CPU utilization reaches 80%, they will both be executed when the threshold is met.

Therefore, the total number of instances added will be the sum of the instances specified in both policies.

In this case, 5 instances from one policy and 5 instances from the other policy will result in a total of 10 instances being added.

Steps to Configure and Verify Scaling Policies:

Go to the AWS Management Console.

Navigate to EC2 and select "Auto Scaling Groups."

Select your Auto Scaling group and review the scaling policies.

Ensure that both scaling policies are configured to trigger at 80% CPU utilization.

Monitor the Auto Scaling group's activity to verify the addition of instances when the CPU utilization threshold is reached.

Scaling Policies for Amazon EC2 Auto Scaling