Explore >> Select a destination
|
You are here 
|
manuel.kiessling.net | ||
| | | | |
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. | |
| | | | |
awsteele.com
|
|
| | | | | Here's my seventh or eighth attempt at a blog. It's mostly going to be my experimentation with using AWS (Amazon Web Services, not Aidan William Steele). | |
| | | | |
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.hackeriet.no
|
|
| | | Let us go over the stack we use to power this blog and why it's both easy to use and fast for our visitors. The goal is to serve the blog as fast as possibl... | ||
