Seeding of a Elasticache cluster in another account in another region
0
Giving an example : Let's say I am in AWS region A , in AWS Account AA & have a Elasticache cluster ECA. And I export the backup of ECA to S3 bucket SBA. Now in another region B, if I have an account AB and Elasticache ECB, would ECB be able to read from SBA (s3 bucket of first account )?
asked 2 years ago965 views
2 Answers
- Newest
- Most votes
- Most comments
0
If I understand your question, you want to provide access from account AB into the S3 bucket of account AA, correct? You can follow this guide to set up cross account S3 access: https://aws.amazon.com/premiumsupport/knowledge-center/cross-account-access-s3/ . If you have done this already, and these instructions are not solving your problem, please provide more details, error messages, and such.
answered 2 years ago
0
Make sure to check these 2 things -
- Copy the backup (.rdb) from the S3 bucket (region A) that contains the backup to an S3 bucket located in the region B where the Redis cluster is being restored. aws s3 cp
- Grant ElastiCache access to the .rdb backup object in S3 using a canonical ID or bucket policy (this should be done to the backup file as well, not just the bucket). Procedure detailed here.
answered 24 days ago
Relevant content
- Accepted Answerasked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you Byron. I have exported a ElastiCache cluster backup (backupEC.rdb file) to S3-bucket-in-AccA . I have then added bucket policy for useraccB as principal for this bucket S3-bucket-in-AccA. Now I login to AccB as useraccB and try to seed a ElastiCache cluster with backupEC.rdb file. But my Elastic cluster is not getting created. I am not seeing any error messages except Create_Failed in ElastiCache console. So more than account access, I am trying to ask if ElastiCache cluster in an account can be seeded from a backup in another Account assuming we have right policies attached for the user to S3 bucket. Hope it clarifies a bit more.