NovaCare Telehealth is modernizing its HIPAA-compliant patient-record processing service by migrating its on-premises microservices to AWS. The target architecture must run on Amazon ECS using the AWS Fargate launch type to minimize operational overhead. The containers must run in a private VPC with no internet access. The application needs to securely retrieve database credentials and API keys stored in AWS Systems Manager Parameter Store. These parameters are encrypted using a customer managed key (CMK) in AWS Key Management Service (AWS KMS) located in a centralized security account. All AWS service traffic must traverse private VPC endpoints. Which solution configuration meets these security and compliance requirements with the least operational overhead?
- ADeploy the Amazon ECS tasks using the AWS Fargate launch type with the bridge network mode. Create interface VPC endpoints for Systems Manager Parameter Store and AWS KMS in the application VPC. Grant the ECS task execution role permissions to decrypt the customer managed key in the security account and read the parameters.
- BDeploy the Amazon ECS tasks using the AWS Fargate launch type with the awsvpc network mode. Create interface VPC endpoints for Systems Manager Parameter Store and AWS KMS in the application VPC. Configure the Parameter Store parameters to use the AWS-managed KMS key in the centralized security account, and grant the ECS task execution role permissions to decrypt the parameters.
- Deploy the Amazon ECS tasks using the AWS Fargate launch type with the awsvpc network mode. Create interface VPC endpoints for Systems Manager Parameter Store and AWS KMS in the application VPC. Grant the ECS task execution role permissions to decrypt the customer managed key in the security account and read the parameters.Answer
- DDeploy the Amazon ECS tasks using the AWS Fargate launch type with the awsvpc network mode. Create interface VPC endpoints for Systems Manager Parameter Store and AWS KMS in a shared services VPC. Configure a Route 53 private hosted zone in the shared services VPC to resolve endpoint DNS names, without associating the private hosted zone with the application VPC.