Job titles are vague and not standardized, so all I can really say is focus on what's relevant to the work you want to do. For example, if you want to automate tasks on AWS, you definitely want to learn boto3. Anything covered here is potentially relevant: https://github.com/tuladhar/Python-for-SysAdmin More on reddit.com

I'd say the biggest difference between the 3 is that AWS started with the smallest building blocks/primitives (IaaS) and then built higher order services on top of them. Azure and GCP started with higher order services (PaaS) and then brought in IaaS offerings. I think this is most evident in that AWS seems to be the most flexible but also requires the most "glue" to create fully functioning services. For the most part I'm going to exclude Azure here - it's the most expensive and while they've made great strides in supporting Linux it's still primarily MSFT-stack-centric. In my experience AWS has an excellent python SDK (boto3). I haven't dealt much with GCP outside of Terraform to say how its SDKs are. I will say GCP is great as long as you're committed to doing things The Google Way - stepping outside of that even a little seems very painful and we find ourselves contorting into unnatural shapes to get things working in there as an enterprise. In terms of cost GCP is generally considered the cheapest, AWS second, Azure third. Performance-wise I'd say AWS and GCP probably keep leapfrogging each other for the biggest/fastest VMs. They'll all probably run identical code within milliseconds of the others. Network is a really big differentiator here. AWS seems to be much easier to deal with - we've been banging our heads on GCP networking for months now. The story a while back was that GCP was way less oversubscribed and the network performed better. I find the AWS console way more intuitive than GCP, but if I didn't have the context for the comparison GCP may not be as frustrating. GCP will silently create things in your projects just because you clicked on a service name in their console accidentally, and I find it incredibly frustrating trying to find things in their menus. IAM in AWS is both a dark magic and my favorite of the identity models. While GCP and Azure might be simpler to get started with, once you learn the AWS model it provides a very expressive language that allows you to do things fairly easily that become more difficult in GCP and Azure. And finally the enterprise support from AWS is outstanding (for us - this may vary by actual AWS support staff and your level of support). GCP still has a ton of catching up to do in this respect, but they're aware of it and working on it. Ultimately I'd design a POC project that you can deploy in any of them and see which feels best - neither is a bad choice. More on reddit.com

Bash, $cloud-cli and jq goes a long way as well. More on reddit.com

Cloud computing is sort of "self-service compute/storage/network services on someone elses hardware". The concepts around this is not tied to a specific programming language. To learn to work with cloud computing, it is probably better to combine that with things you already know. Try not to learn too many new things at the same time. More on reddit.com