I spend a fair amount of time thinking about and talking to people about where IAM fits in the job. Cloud engineering as a whole has become such a vast subject with a number of focus areas and learning paths, that it’s easy to get lost. While it’s great that software delivery has become more of a team sport than ever before, modern cloud architectures also place a lot of responsibility on individuals to learn new things.
I aim to tackle cross-functional responsibilities – personal and technical – through a series of articles looking at AWS IAM through the lens of specific job functions. These aren’t meant to be 101 pieces that describe the basic elements of IAM, rather a selective look at things that really matter. As a function so closely tied to software delivery, I started the series with Software Developers.
Give a read, and be on the lookout for more in the series. I’d be interested in hearing from you too – given your role, what do you think is most important to know about IAM?
Tweet
Share