|
You are here |
manuel.kiessling.net | ||
| | | | |
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",... | |
| | | | |
blog.ryanjarv.sh
|
|
| | | | | ||
| | | | |
develop-build-deploy.com
|
|
| | | | | The second part of my Puppet series explains how to use the infrastructure that was set up in part 1 in order to automatically and centrally manage the configuration of a Puppet client system. | |
| | | | |
general-metrics.com
|
|
| | | Exploring ways to bring a portable HMR client to any dev server. | ||