Who cares what OS the AWS machines are running? I can’t touch it, it’s completely inaccessible for me and other clients. I can only touch the services which AWS provides. I wouldn’t know the difference if it was running windows, since the OS is completely transparent, basically a hidden implementation detail.

You keep making the assumption that AWS == EC2, meanwhile it is just one of many services AWS provides.

Abstracting away is costly. You can target only the lowest common denominator. The abstractions are going to leak. It’s like the criticism of ORMs, only worse since SQL is at least standardized.

I’m in a golden cage where my job earns about twice or more of what a large majority of remote jobs offer (available where I am, which is Europe).

I guess I could get very lucky and find a great paying remote job, but I feel like I could lose in the end.

People still want the money, tho. It’s the main reason I’m staying in my no-remote job.

RabbitMQ is more expensive on AWS than e.g. SNS/SQS. It’s not a coincidence, you’re trading lock-in for a cheaper price.

The increased complexity comes from the fact you will need some components which exist in either managed, but vendor lock-in form, or you need to spin them up / managed yourself.

Being cloud-agnostic also means additional cost/complexity.

Sometimes the only way to win the game is by not playing it.