Sometimes writing AWS IAM policies gets confusing. Especially if our policy authoring is reactive in nature instead of following a proactive permissions strategy.
The fact that IAM policies contain some restrictions doesn’t really help either.
To start off, let’s take a look at what the IAM policy evaluation order looks like:
Wow — this is complicated! Additionally some of the documentation and courseware suggest doing both allow and deny-statements.
Well the Amazon S3: Limits managing to a specific S3 Bucket example in the IAM User Guide shows the idea.
Let’s admit it. We access more and more of the information we need in our daily activities using URLs. These URLs have become longer and more cryptic over time but that’s ok since we simply click on them.
However, sometimes we need to communicate those URLs in a non-internet-native way. For me this has happened during training classes as well as when writing a book. I want the class to download a piece of source code, but the GitHub project file URL is way too long to be correctly retyped by the attendees. …