Master AWS Certifications with Confidence

Amazon CloudFront

Elastic Load Balancing

Amazon S3

Amazon Elastic Transcoder

Spot Instances

On-Demand Instances

Savings Plans

Dedicated Hosts

Deploy an interface VPC endpoint for SQS in the private subnets. Attach a security group to the endpoint that permits inbound traffic from the EC2 instances' security group.

Create an interface VPC endpoint for SQS in the public subnets. Apply a VPC endpoint policy that grants access to the EC2 instances' private IP addresses.

Set up a gateway VPC endpoint for SQS and associate it with the private subnets. Configure the EC2 instances' security group to allow outbound traffic to the SQS endpoint.

Use a NAT gateway in the public subnets and configure the EC2 instances to route SQS traffic through it. Attach an IAM role with SQS permissions to the instances.

Resize the EC2 instance to a larger instance type. Set up an Auto Scaling group with min/max size of 1. Create an RDS read replica and redirect read requests to it while keeping write traffic on the primary instance.

Resize the EC2 instance to a larger instance type. Configure an Auto Scaling group with min/max size of 1. Add an RDS read replica and redirect all read/write traffic to the replica.

Configure an Auto Scaling group with min size 1 and max size 3. Resize the RDS instance to a larger instance type and enable Multi-AZ deployment.

Resize both the EC2 and RDS instances to larger instance types. Configure an Auto Scaling group with min/max size of 1.

Migrate the Oracle databases to Amazon Aurora PostgreSQL using Oracle Data Pump utilities (expdp/impdp) for backup and restore.

Transfer data to Amazon S3 using an AWS Snowball Edge Storage Optimized device. Configure Amazon Aurora PostgreSQL and use S3 integration with PostgreSQL's COPY command to load data.

Convert the database schema using the AWS Schema Conversion Tool to Amazon Aurora PostgreSQL. Migrate the data using AWS Database Migration Service (AWS DMS) from on-premises Oracle to Aurora PostgreSQL.

Migrate data over the network using AWS DataSync from on-premises storage to Amazon S3. Set up Amazon Aurora PostgreSQL and load data using PostgreSQL's COPY command with S3 integration.

Modify the RDS instance to a Multi-AZ deployment in us-east-1.

Migrate the database to an Amazon Aurora global database with the primary in us-east-1 and the secondary in us-west-2.

Create a cross-Region read replica of the RDS MySQL instance in us-west-2.

Deploy a standby MySQL database on an Amazon EC2 instance in us-west-2.

Retrieve the AWS CloudTrail events for the resource secure-data where the event name is DeleteBucket. Inspect each event.

Retrieve the Amazon CloudWatch log events from the most recent log stream within the S3/secure-data log group. Inspect the log events.

Retrieve the AWS X-Ray trace summaries. Filter by services with the name secure-data. Inspect the ErrorRootCauses values within each summary.

Retrieve the AWS Config resource inventory. Filter the inventory by resources with a type of AWS::S3::Bucket. Inspect the deletion details.

Create a release branch from the commit intended for version 2.0. Apply fixes to the release branch. Continue developing new features on the main branch, merging them into main. After deployment, merge the release branch into main.

Create a Git tag on the commit for version 2.0. Continue developing new features on main, merging into main. Apply fixes to the main branch. Update the Git tag to the latest main commit.

Create a release branch from the version 2.0 commit. Apply fixes to the release branch. Continue developing on main, merge features into main. Rebase main onto the release branch after deployment.

Create a Git tag on the version 2.0 commit. Continue developing on main, merge features into main. Apply fixes directly to the Git tag.