1 Answer
- Newest
- Most votes
- Most comments
0
Have you tried removing StorageEncrypted: "" entirely? The default is "false" and if you're lucky this won't trigger a stack update. Worth a try I think.
The best solution though, when you've got time, is to convert your DB to encrypted for best practice. The process is in summary:
- snapshot the DB, encrypt the snapshot, then restore (and if you can’t tolerate an outage that long, you’ll need a more complex process involving DMS)
- resolve stack drift by updating the stack with “DeletionPolicy: Retain” on the DBInstance, then updating the stack with the DBInstance removed, then importing the DBInstance into the stack with “StorageEncrypted: true”.
Relevant content
- Accepted Answerasked 22 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated 2 years ago