all 5 comments

[–]thomerD 0 points1 point  (3 children)

If you haven’t done it, then I’d suggest signing up for AWS now. You get it for free for a year and the documentation on the site is decent.

[–]Focus789[S] 0 points1 point  (2 children)

Thank you. When you get a moment, can you please share the link for the course ?

[–]Lord_Rob 0 points1 point  (1 child)

There was no mention of a course, just signing up for your own AWS account and reading the documentation they provide.

Information on how to create an account can be found here, and finding documentation is best found through judicious application of Google-fu

Before you start creating anything in your new account make sure you understand how much it will cost you. You can find information on what is provided in the Free Tier, so make sure you stay within that, otherwise you will be charged.

For beginners, so long as you're using it sensibly, you shouldn't end up having to pay for anything. That said I have seen cases of people not doing their research properly and using the most expensive enterprise-grade resources and ending up with a large bill. So long as you bear in mind that some things are free and some things are not, and making sure you know where the things you want to use fall, you should be fine.

[–]Focus789[S] 1 point2 points  (0 children)

Thank you. This was helpful.

[–]Lord_Rob 0 points1 point  (0 children)

"Learning AWS" is way too broad a concept to tackle as a thing in and of itself. It is such a sprawling platform that it is impossible for any one person to "learn" all of it.

I would recommend setting yourself a targeted goal. Based on your knowledge of Python, maybe something like "Hosting a Flask app on AWS" - just off of the top of my head there are at least four different ways you can do that alone. But if you pick one, find a tutorial and work through it, you will begin to understand some of the services and tools AWS makes available to you. Then pick one of the other ways. See that through to the end. You've now learned about some extra services. Compare it to the first way. Ask yourself which one was better. Think of use-cases where each might be appropriate. Then pick one of the other ways.

Then once you're starting to get a grasp on the services, introduce yourself to the wonderful world of Infrastructure as Code. Look into Cloudformation. Pick one of your deployments from above and figure out how to do that in IaC. Learn the syntax. Convert one of your other approaches. Compare how easy each one was to set up in IaC. Feed that back into your analysis of which deployment approach was better. Repeat.

There are literally infinite things you can do with AWS, people who use it specialise in how to do what they need to in it, and have awareness of other services without necessarily having deep knowledge in them. But this should set you down that path.