Let's face it, AWS can make you pull your hair out if you don't understand what's happening.
Scratch that, that's programming in general.
What I'...
For further actions, you may consider blocking this person and/or reporting abuse
My two concerns about AWS
Cost Monitoring is a really painful problem and trust me there's MANY people who have this issue!
There are some companies trying to fix it, but AWS is so cryptic in its spend sometimes it gets really hard to showcase
Lock-in, also fair, but thats the case with most cloud tools though and why they're valued at such high numbers, the LTV is off the chart
Lock-in,
this really depends, you can limit your lock in by using Docker based deployments. But even if you don't, there's always a form of lock in whatever solution you choose to use and there's always a cost to re-engineer the solution regardless of platform. So I believe the lock-in issue isn't that much of a deal, and especially not these days with virtualization and cloud agnostic deployment options available in the worst case.
Cost monitoring,
The tagging system in AWS is extremely important to use consistently such that you can more easily group your deployments and get pretty accurate day to day spend of those deployments. In cost explorer it's then a piece of cake to see which parts of your application incur what costs.
Then budget alerts are there to cover hard number value alerts.
If you're running a multi account setup, use organizations with consolidated billing. All your billing for all sub-accounts goes to one account. Again, the tagging system you've setup will help you sort out exactly what spend comes from where.
Really the tools are there.
Cost monitoring has improved a lot in the past couple of years. From my experience in the past couple of years, AWS spends a significant amount of engineering effort reduce churn due to cost especially for companies that are not fully locked in (😉), the alerting can be set to a smaller window such is 1 hr. Allowing you to monitor cost in really smaller increments. Also you should make the most with the Solutions Architects AWS provide. They bring in a lot of tips on how well you can cut down cost.
If you are using something like Terraform for IaC, there are some plugins that estimate the resource cost before provisioning.
In terms of vendor lock-in it's more or less a design problem and a trade off we make during development/product planning. Has nothing to be done on AWS side. Its a conscious decision we make when opting in.
Anywhere else that's just called "Sales Engineer"
Great response Gayan!
Thanks for sharing this! Really appreciate it
As I'm predominantly a back end developer, with a life-long experience in Linux, I think you've grossly over-simplified the terms, but kudos on the attempt at least.
Noting what you list as your job title, please, for the love of everything holy tidy up the reference to "tunnelling" - when you say that, those of us with experience in Linux read "SSH tunnel", and that's categorically not what happens when you connect to an EC2. It's much closer to simply "SSHing" to an EC2 than it is "tunnelling."
Hey Dave
Hahaha, I have, the target userbase for this article is definitely not people like you and me who have an nth layer understanding of how things operate, but rather for people who're just getting into space
"Noting what you list as your job title, please, for the love of everything holy tidy up the reference to "tunnelling"" - hahaha this made me laugh - love it!
It is simply SSHing, but to make it sound cooler I called it tunnelling 😂
Thanks for the feedback though, I'll update the point
Wish this post existed years ago. ;-)
🙏🙏🙏🙏🙏🙏
Good summary Vaibhav :) Will wait for next post:)
Thanks mate! Out soon 😊😊
Great Article!
Loved how you gave realistic use-cases related to each service.
Thanks mate!
Very nice one! Looking forward for more in this topic
Thanks mate! More to come for sure!