|
You are here |
manuel.kiessling.net | ||
| | | | |
blog.atj.me
|
|
| | | | | The personal blog of Adam Jarret | |
| | | | |
it20.info
|
|
| | | | | This is my first blog post as an AWS employee. I have spent the last 6+ months learning new things (IAM being one of them) and I figured I could (and should) ... | |
| | | | |
memo.mx
|
|
| | | | | In AWS, in order to access resources in other accounts without creating new users or handling passwords, you can use sts:AssumeRole. Let's say that you have some resources in AccountA (AWS Managed Prometheus for example) that you want to access from AccountB Account A In AccountA create a role account_a_role that has 2 types of policies: a Trust Relationship that define which entities can assume this role { "Version": "2012-10-17", "Statement": [ { "Sid": "AllowAssumeRoleFromAccountB", "Effect": "Allow",... | |
| | | | |
pliutau.com
|
|
| | | Software Engineering Lead with a passion for APIs, Web, Cloud, Microservices, DevOps, Kubernetes etc. Engineering Lead at solsten.io | ||