Master AWS Certifications with Confidence

Amazon Elastic Container Service (Amazon ECS)

AWS Lambda

Amazon Elastic Kubernetes Service (Amazon EKS)

Amazon EC2

AWS Control Tower

AWS Systems Manager

AWS Service Catalog

AWS Organizations

Store the medical imaging data in Amazon S3 Glacier and use Expedited retrievals.

Store the medical imaging data in Amazon S3 Glacier and use Standard retrievals.

Store the medical imaging data in Amazon S3 Standard-Infrequent Access (S3 Standard-IA).

Store the medical imaging data in Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA).

Use separate AWS Glue jobs for each partner. Configure each job with server-side encryption using Amazon S3 managed keys (SSE-S3) to encrypt the output data.

Deploy dedicated Amazon EMR clusters for each partner. Apply client-side encryption with custom-managed keys (CSE-Custom) to encrypt data during processing.

Use separate AWS Glue jobs for each partner. Configure each job with client-side encryption using AWS KMS keys (CSE-KMS) to encrypt data during processing.

Deploy dedicated Amazon EMR clusters for each partner. Apply server-side encryption with AWS KMS keys (SSE-KMS) to encrypt the output data.

Deploy Amazon EC2 instances with individual Elastic IP addresses. Configure a Network Load Balancer (NLB) with the static TCP port, register the EC2 instances with the NLB, and create an A record for global.service.com pointing to the EC2 instances' Elastic IP addresses. Share these Elastic IPs with partners for allow lists.

Use an Amazon ECS cluster with tasks assigned public IPs. Set up a Network Load Balancer (NLB) with the TCP port, link the ECS service to the NLB via a target group, and create an A record for global.service.com mapping to the ECS tasks' public IPs. Provide these IPs to partners.

Deploy EC2 instances across Availability Zones. Assign one Elastic IP per Availability Zone and attach them to a Network Load Balancer (NLB) configured with the static TCP port. Register the instances with the NLB's target group. Create an A (alias) record for global.service.com pointing to the NLB's DNS name. Share the NLB's fixed Elastic IPs with partners.

Host the service on an Amazon ECS cluster with public IPs for each host. Configure an Application Load Balancer (ALB) for the TCP port, associate the ECS service with the ALB via a target group, and create a CNAME record for global.service.com linked to the ALB's DNS name. Provide the ALB's IPs to partners.

Develop an AWS CloudFormation template that defines the existing infrastructure, using parameters for Region-specific values. Deploy this template in the second Region.

Manually replicate the infrastructure in the second Region using the AWS Management Console, ensuring all configurations match the original Region.

Configure Route 53 to use geolocation routing, directing users to the nearest Region's ALB.

Update the Route 53 record to use latency-based routing, optimizing traffic distribution between the two ALBs.

Enable DynamoDB Streams on the existing table and add a replica in the second Region to create a global table.

Create a new DynamoDB table in the second Region, enable DynamoDB Streams, and set up a global table. Migrate data from the original table once.

User ID

Registration timestamp

Approval status

Feedback score from 1 to 10

Upload the ZIP file to Amazon S3. Configure the Lambda functions to reference the S3 bucket and key in their import statements.

Create a new Lambda function containing the libraries. Update the existing Lambda functions to invoke this new function synchronously.

Create a Lambda layer containing the ZIP file. Attach the layer to each required Lambda function.

Configure each Lambda function to mount an Amazon EFS file system where the libraries are stored.