/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 manuel.kiessling.net
Single Sign-On and Resource Separation on AWS Manuel Kießling
| | it20.info
AWS Identity and Access Management: Introduction to Resources Access Control | IT 2.0
3.6 parsecs away

Travel
| | 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) ...
| | src-bin.com
An AWS account just for getting into other AWS accounts
3.4 parsecs away

Travel
| | In You should have lots of AWS accounts, I made a case for isolating environments and even services in their own accounts to reap all sorts of security, reliability, and compliance benefits. With the right tools in hand (Substrate, for one), operating lots of accounts can be just as efficient
| | memo.mx
AWS | Cross-Account IAM Role Assumption | Memo Garcia
3.4 parsecs away

Travel
| | 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", "Principal": { "AWS": "arn:aws:iam::ACCOUNT_B_ID:role/account_b_role" }, "Action": "sts:AssumeRole" } ] } You can also set Conditions to filter which entities can AssumeRole and even configure AssumeRoleWithWebIdentity for users who have been authenticated w...
| | notes.rolandcrosby.com
Deploying a blog with Hugo and AWS · Notes
16.9 parsecs away

Travel
| [AI summary] The author details the process of deploying a static Hugo blog to AWS using S3, CloudFront CDN, and a Lambda@Edge function to handle directory indexing.