2 Answers
- Newest
- Most votes
- Most comments
0
Hi,
One option would be to create a policy for the execution role of your AWS Lambda function that allows access to a role in account B. That role should in turn allow access to the resource, in this case the S3 bucket. You can find more information in this article: https://repost.aws/knowledge-center/cross-account-access-s3
0
A better way to answer this question would be to understand you end goal and requirement.
Do you just require a copy of the RDS instance to be available in a different account? If so, have you thought about using AWS Backup?
Relevant content
asked 2 years ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
I'll explain in more detail:
Hi, the above still applies. The difference is in this case that you give permissions to the AWS Lambda function in account B to access a role in account A. That role in account A then gives access to RDS.
However, you could just copy the snapshot manually via the CLI, see https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/copy-data-from-an-s3-bucket-to-another-account-and-region-by-using-the-aws-cli.html