1 Answer
- Newest
- Most votes
- Most comments
0
That is not a good practice and will complicate the maintenance and your users access to the data (remember they need both permission to the catalog and to s3).
You can use a role from account B which has permission to the bucket in A but I would recommend instead moving the data to account B if possible or using the crawler in account A and then sharing the table with account A using the LakeFormation
Relevant content
- asked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago