Explore >> Select a destination
|
You are here 
|
nodramadevops.com | ||
| | | | |
www.stackery.io
|
|
| | | | | In my last post we looked at the structure of AWS IAM policies and looked at an example of a policy that was too broad. Let's look at a few more examples to explore how broad permissions can lead to security concerns. | |
| | | | |
www.serverless.com
|
|
| | | | | Learn the basics of IAM permissions with your Serverless projects. | |
| | | | |
src-bin.com
|
|
| | | | | 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 | |
| | | | |
www.woolyknit.com
|
|
| | | |||
