Any thoughts on this? Was the AWS console designed to serve infrastructure engineers or DevOps professionals? Is it normal for developers to struggle with it?
Thanks!
1. Constantly switching between different components can cause frequent context switches, making it harder to work efficiently.
2. AWS offers a wide range of capabilities, and developers may struggle with figuring out how to effectively combine them in real-world scenarios.
3. There are many concepts and security restrictions within AWS, such as IAM, which adds complexity to the learning curve.
To make the most of what AWS has to offer, developers need to invest time in studying extensive documentation and even learn Infrastructure as Code. Unfortunately, this can slow down the implementation of innovative ideas.
Fortunately, there are a few new tools that can help address these problems. For instance:
- Plutolang: https://github.com/pluto-lang/pluto
- Winglang: https://github.com/winglang/wing
- Nitric: https://github.com/nitrictech/nitric
Maybe if you use AWS all the time, it makes sense. Howevet, as someone who was just an occasional user, it became far too confusing. I closed our account and found other solutions.
Everything I needed to know was just a few Google Searches away to the official AWS documentation. They are very well written specifically for standard tasks.
The support is also really good, it light years ahead of what you would get from another service like Google Cloud.
You don't have to understand the entire console. You just need to know a few components that will be useful for your situation.
AWS has the some services that supposedly are easy to use like Lightsail but I don't have experience with them.