What Are the Real-World Challenges of Moving to AWS Cloud from Traditional Infrastructure?

Community
1

I’ve been learning more about it, especially how it markets itself as a cloud platform that provides more than just hosting and storage..

I noticed that even though AWS makes a lot of noise about scalability, freedom, and on-demand services, a lot of real users complain about how hard it is to learn how to use it and how hard it is to integrate with other services.

So, here’s my question:

What were the hardest things you (or someone you know) had to deal with when switching from traditional infrastructure to AWS cloud services, and how did you get past them?

That’s how it is with me. Anyone who has used AWS in real life please let me know what they thought or what they think are the best ways to do things.

2

Hello!!!

The IAM and permissions model are by far the most difficult parts of moving to AWS that I have seen.

At first, roles, policies, and groups seem easy enough, but when you add more teams, accounts, and cross-service integrations, it gets really hard.

We had to use terraform to automate policy generation as much as possible, and we had to use a strict tagging strategy and enforce least-privilege roles everywhere.

After that was done, the headaches went down a lot. Also, don’t think that networking things like VPC peering, route tables, and security groups are easy to learn.

If you just assume that the defaults work, you could get bitten.