|
You are here |
notes.rolandcrosby.com | ||
| | | | |
seanmcgary.com
|
|
| | | | | ||
| | | | |
fak3r.com
|
|
| | | | | ||
| | | | |
ptimofeev.com
|
|
| | | | | A look at what Infrastructure as Code is and how it can be used in a practical exercise: spinning up a proxy server on Amazon AWS with Terraform. | |
| | | | |
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",... | ||