Master AWS Certifications with Confidence

Enabling multi-factor authentication (MFA) for the root user

Using AWS CloudFormation to deploy infrastructure

Configuring AWS Trusted Advisor to monitor security best practices

Sharing IAM credentials across multiple users

Disabling Amazon GuardDuty to reduce costs

Amazon S3 access control lists (ACLs)

AWS Certificate Manager (ACM)

Network Access Analyzer

AWS Identity and Access Management Access Analyzer

Create a custom domain name in API Gateway as edge-optimized. Import the certificate into ACM in ca-central-1. Attach the certificate to the domain. Configure Route 53 with an A record pointing to the API Gateway URL.

Create Route 53 records pointing to the API Gateway's execute-api URL. Import the certificate into ACM in us-east-1 and attach it to the API's methods.

Import the certificate into ACM in us-east-1. Create a custom domain name in API Gateway as edge-optimized, attaching the certificate. Create a Route 53 alias record pointing to the API Gateway's domain.

Create a Regional API Gateway endpoint, import the certificate into the same region, attach it to the APIs, and configure Route 53 with a CNAME to the API's URL.

Use a data stream in Amazon Kinesis Data Streams in on-demand mode to capture the logs. Use AWS Lambda to process the data in real time.

Use Amazon Kinesis Data Firehose to capture the logs. Use AWS Glue to process the data in real time.

Use Amazon Kinesis Video Streams to capture the logs. Use AWS Glue to process the data in real time.

Use Amazon Managed Service for Apache Flink to capture the logs. Use AWS Lambda to process the data in real time.

Migrate to DynamoDB Accelerator (DAX) for caching. Update the application to use DAX. Create an Auto Scaling group for the EC2 instances. Deploy an Application Load Balancer (ALB) targeting the Auto Scaling group. Update the Route 53 record to use a simple routing policy pointing to the ALB's DNS. Configure scheduled scaling for EC2 instances before peak seasons.

Replace the Memcached cluster with Amazon ElastiCache for Redis. Update the application to use ElastiCache. Create an Auto Scaling group for the EC2 instances. Set up an Amazon CloudFront distribution with the Auto Scaling group as the origin. Update Route 53 to route traffic to the CloudFront DNS. Manually scale EC2 instances before peak seasons.

Replace the Memcached cluster with Amazon ElastiCache for Memcached. Update the application to use ElastiCache. Create an Auto Scaling group for the EC2 instances. Deploy an Application Load Balancer (ALB) targeting the Auto Scaling group. Update the Route 53 record to use a simple routing policy pointing to the ALB's DNS. Configure scheduled scaling for EC2 instances before peak seasons.

Migrate to DynamoDB Accelerator (DAX) for caching. Update the application to use DAX. Create an Auto Scaling group for the EC2 instances. Set up an Amazon CloudFront distribution with the Auto Scaling group as the origin. Update Route 53 to route traffic to the CloudFront DNS. Manually scale EC2 instances before peak seasons.

Create an Amazon SNS topic with an email subscription targeting the team's distribution list.

Create a task state named 'Notify' that publishes a message to the Amazon SNS topic.

Add a Catch field to every Task, Map, and Parallel state with \"ErrorEquals\": [\"States.ALL\"] and \"Next\": \"Notify\".

Verify the email address in Amazon Simple Email Service (Amazon SES).

Implement a Dead-Letter Queue using Amazon SQS to capture failed executions and trigger an SNS notification.

Add a Retry field to each state with \"ErrorEquals\": [\"States.Runtime\"].

Use a custom query parameter to specify the API version and configure the Lambda function to process requests accordingly.

Implement an API Gateway canary release deployment to split traffic between the two versions based on a percentage.

Apply an API Gateway resource policy that routes incoming requests to the appropriate version based on the client's IP address.

Deploy each API version as a separate stage with distinct endpoints and utilize stage variables to manage environment-specific configurations.

Add an Export declaration to the Outputs section of the original template and use Fn::ImportValue in other templates.

Add Exported: true to the MyDBInstance resource in the original template and use ImportResource in other templates.

Create a custom AWS CloudFormation resource that retrieves the endpoint from the MyDBInstance resource of the first stack.

Use Fn::Merge to combine the existing template with other templates and reference the DBEndpoint output directly.