1 Answer
- Newest
- Most votes
- Most comments
2
If the error occurs solely on the side of Account B, it could be due to an improperly defined cross-account policy. Please ensure that the roles in your Account A, which Account B assumes to run queries and receive results, are correctly configured. You can refer to the tutorial on cross-account roles at https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html for guidance.
For troubleshooting, you can also attempt to assume the role from the same Account A and execute queries to verify if the issue lies within the role configuration.
Relevant content
- Accepted Answerasked 7 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago