- Newest
- Most votes
- Most comments
If I am reading this correctly, you should be able to set the role session name to whatever you want it to be (providing that you haven't built conditionals within the trust.
Try using whatever you want, also I am a big fan of using AWSume which makes setting role chaining easier IMHO. Give it a try. Getting your trust and policy statements to work are essential so that as you assume one role to the next the role assumed is included as being "ok" to assume another.
The problem is that, if i attach policy (which can be found on the link i have shared in the question) to the role "A" im not able to provide everything in the "session name" (and i dont want it to be like that), so im trying to understand what it expects in this case. Im trying to force user to provide its username as session name for trailing purposes, and the policy works in case of IAM user - IAM role connection, but not in the IAM role - IAM role. Thought i havent looked into the AWSume, will do, thanks.
Relevant content
- asked 10 months ago
- asked 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
@Joann Babak did my answer work for you ? Let me know if you have any issues with this, or if it helps you then please accept my answer after you've tried it out - it would be much appreciated! Good luck :)