Amazon SOA-C02 Exam Dumps

To configure replication of a DynamoDB table to another AWS Region for disaster recovery, you should use DynamoDB Global Tables. Global Tables use DynamoDB Streams to replicate changes across multiple regions.

Enable DynamoDB Streams:

Navigate to the DynamoDB console.

Select your table and enable DynamoDB Streams.

Add a Global Table Region:

With Streams enabled, go to the Global Tables tab.

Add a new region to the table, specifying the region where you want to replicate the data.

Automatic Replication:

DynamoDB will handle the replication of data across regions automatically, ensuring data consistency and high availability.

DynamoDB Global Tables

Enabling DynamoDB Streams

AWS Budgets can be used to create a Savings Plans budget and track the daily utilization of the company's Savings Plans. By creating a budget, it will trigger an action when the utilization drops below 90%, which in this case will be to send an email notification via an Amazon SNS topic. This will ensure that the company is notified when their Savings Plans utilization drops below 90%, allowing them to take action if necessary.

[1]https://docs.aws.amazon.com/savingsplans/latest/userguide/sp-usingBudgets.html

AWS Compute Optimizer provides recommendations for optimizing the performance and cost of your AWS resources, including Lambda functions.

Steps:

Enable AWS Compute Optimizer:

Open the AWS Compute Optimizer console.

Choose 'Get started'.

Enable Compute Optimizer for your account.

View Lambda Function Recommendations:

After enabling Compute Optimizer, allow some time for data collection and analysis.

Navigate to the 'Lambda Function Recommendations' section in the Compute Optimizer console.

Review the recommendations for your Lambda functions, which may include adjustments to memory size or other configurations to improve performance and reduce costs.

Export Recommendations:

In the Compute Optimizer console, you can export the recommendations to a CSV file for further analysis and action.

AWS Compute Optimizer

Optimizing Lambda Function Configurations

Auto Scaling groups automatically adjust the number of EC2 instances to handle the load on your application. A target tracking scaling policy adjusts the capacity of the Auto Scaling group based on a target metric, such as CPU utilization or application latency.

Create an Auto Scaling Group:

Navigate to the EC2 console and select 'Auto Scaling Groups'.

Create a new Auto Scaling group and specify the launch template or configuration for your EC2 instances.

Configure Target Tracking Scaling Policy:

In the Auto Scaling group settings, add a scaling policy.

Choose 'Target Tracking' and select a predefined metric such as 'Average CPU Utilization'.

Set the target value (e.g., 50% CPU utilization).

Attach ALB to Auto Scaling Group:

In the 'Load Balancing' section of the Auto Scaling group settings, attach your existing ALB.

This ensures that new instances are automatically registered with the ALB.

Review and Create:

Review the Auto Scaling group settings and create the group.

Amazon EC2 Auto Scaling

Target Tracking Scaling Policies

To allow AWS Systems Manager Patch Manager to access your EC2 instances, you need to attach an IAM instance profile with the necessary permissions to the instances.

Create IAM Role for Systems Manager:

Open the IAM console at IAM Console.

Create a new role and choose EC2 as the trusted entity.

Attach the AmazonEC2RoleforSSM managed policy to the role.

Attach IAM Role to Instances:

Open the Amazon EC2 console at Amazon EC2 Console.

Select the instances that you want to manage with Systems Manager.

Choose Actions, then Instance Settings, and select Attach/Replace IAM Role.

Attach the IAM role you created.

This setup ensures that Systems Manager has the necessary permissions to manage the instances.

Setting Up AWS Systems Manager

Create an IAM Instance Profile for Systems Manager