Master AWS Certifications with Confidence

VPC endpoints

Application Load Balancer

NAT gateway

Internet gateway

AWS Firewall Manager

Amazon GuardDuty

Amazon Detective

AWS WAF

Create an IAM role that grants access to the DynamoDB table. Attach the role to the EC2 instances.

Create an IAM policy that grants access to the DynamoDB table. Attach the policy to the EC2 instances.

Create an IAM group that grants access to the DynamoDB table. Attach the group to the EC2 instances.

Create an IAM user that grants access to the DynamoDB table. Attach the user account to the EC2 instances.

Replace the ALB with a Network Load Balancer. Continue hosting the NoSQL database on EC2 instances with its existing replication setup.

Configure the Auto Scaling group to distribute EC2 instances across three Availability Zones. Retain the embedded NoSQL database and manage its replication manually on the EC2 instances.

Replace the ALB with a Gateway Load Balancer. Migrate the embedded NoSQL database to Amazon DynamoDB using AWS DMS.

Update the Auto Scaling group to span three Availability Zones. Migrate the embedded NoSQL database to Amazon DynamoDB using AWS Database Migration Service (AWS DMS).

Develop a Lambda function to collect performance metrics for each Lambda function from Amazon CloudWatch Metrics over a 2-week period. Transform the data into a CSV format and save it to S3. Use an Amazon EventBridge rule to trigger the Lambda function every 2 weeks.

Enable AWS Compute Optimizer. Create a Lambda function that invokes the GetLambdaFunctionRecommendations API to retrieve optimization data. Format the results into a CSV file and store it in S3. Schedule the function using an Amazon EventBridge rule every 2 weeks.

Activate AWS Compute Optimizer. Configure a recurring export job directly from the Compute Optimizer console to generate a CSV report every 2 weeks and save it to the S3 bucket.

Upgrade to the AWS Enterprise Support plan. Use AWS Trusted Advisor to export cost optimization checks for Lambda functions into a CSV file. Schedule the export job via the Trusted Advisor console to run every 2 weeks and store the output in S3.

Create a transit gateway in ap-northeast-1. Attach the VPCs in us-west-2 and the two VPCs in ap-northeast-1 to the transit gateway. Configure route tables to direct traffic through the transit gateway.

Deploy a transit gateway in each Region. Attach the relevant VPCs to their regional transit gateway. Establish a peering connection between the transit gateways and update route tables to route traffic through the gateways.

Create a full mesh of VPC peering connections between all VPCs in both Regions. Update route tables to route traffic through the peering connections.

Create separate VPC peering connections from each of the three VPCs in us-west-2 to both VPCs in ap-northeast-1. Update route tables in all connected VPCs to route traffic through the peering connections.

A lazy-loading cache

A write-behind cache

A read-through cache

A write-through cache

Store the API key directly in the buildspec.yml file as a plaintext variable. Use an AWS Step Function to trigger rotation monthly.

Store the API key in AWS Systems Manager Parameter Store as a SecureString and reference it via environment variables. Enable rotation using a custom Lambda function.

Store the API key in AWS Secrets Manager and reference it via environment variables. Configure Secrets Manager to rotate the key automatically every 30 days.

Encrypt the API key using AWS KMS and store it in an environment variable. Set up an Amazon CloudWatch Events rule to handle rotation.