A company is running an application that uses an Amazon ElastiCache for Redis cluster as a caching layer. A recent security audit revealed that the company has configured encryption at rest for ElastiCache. However, the company did not configure ElastiCache to use encryption in transit. Additionally, users can access the cache without authentication. A solutions architect must make changes to require user authentication and to ensure that the company is using end-to-end encryption. Which solution will meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Create an AUTH token. Store the token in AWS Secrets Manager. Configure the existing cluster to use the AUTH token, and configure encryption in transit. Update the application to retrieve the AUTH token from Secrets Manager when necessary and to use the AUTH token for authentication.
Most accepted answer: B. Create an AUTH token. Store the token in AWS Secrets Manager. Configure the existing cluster to use the AUTH token, and configure encryption in transit. Update the application to retrieve the AUTH token from Secrets Manager when necessary and to use the AUTH token for authentication.
Community votes: A=5, B=10
Selected Answer: B AWS “What’s New” Announcement (Dec 28, 2022) “Amazon ElastiCache for Redis now supports updates to encryption in transit on existing cluster resources. You can change the TLS configuration of your Redis clusters without re‑building or re‑provisioning them or impacting application availability. ... Upgrade your Redis cluster to version 7 or above. You can then modify the encryption‑in‑transit property for your cluster using the ElastiCache Console, API or CLI.” https://aws.amazon.com/about-aws/whats-new/2022/12/amazon-elasticache-redis-enabling-encryption-transit-existing-clusters/?utm_source=chatgpt.com upvoted 4 times
Selected Answer: B Elasticache can be updated to support AUTH. Note: RBAC replaces AUTH now. upvoted 2 times
Selected Answer: A Encryption in transit cannot be enabled on an existing ElastiCache cluster. A new cluster must be created. upvoted 4 times
Selected Answer: B Amazon ElastiCache for Redis now supports updates to encryption in transit on existing cluster resources. You can change the TLS configuration of your Redis clusters without re-building or re-provisioning them or impacting application availability. When enabling encryption in transit, your overall solution can remain connected to Redis clusters. To get started, upgrade your Redis cluster to version 7 or above. You can then modify the encryption-in-transit property for your cluster using the Elasticache Console, API or CLI. This feature is available in all regions at no additional cost. To learn more, see the ElastiCache user guide. upvoted 3 times
Selected Answer: A The correct answer is A - Create an AUTH token, store it in Parameter Store, and create a new cluster with AUTH and in-transit encryption. Key reasons: ElastiCache doesn't allow enabling AUTH on existing clusters SSL certificates aren't used for Redis authentication Parameter Store is more cost-effective than Secrets Manager for this case Solution meets both requirements: AUTH authentication and end-to-end encryption upvoted 2 times