Amazon ElastiCache for Redis Encryption | An Introduction

Are you looking for an introduction to Amazon ElastiCache for Redis Encryption? Our Redis Support team is here to lend a hand with your queries and issues.

An Introduction to Amazon ElastiCache for Redis Encryption

Amazon ElastiCache for Redis is responsible for supporting encryption in-transit and encryption at-rest. Furthermore, it supports Redis authentication tokens to protect data with additional security controls in the AWS Regions.

Did you know that we can enable encryption in-transit as well as encryption at-rest when we create a new cluster?

In fact, encryption in transit is responsible for encrypting all communications between clients & Redis server as well as among the Redis servers. Encryption at rest improves data security by encrypting data on-disk.

Amazon ElastiCache for Redis offers default encryption at rest, as well as the option to use our own symmetric CMKs or customer-managed customer master keys in Amazon Key Management Service.

When we enable encryption at rest, via CMKs, then Amazon ElastiCache for Redis will encrypt all data on disk-like service backups in Amazon S3. Furthermore, ElastiCache for Redis now offers us more control and flexibility with Amazon KMS integration and support for CMKs.

We can easily enable in-transit encryption through the AWS CLI, the AWS Management Console, or the ElastiCache API.

On the other hand, at-rest encryption is enabled on a replication group only when it is created. This is due to the processing required to encrypt and decrypt the data.

Additionally, enabling at-rest encryption will change the performance during these operations. Our experts suggest bench-marking data with and without at-rest encryption in order to determine the performance impact for each scenario.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To sum up, our Support Engineers introduced us to encryption in-transit and encryption at-rest offered by ElastiCache for Redis.