- Newest
- Most votes
- Most comments
There was an issue with the service starting on 21-02-2023, which is resolved now after deployment of a fix. Cross region snapshot Copy should be working now from the console as well. If it is still an issue for a specific region; as a workaround, you can use below AWS CLI to copy the snapshots (modify according to your environment).
$ aws rds copy-db-snapshot
--source-db-snapshot-identifier <ARNofSourceSnapshot>
--target-db-snapshot-identifier <TargetSnapshotIdentifier>
--kms-key-id <ArnOfTargetKMS>
--source-region <SourceRegion>
--region <DestinationRegion>
I found this
You must use this option if the DB cluster snapshot is encrypted and you are copying the snapshot to another AWS Region. In that case, you must specify a KMS key for the destination AWS Region.
in this doc https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-copy-snapshot.html#aurora-copy-snapshot.AcrossRegions navigate to Copying an encrypted DB cluster snapshot by using the AWS CLI or Amazon RDS API
Basically there is no way copy an encrypted snapshot from one region to another using AWS Web Console, because you need to perform the API Call in from the destination region and the Copy Snapshot Web page will be in the source region.
Here is the command:
aws rds copy-db-cluster-snapshot \
--source-db-cluster-snapshot-identifier arn:aws:rds:us-east-2:1234567890:cluster-snapshot:my-snapshot-20230222 \
--target-db-cluster-snapshot-identifier my-snapshot-20230222-from-ohio \
--kms-key-id asdlkj-aasdlkj-230498234 \
--profile my_personal_profile \
--region us-west-1
At the end I had to specify the --region to previous params like --kms-key-id and --target-db-cluster-snapshot-identifier telling them where should they live.
Sounds like a key issue.
If you copy an encrypted snapshot across Regions, you will need to specify a KMS key valid in the destination AWS Region. It can be a Region-specific KMS key, or a multi-Region key.
More here . . . https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html
I don't think this is a key issue, at least not for me. I have been copying an automated snapshot of our production RDS instance in us-east-1 (N. Virginia) daily to the us-west-2 (Oregon) region for the past several months using the RDS Management Console and specifying a valid KMS key in the us-west-2 region. Yesterday, Feb 21, for the first time this procedure failed with the error message: "Unable to parse sigV4 params, params missing." I continue to get the same error today as well.
I get the same error message when I copy from us-east-1 to us-west-2 and specify the (default) aws/rds key.
Same here. I have been copying snapshots between Ohio and Virginia for the past 5 years and starting yesterday, Feb 21, it fails and I get the same error. This has become a high priority issue for us, please offer any assistance.
Relevant content
- asked 5 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Thank you! I was able to copy the last three encrypted RDS automated snapshots from us-east-1 to us-west-2 using the AWS RDS Management Console without any issues just like I used to be able to prior to getting the "Unable to parse sigV4 params, params missing." error message on 2/21/2023. I find it surprising that, if this was due to an issue with the service, there was no indication of it in the Event log in the AWS Health Dashboard, which is one of the first places I looked when trying to figure out what might have been the cause of the error.