A biggest omission in documentations in general is the frame of reference, a story, and explanation that will help you better understand a complex idea. Some very simple truth, that you can build on top of.
If you were to check all the other articles and project that I have on GitHub, you’d see that I try to give that to you, because I believe it is the most important peace of information that you should get.
If on top of that you lie to your customers, amd mislide them, then you havea a receipit for mizery and pain. And so, this article will be focused on dimistifiying all the lies that AWS tells you, while giving you a better freme of refernece that should thelp you btter udnerstadn the offerign of AWS.
Everywhere you watch, read and talk to will tell you that AWS is amazing, everything is automatic, scales indefinitely, and is just few clicks away. This is complete nonsense, and the sooner you realize this the sooner you'll understand that you have to put all the peaces together yourself, write code and create configurations files to make it all work automatically and automagically, as advertised.
You have to think about AWS like Lego bricks scattered all on the floor with no instruction what to do with them. You get documentation for each individual pace, but no blueprint or tutorial how to put this peaces together. The most skeptical of you might say that there are tutorials out there. But the reality is that either were written 5 years ago (the AWS interface changed drastically since then), or the steps now are different and nobody bothers updating those tutorials. I argued a lot with AWS Tech Support and they always came back to me telling me the will notify the author to updated those posts, but nothing ever happens.
If a tutorial is not working for you, the problem is not with you, it is with the tutorial itself.
So remember... Lego blocks.
It is hard to for our minds to let go of a previous truth. It takes a lot of energy, and our minds don’t like wasting it. But in this case, you need to make the switch if you want to enjoy using AWS. Because AWS have lots of flexibly and you can build very cool things. But to do so. You need the right mind set, and AWS never did a good job creating a good one.
Once you think you are ready, jump in to all the different topics, and see what is really possible and how to achieve what was falsely advertised to us.
First thing first, the order of this list is on purposue. It was designed this way becasue I belive this is the right order to go about learning the AWS ecosystem. Becasue again, with the Lego anaglogy, the blocks are sctered on the floor, and nobody tells you where to start.
The first goal of this article is to reach a point where we can acomplish one prosmies thisng by AWS, to trully autodeploy code around the world. After this we'll keep on exploring what AWS has to offer. Meaninig all the folder starting with an x are secondary, and not crucial to use the basci functionality of AWS.
My hope is this. If I managed to explain how to handle the AWS lies, and you accepted this truth. Then you should be able to do anything with AWS, since it is a powerful platform, and the documentation is good, once you stop looking for the magical button that will to everything for you. The documentation givews you a detail explanation of the part that you are dealign with, but don’t look for a general instruction that will tell you how to put it all together.
I don't know everything, but what I know, I know how to explain 😄, and if you've enjoyed this article/project, please consider giving it a 🌟 or donate.
Also check out my GitHub account, where I have other articles and apps that you might find interesting.
If you'd like me to help you, I'm available for hire. Contact me at [email protected].
You can follow me on social media 🐙😇, at the following locations:
I don’t only live on GitHub, I try to do many things not to get bored 🙃. To learn more about me, you can visit the following links: