SOA-C02 - AWS Certified SysOps Administrator - Associate (SOA-C02)

Here are the steps to update an existing AWS CloudFormation stack:

• Log in to the AWS Management Console and navigate to the CloudFormation service in the us-east-2 Region.
• Find the existing stack named 1700182 and click on it.
• Click on the "Update" button.
• Choose "Replace current template" and upload the updated CloudFormation template from the Amazon S3 bucket named "cloudformation-bucket"
• In the "Parameter" section, update the EC2 instance type to us-east-t2.nano and add the IP address range 192.168.100.0/30 for SSH access.
• Replace the instance profile IAM role with IamRoleB.
• In the "Capabilities" section, check the checkbox for "IAM Resources"
• Choose the role CFServiceR01e and click on "Update Stack"
• Wait for the stack to be updated.
• Once the update is complete, navigate to the stack and click on the "Stack options" button, and select "Prevent updates to prevent accidental deletion"
• To get the value of the Prodlnstanceld , navigate to the "Outputs" tab in the CloudFormation stack and find the key "Prodlnstanceld". The value corresponding to it is the value that you need to enter in the text box below.

Note:

• You can use AWS CloudFormation to update an existing stack.
• You can use the AWS CloudFormation service role to deploy updates.
• You can refer to the AWS CloudFormation documentation for more information on how to update and manage stacks: https://aws.amazon.com/cloudformation/

Here are the steps to configure Amazon EventBridge to meet the above requirements:

• Log in to the AWS Management Console by using the AWS Management Console shortcut from the VM desktop. Make sure that you are logged in to the desired AWS account.
• Go to the EventBridge service in the us-east-2 Region.
• In the EventBridge service, navigate to the "Event buses" page.
• Click on the "Create event bus" button.
• Give a name to your event bus, and select "default" as the event source type.
• Navigate to "Rules" page and create a new rule named "RunFunction"
• In the "Event pattern" section, select "Schedule" as the event source and set the schedule to run every 15 minutes.
• In the "Actions" section, select "Send to Lambda" and choose the existing AWS Lambda function named "LogEventFunction"
• Create another rule named "SpotWarning"
• In the "Event pattern" section, select "EC2" as the event source, and filter the events on "EC2 Spot Instance interruption"
• In the "Actions" section, select "Send to SNS topic" and create a new standard Amazon SNS topic named "TopicEvents"
• In the "Input Transformer" section, set the Input Path to {“instance” : “$.detail.instance-id”} and Input template to “The EC2 Spot Instance has been interrupted on account.
• Now all Amazon EC2 events in the default event bus will be replayable for past 90 days.

Note:

• You can use the AWS Management Console, AWS CLI, or SDKs to create and manage EventBridge resources.
• You can use CloudTrail event history to replay events from the past 90 days.
• You can refer to the AWS EventBridge documentation for more information on how to configure and use the service: https://aws.amazon.com/eventbridge/

Here are the steps to configure an Amazon S3 bucket to serve a static error page in the event of a failure at the primary site:

• Log in to the AWS Management Console and navigate to the S3 service in the us-east-2 Region.
• Find the existing S3 bucket named lab-751906329398-26023898.com and click on it.
• In the "Properties" tab, click on "Static website hosting" and select "Use this bucket to host a website".
• In "Index Document" field, enter the name of the object that you want to use as the index document, in this case, "index.html"
• In the "Permissions" tab, click on "Block Public Access", and make sure that "Block all public access" is turned OFF.
• Click on "Bucket Policy" and add the following policy to allow public read access:

{

"Version": "2012-10-17",

"Statement": [

{

"Sid": "PublicReadGetObject",

"Effect": "Allow",

"Principal": "*",

"Action": "s3:GetObject",

"Resource": "arn:aws:s3:::lab-751906329398-26023898.com/*"

}

]

}

• Now navigate to the Amazon Route 53 service, and find the existing hosted zone named lab-751906329398-26023898.com.
• Click on the "A record" and update the routing policy to "Primary - Failover" and add the existing ALB as the primary record.
• Click on "Create Record" button and create a new secondary failover alias record for the domain lab-751906329398-26023898.com that routes traffic to the existing S3 bucket.
• Now, when the primary site (ALB) goes down, traffic will be automatically routed to the S3 bucket serving the static error page.

Note:

• You can use CloudWatch to monitor the health of your ALB.
• You can use Amazon S3 to host a static website.
• You can use Amazon Route 53 for routing traffic to different resources based on health checks.
• You can refer to the AWS documentation for more information on how to configure and use these services:

Graphical user interface, text, application Description automatically generated

Graphical user interface, application, Teams Description automatically generated

Graphical user interface, text, application Description automatically generated

Graphical user interface, text, application, email Description automatically generated

Graphical user interface, text, application Description automatically generated