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

S3 Storage Lens and Lifecycle Policies:

Incomplete Multipart Upload Bytes Metric: This metric in S3 Storage Lens helps you identify the storage consumed by incomplete multipart uploads.

S3 Lifecycle Policies: Lifecycle policies allow you to automatically manage the lifecycle of objects, including deleting incomplete multipart uploads after a specified number of days.

Steps:

Go to the AWS Management Console.

Navigate to S3 and select the bucket.

Go to the "Metrics" tab and view the "Incomplete Multipart Upload Bytes" metric in the S3 Storage Lens dashboard.

To create a lifecycle policy:

Select the bucket.

Go to the "Management" tab.

Under "Lifecycle rules," click "Create lifecycle rule."

Define a rule name.

Choose "Multipart upload" and specify "Delete incomplete multipart uploads" after 7 days.

Save the rule.

AWS S3 Storage Lens

AWS S3 Lifecycle Policies

To ensure high availability and disaster recovery for the RDS for MySQL database, follow these steps:

Create a Cross-Region Read Replica:

In the RDS console, create a cross-Region read replica of the primary database instance. This read replica will provide high availability and the lowest RTO and RPO in case of a disaster.

To manage user accounts and permissions across multiple AWS accounts and integrate with an on-premises Active Directory, using AD Connector is the most operationally efficient solution. AD Connector serves as a directory gateway with which you can redirect directory requests to your on-premises Microsoft Active Directory without storing any directory data in the cloud. This setup allows IAM Identity Center to use the existing corporate credentials, ensuring centralized management and seamless user access control. Option C perfectly meets these requirements by leveraging existing infrastructure with minimal changes. AWS documentation on AD Connector offers guidance AWS Directory Service AD Connector.

To securely connect to Amazon S3 buckets from Amazon EC2 instances over a private connection without incurring additional costs, you can use a gateway VPC endpoint for S3. This method allows you to create a single gateway VPC endpoint for all S3 buckets in the same region, ensuring secure, private communication.

Create a Gateway VPC Endpoint:

Navigate to the VPC console.

In the navigation pane, choose "Endpoints" and then click "Create Endpoint".

Select "AWS services" and then choose "com.amazonaws..s3" from the service name dropdown.

Select the VPC in which to create the endpoint and the appropriate route tables.

Click "Create endpoint".

Update the Route Tables:

The gateway VPC endpoint will automatically update the selected route tables to include routes that direct S3 traffic through the endpoint.

Ensure that the route tables associated with your subnets include routes for the S3 service pointing to the gateway VPC endpoint.

Verify the Configuration:

Ensure that instances in the VPC can access the S3 buckets using private IP addresses.

Check the routing configuration to confirm that traffic to S3 is routed through the gateway VPC endpoint.

Gateway VPC Endpoints for Amazon S3

Creating a Gateway Endpoint