I came to AWS from Google Cloud, and IAM humbled me
Four things I had to unlearn about identity when I crossed clouds, written by a third-semester student in Oaxaca who spent an evening blaming himself instead of his mental model.
I am writing this from Tehuantepec, a city in the Isthmus of Oaxaca, in southern Mexico. I am in my third semester of Computer Engineering at Universidad del Istmo. I mention it not for sympathy but because it explains how I got here: I did not choose Google Cloud as my first cloud. It was the program that reached my university first, and where I am from you do not pick the door. You walk through the one that opens.
A few weeks ago I finished the Google Cloud Computing Foundations certificate. Compute Engine, load balancing, IAM policies, least privilege, serverless with Cloud Functions, a first look at BigQuery. I was proud of it. I should have been more suspicious of how proud I was.
Then I started on AWS, and most of it transferred beautifully. Compute Engine and EC2 are the same idea wearing different clothes. Cloud Functions and Lambda are the same idea. I could read AWS analytics docs without drowning, because BigQuery had already taught me the shape of the problem.
Identity did not transfer. Identity got in my way precisely because I thought I already understood it.
Here is what I had to unlearn. I am a student, not an expert, and I am publishing this partly so that people who know more than me can correct it in the comments.
The first thing. In GCP I asked who has which role. In AWS I have to ask whether the request survives.
The model I learned in GCP: attach a policy to a resource, bind members to roles, and let it inherit down the hierarchy. Organization, folder, project, resource. Permissions accumulate as you descend. There is one place to look, and looking there answers the question.
AWS does not give me one place to look. A single API call is evaluated against identity policies, resource policies, permission boundaries and service control policies, and it has to survive all of them. The question stops being what does this user have, and becomes: is there anything, anywhere in this chain, that says no.
The second thing: an explicit deny is absolute. My GCP instinct was additive, grant more roles and get more access. In AWS one explicit deny beats every allow above it, however many there are. The moment that clicked, a pile of access denied messages that had felt random turned into a system I could reason about.
The third thing cost me a night: an AWS role has two policies, not one. A GCP service account felt like a single object to me. It is an identity, you grant it roles, done.
An AWS role splits that in half. The trust policy says who is allowed to assume the role. The permission policy says what the role can do once assumed. I built a role with permissions I was sure were correct, and nothing could use it. I read those permissions maybe fifteen times. They were fine. They were always fine. Nothing was allowed to become the role in the first place, and I had no vocabulary for that failure, because in my head roles did not work that way.
The fourth thing: role is a false friend. In GCP a role is a bundle of permissions you grant to somebody. In AWS a role is an identity you temporarily become. Same word, two different objects.
No document lied to me. I was reading the right words with the wrong cloud's meaning quietly attached, and nothing in an interface can catch that. That is the part I keep thinking about. The failure was not in the docs and it was not in the console. It was in a mental model I had earned honestly, in a place that told me I was doing well.
There is a version of this experience where I concluded I was not good at this. I know that version, because for about six hours I was living in it. Where I come from, that conclusion is expensive. A lot of people around me are one bad week away from deciding this world is not for them, and there are not many people nearby to tell them otherwise.
So if you are crossing from another cloud and identity is where you stalled: you are not behind. You are carrying a model that served you well and is now costing you. That is a different problem, and it has a different fix.
I would rather this article be corrected than admired. If you have made this jump, in either direction, what else looked like a translation and was not? And for anyone who learned AWS first and then went to GCP or Azure: does the confusion run the same way, or is it worse coming back?
I will be in the comments. I am still early enough in this that I am mostly here to be told what I got wrong.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article