Amazon Web Services Updated SOA-C02 Exam Questions and Answers by jeremiah

Objective:

Resolve the failure of the CloudFormation Auto Scaling group resource creation due to a missing wait condition signal.

cfn-signal:

The cfn-signal command is used in user data scripts to signal CloudFormation that the resource has been successfully created or configured.

This ensures the stack creation process continues as expected.

Steps to Implement:

At the end of the user data script in the EC2 launch template:

Add the command: cfn-signal --stack --resource --region

Replace , , and with appropriate values.

AWS References:

cfn-signal:Using cfn-signal to Signal Completion

Why Other Options Are Incorrect:

Option B: While port 443 is necessary for CloudFormation signaling, the main issue is the absence of cfn-signal.

Option C: Reducing DesiredCapacity may bypass the error but does not solve the root cause.

Option D: Associating a public IP may help connectivity but is unrelated to the wait condition.

AWS Secrets Manager allows you to store, manage, and automatically rotate database credentials. This service is designed to be used for such requirements efficiently.

Store Database Credentials in AWS Secrets Manager:

Open the AWS Secrets Manager console at AWS Secrets Manager Console.

Choose Store a new secret.

Select Credentials for RDS database and provide the database connection details and credentials.

Choose Next to configure the secret.

Configure Rotation:

Enable automatic rotation for the secret.

Set the rotation interval to 365 days.

Select or create a Lambda function that will be used to rotate the secret. AWS Secrets Manager provides a template for this function which can be customized if necessary.

Apply and Monitor:

Apply the changes and ensure that your application retrieves credentials from AWS Secrets Manager.

Monitor the rotation activity in Secrets Manager to ensure that the credentials are being rotated as expected.

AWS Secrets Manager

Rotating Your AWS Secrets Manager Secrets

To make an internal web application highly available, you should configure the Amazon EC2 Auto Scaling group to launch instances in multiple Availability Zones within the same AWS Region. This ensures that the application remains available even if one Availability Zone becomes unavailable.

Login to AWS Management Console:

Open the Amazon EC2 console at Amazon EC2 Console.

Update Auto Scaling Group:

In the navigation pane, choose Auto Scaling Groups.

Select the Auto Scaling group that you want to modify.

Choose Edit.

Add Multiple Availability Zones:

In the Availability Zones and subnets section, select at least one additional Availability Zone.

Ensure that the selected subnets belong to different Availability Zones.

Save Changes:

Save the configuration changes to update the Auto Scaling group.

Distributing Instances Across Multiple Availability Zones

Auto Scaling Groups

 Group EC2 Instances Using Resource Groups:

Resource groups help organize and manage AWS resources based on tags and other criteria.

Steps:

Go to the AWS Management Console.

Navigate to AWS Resource Groups.

Create resource groups for similar EC2 instances based on tags or other criteria.

AWS Resource Groups

 Create a Schedule in Patch Manager:

AWS Systems Manager Patch Manager automates the process of patching managed instances.

Steps:

Go to the AWS Management Console.

Navigate to Systems Manager and select Patch Manager.

Create a patch baseline if not already created.

Create a schedule for patching and specify the resource group as the target.