same pain here
I returned to AWS and was reminded why I left
351–360 of 684 posts
Re: I returned to AWS and was reminded why I left
#352Earlier quoted context omitted.
> It was the sign of a product packed with traps, footguns and all kind of things that would go wrong and the blame goes to the user. I spent 5 years optimizing spendings on AWS at various companies. Yes, it does come with traps and footguns. On the other hand if you know what are you doing, there are plenty of tools to optimize your spendings with RIs, saving plans, auto-scaling, etc, and spend less than the list pr…
Everything you describe is reinforcing the point of the person you are responding to.
Yes, and exactly that is why I started my first comment with this: "I agree with you at some degree".
I agree with him/her, just shared my more nuanced take, based on my experience coming from my past workplaces.
Re: I returned to AWS and was reminded why I left
#353Earlier quoted context omitted.
2FA has been in place for years through email but this new requirement forces a phone.
Good. E-mail based 2FA is bad, and they appear to support TOTP too as an option, as they should. Wish they supported U2F though.
Why is email based 2fa bad but phone good? There are classes of issues you get through phone 2fa compared to email
Re: I returned to AWS and was reminded why I left
#354When it comes to email: “Don’t shit where you eat” is the closest analogy I can think of. Have your email somewhere else, it on any service that might decide to lock your account for any reason. Have your domain ownership somewhere else. And have already, or have a plan already, to move that somewhere if for some reason your email provider gets pissed at you.
Re: I returned to AWS and was reminded why I left
#355Almost everything is true about Azure as well, especially obscure pricing and complexity in absolutely everything.
Re: I returned to AWS and was reminded why I left
#356Earlier quoted context omitted.
> [if] you have the option to walk out, and you don’t Ignores nothing, and blames no victim. It advises people to avoid becoming one when possible.
"all that follows is your own fault" does blame the victim. The abuse is definitely NOT the victim's fault, it's 100% the fault of the abuser. (Most of the time; I won't say there are never mutually-abusive relationships, but most of the time it's one way). Thing about abusive relationships is, though, many (I would go so far as to say "most" but I'm no expert on the numbers) people in one have lots of options to wal…
If the victim had the option to walk, but did not, then it is his fault for not doing that.
If I know a dog is dangerous, but try to touch it anyway and get bitten - then yes the evil dog bit me, but it was my fault for not reacting to danger. Same way with a abusive company, if you know they are, but still make a contract because it seems convenient, then it is still a abusive company, but your fault for getting into a relationship with them.
Re: I returned to AWS and was reminded why I left
#357Earlier quoted context omitted.
please educate instead of insult. happy to hear your response. that is why we’re here, after all.
Sure. CFOs optimise for fewer vendor relationships; fewer invoices, fewer things to talk about during compliance, less reconciliation overhead. Consolidated spend also improves their negotiating position. So when AWS offers good-enough Elasticsearch bundled into an existing relationship, it wins regardless of whether the original is better supported or better value. "More efficiently" means procurement efficiency, no…
thank you. really appreciate that insight.
Re: I returned to AWS and was reminded why I left
#358Years ago, I joined a company, took over a dev team and was asked to launch the product in 3 months. They were using AWS, so I logged in the account to add a few more machines. Right there, in front of my eyes, were the signs of an adversarial, abusive relationship. The UI to fire up a new machine did not show me the price. I had to look up the price in another table that did not have the specs. I had to have the two…
When I log into AWS there is a big graph saying "Cost savings" and offers all the different ways to save money. The idea that AWS is abusive seems a bit much to me. There is Amazon Lightsail for people who prefer pay-monthly upfront costs.
Have you tried to use this feature? From my experience it’s typically reserved instances that provide discounts for longer contracts. It feels a lot like cable TV to me. I think the interface is difficult to use but am able to get what I want from the CLI and some scripts I have aliased.
Re: I returned to AWS and was reminded why I left
#359Earlier quoted context omitted.
Some internal perspective - IAM has maybe thousands of options but fundamentally it is "what does this role have access to doing (action + resource)" + "who has access to this role". That is really it from a 10k foot level. IAM is great because it applies internally just like it does externally. The internal AWS team don't get more access than you do, and if we get access to do certain thing on your account to perfor…
> that's because you have a service principle in your IAM trust relationship that allowed us access That’s why it’s so complicated!!! I don’t understand how I should evaluate trust for your internal EBS org versus your internal ALB org. I kinda just expect it to be all “AWS” trust. And it’s all garbage anyway. There’s no way I can prevent the hypothetically untrustworthy EBS team from surreptitiously adding charges t…
>I kinda just expect it to be all “AWS” trust.
This would be very unwise from security standpoint. Internal access to customer stuff is granular and made hard for internal staff to gain, to minimize chances of screw up intentional or not.
Re: I returned to AWS and was reminded why I left
#360Earlier quoted context omitted.
Doesn't Amazon engineering culture have a very engineer-led product culture? Meaning, devs are often responsible for the UX and flow. I remember many years ago we hired a junior developer who just finished his internship at AWS and he showed me the dashboard he shipped all by himself in the summer with no product or designer help. It looked horrible. Some devs have a good product/UX sense but the vast majority are ho…
AWS UX isn't bad because engineers are bad at UX. It's because inside AWS it's every man for himself, and every team for itself. They don't collaborate, they don't talk, they compete to ship everything as quickly and cheaply as possible - quality, usability, and common sense be damned.
Conways Law
https://en.wikipedia.org/wiki/Conway%27s_law