Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: 686ad334-191c-4e50-bcf0-9db10805c964, api error │ AccessDenied: Roles may not be assumed by root accounts. #106

Open
SasiKumarrr opened this issue Jan 9, 2025 · 0 comments
Open

operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: 686ad334-191c-4e50-bcf0-9db10805c964, api error │ AccessDenied: Roles may not be assumed by root accounts. #106

SasiKumarrr opened this issue Jan 9, 2025 · 0 comments
Labels
bug 🐛 An issue with the system

Comments

@SasiKumarrr
Copy link

Describe the Bug

i have created a two iam role for requester and accepter account i got this i dont why i applied the same roles mentioned in the file

Expected Behavior

i just want to peer to vpc on different account

Steps to Reproduce

can anyone help me with this

Screenshots

Screenshot (2227)

Environment

No response

Additional Context

No response
@SasiKumarrr SasiKumarrr added the bug 🐛 An issue with the system label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 An issue with the system
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SasiKumarrr