5 ms·
I disagree. Once you learn IAM and able to segregate users into groups each with its own layer of security, then it is good enough. Often the UI, and docs make
by f430 6y ago
I disagree. Once you learn IAM and able to segregate users into groups each with its own layer of security, then it is good enough.
Often the UI, and docs make it seem like everything is all over the place but AWS feels like lego with some pieces tucked away. That is where I think AWS can be improved upon with a better documentation UI and discoverability.
I do have to commend Google on Flutter + Firebase + Firebase Functions. I think if Amplify focused on serving Flutter users more it could pull me away from Google altogether.
Unfortunately, Google has done a fantastic job with making Flutter integrate with Firebase through Android Studio and there really is no product from AWS that matches its developer friendliness and low learning curve. This makes it very easy to switch.
I guess it is somewhat of a threat because the Firebase Cloud Functions also offer something of a counter to AWS Lambda as much as I love using it with API Gateway.
- Fordec 6y agoIAM shouldn't be a thing to learn. It's account management, default and easy to access options should be sane enough for most people to use. At big companies, sure someone has it as a dedicated part of their job description. But if you're in the majority of smaller companies, ones maybe that's just doing e-commerce and tech isn't their core skill set, account settings should be near invisible and still be trustworthy. It's not the Slacks of the world that have an issue with this, but the long tail of the world we now live in that software has eaten and companies are just scrambling to exist in it. Flutter integration is not in the list of concerns of this long tail. And telling them to "just learn it" isn't the customer focused mindset, it's the engineering one.
- cbushko 6y agoI created all of the IAM roles that our 100+ person company uses. It was and is important from a security standpoint that we do not just blindly give too many permissions to employees. I had to do some research to understand what the bare minimum was and it wasn't too difficult to do. Custom roles created through Terraform helped a lot.
- f430 6y agoIt absolutely is required beyond small 3 person startups. Google is great to get started but when you are dealing with a dozen or more developers, especially at large organizations IAM offers that granular control and overview. Yes its a bit of a pain having to add policies sometimes when you are first getting started but once it's up and running you can rest easy. Learning it isn't that much more time consuming or difficult, its just a bit of effort that is all (we are talking a few hours at most).
- manigandham 6y agoWhat exactly are you disagreeing with? Segregating users into groups is possible with either platform. The discussion is about GCP having much better functionality around it where projects and permissions are naturally integrated with gsuite organizations and users. This is objectively true. AWS has an archaic project system with a dozen different attempts at uniting it all but nothing comes close to GCP's smooth and easy manageability.