|
|
|
|
|
|
by serverlessmom
1570 days ago
|
|
|
> Permissions in GCP seem like a mess, I’m trying to use python to get credentials and there is a whole python library for authentication and getting credentials (google-auth). I feel you, but I gotta agree with the other commenters that it's really just about time and experience. Anyone long-experienced on one public cloud will really struggle switching clouds. Your experience is low but your expectations are high. You're not just poking into a dashboard trying to spin up a single VM, you want to do all the stuff you're used to doing on AWS. While IAM does feel easy once you know it, as someone who's run hackathons and bootcamps I can say it's not easy for everyone to just pick up. It's as complicated as it needs to be, but yeah it can be a steep learning curve. |
|
|
AWS is great, has many options, is ubiquitous across verticals and is everywhere, but it lacks polish in many ways. GCP offers similar tools to that of AWS but, in many ways, feels more polished and offers tools that are integrated across the ecosystem by those who don't want to have to mess with the underpinnings of the infrastructure, roll their own, or have to buy third party services if they do not want to.
That all said, IAM on both absolutely suck. I should NOT need to read the documentation or study the systems like I do to get it up and running. Both providers seriously need to up their game here and offer sane and secure defaults that just work. The last time I dealt with AWS I wanted to pull out my hair (and this could be due to my heavy investment in GCP) and while GCP is frustrating with IAM, it wasn't nearly as arcane as I felt AWS was.
YMMV.