You cannot directly configure RDS Read Replicas to be encrypted if the source DB instance is unencrypted. However, you can create an encrypted snapshot of the original unencrypted database and then restore from that snapshot to create an encrypted RDS instance or its read replicas.
Here's a step-by-step process:
- Create a Snapshot: Take a snapshot of your existing unencrypted RDS instance.
- Encrypt the Snapshot: When copying this snapshot, you can enable encryption for it using AWS KMS (Key Management Service).
- Restore from Encrypted Snapshot: Restore the encrypted snapshot to create an encrypted version of your original database or its read replicas.
Therefore, while you cannot directly encrypt a Read Replica of an unencrypted RDS instance, you can achieve this by first creating and then restoring from an encrypted snapshot.
So the correct answer is:
No, you must first restore the source DB instance from an encrypted snapshot to create encrypted Read Replicas.
This ensures that all data at rest in your database environment is securely encrypted.
Read the full article at DEV Community
Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.

![[AINews] The Unreasonable Effectiveness of Closing the Loop](/_next/image?url=https%3A%2F%2Fmedia.nemati.ai%2Fmedia%2Fblog%2Fimages%2Farticles%2F600e22851bc7453b.webp&w=3840&q=75)



