Master AWS Certifications with Confidence

When an application hosted in an on-premises data center requires temporary access to AWS services

When the company needs to provide AWS access via access keys for a third-party application that does not support role assumption

When granting permissions to an AWS Lambda function to interact with Amazon S3

When enabling cross-account access for users from another AWS account

When users are authenticated via AWS Single Sign-On (SSO) and require federated access

AWS Config

Amazon Macie

AWS Certificate Manager

AWS CloudTrail

Use AWS CLI's s3 cp command with the --ssl flag to transfer data directly to the S3 bucket

Configure AWS DataSync to transfer the data from the on-premises location to the S3 bucket

Ship an AWS Snowcone device to the on-premises location, load the data, and return it to AWS for S3 upload

Establish a Direct Connect connection between the on-premises network and AWS, then use s3 sync to transfer the data

Deploy a NAT instance in a public subnet. Update the route tables for the private subnets to direct internet-bound traffic to the NAT instance.

Deploy a NAT instance in a private subnet. Configure the private subnet route tables to route internet traffic through the NAT instance.

Create a NAT gateway in a public subnet. Update the private subnet route tables to route default internet traffic via the NAT gateway.

Create a NAT gateway in a private subnet. Configure the private subnet route tables to send internet traffic to the NAT gateway.

Deploy two IDS appliances in the shared services VPC, each in a different Availability Zone.

Configure a Network Load Balancer in the shared services VPC. Create a target group and register both IDS appliance instances with it.

Deploy a Gateway Load Balancer in the shared services VPC. Create a target group and register both IDS appliance instances with it.

Create a VPC interface endpoint. Update the shared services VPC route table to direct traffic from other VPCs to this endpoint.

Deploy two IDS appliances in the shared services VPC, both in the same Availability Zone.

Create a VPC Gateway Load Balancer endpoint. Update the shared services VPC route table to direct traffic from other VPCs to this endpoint.

Create an Amazon Aurora PostgreSQL Serverless v2 DB cluster. Migrate the RDS DB instance to the Aurora Serverless v2 cluster. Update the application's connection settings to use the Aurora reader endpoint.

Create an RDS Proxy. Configure the existing RDS endpoint as a target. Update the application's connection settings to point to the RDS Proxy endpoint.

Create a Multi-AZ Amazon Aurora PostgreSQL DB cluster. Migrate the RDS DB instance to the Aurora cluster. Configure an RDS Proxy with the Aurora cluster as the target. Update the application's connection settings to use the RDS Proxy endpoint.

Use AWS Database Migration Service (AWS DMS) to replicate the database to an Amazon DynamoDB table. Update the application to use the AWS SDK to connect to DynamoDB for all database operations.

Enable IAM database authentication on the RDS MySQL instance. Create an IAM role with the necessary permissions and attach it to the Lambda function.

Store the MySQL credentials in AWS Secrets Manager. Create an IAM role that allows the Lambda function to retrieve the secrets and use them to connect.

Configure the MySQL credentials as environment variables encrypted with AWS KMS within the Lambda function.

Use AWS Systems Manager Parameter Store to store the credentials. Grant the Lambda function's execution role access to retrieve the parameters.

Set the reserved concurrency for the Lambda function to the API's connection limit.

Reduce the memory allocation of the Lambda function.

Configure provisioned concurrency for the Lambda function to match the API's connection limit.

Increase the Lambda function's timeout setting.