A healthcare company is developing a multi-tier web application to manage patient records that are in an Amazon Aurora PostgreSQL database cluster. The company stores the application code in a Git repository and deploys the code to Amazon EC2 instances.
The application must comply with security policies and follow the principle of least privilege. The company must securely manage database credentials and API keys within the application code. The company must have the ability to rotate encryption keys on demand.
Which solution will meet these requirements?
Requirement Summary:
Multi-tier app on EC2 + Aurora PostgreSQL
Must comply with least privilege and security policies
Need to manage credentials and API keys securely
Must support key rotation on demand
Evaluate Options:
A . Secrets Manager + AWS managed KMS keys
Best practice for secure secret storage
Supports auto rotation
Uses AWS SDK to fetch at runtime (secure, avoids hardcoding)
AWS managed keys are rotated automatically and easier to manage
B . Secrets Manager + customer managed keys
Also valid, but adds complexity
Since the question asks for LEAST development effort, AWS-managed keys are preferred
C . Store secrets in code
Violates all security best practices
D . Use SSM Parameter Store + AWS managed keys
Possible, but Secrets Manager is preferred when rotation is needed
Parameter Store does not natively rotate secrets
Secrets Manager: https://docs.aws.amazon.com/secretsmanager/latest/userguide/intro.html
Automatic key rotation: https://docs.aws.amazon.com/kms/latest/developerguide/rotate-keys.html
Eileen
2 hours agoSimona
6 days agoCraig
11 days agoJutta
17 days ago