2 Answers
- Newest
- Most votes
- Most comments
0
I figured it out by myself: https://stackoverflow.com/a/45881950/393157
I want to repeat, that this kind of problem is very annoying, time wasting and feels exceedingly unnecessary.
answered 7 years ago
0
I found another root cause for this, and another solution:
Just create, then delete, a RDS in the target region!
AWS RDS simply refused to copy a snapshot, no matter what I did to key policies, UNTIL I created a small, automatic RDS. Now any key works "out-of-box", even new ones without any policy change!
answered 5 years ago
Relevant content
- Accepted Answerasked 3 years ago
- Accepted Answerasked a month ago
- Accepted Answerasked 2 months ago
- How do I restore a KMS-encrypted back up file to RDS for SQL Server from an on-premises environment?AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 years ago