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

This configuration approach will meet the requirement of encrypting all data at rest and rotating the encryption keys once each year. By creating a new AWS KMS customer managed key and enabling automatic key rotation, the encryption keys will be rotated automatically every year. By enabling RDS encryption on the database at creation time using the KMS key, all data stored in the RDS for MySQL Multi-AZ database will be encrypted at rest. This approach provide more control over key management and rotation and provide additional security benefits.

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.

References:

Amazon EC2 Auto Scaling

Target Tracking Scaling Policies

Increasing the size of the 1 GiB EBS volumes will increase the IOPS capacity of the volumes, which will improve the I/O performance of the EBS volumes. This option does not require any changes to the instance types or EBS volume types, so it can be done quickly without the need for lengthy acceptance tests to validate that the company's applications will function properly.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/requesting-ebs-volume-modifications.html

To resolve the issue of the EC2 instance in a private subnet not being able to connect to external websites via HTTPS (port 443), it is necessary to adjust the security group settings:

Outbound Security Group Rules: Verify that the security group associated with the EC2 instance allows outbound traffic on port 443 to any destination (0.0.0.0/0). This rule is crucial because it enables the instance to initiate HTTPS connections to external websites.

Network ACLs: While the primary concern here is the security group, ensure also that the Network Access Control List (ACL) associated with the subnet permits outbound HTTPS traffic. However, the ACLs by default allow all outbound traffic unless specifically restricted.

Internet Connectivity: Since the instance is in a private subnet, ensure that it has a route to the internet through a NAT Gateway or NAT Instance located in a public subnet. Without this, the instance won't be able to reach external networks even if the security groups and ACLs are correctly configured.

By ensuring that the security group permits outbound HTTPS traffic, you address the most common configuration oversight that would prevent such connectivity.