My most received questions:
"How do I start my cloud engineering journey & what's the right path?"
There's not a single or correct path.
There are only recommendations.
A small recap of mine to get yourself going 🧵↓
(1/7) Pick a cloud provider you're interested in:
· Amazon Web Service
· Microsoft Azure
· Google Cloud Platform
It doesn't matter which one you start with.
Even though they are completely different in some ways, a lot of your learnings will be transferable.
(2/7) Register yourself an account
Yes, you need a credit card, but you don't need to be scared of unexpected or exploding costs.
All of the providers are having a generous free tier, allowing you to test and explore their services.
Also, you can create budget alerts later on!
(3/7) Why don't just start with watching tutorials and reading articles?
Even though this is also important, the crucial thing is getting hands-on experience.
Something you learned, but never applied won't help you much and will fade away very quickly.
Get your hands dirty.
(4/7) Don't feel overwhelmed by the number of services you'll find.
Generally, each provider got some core services which are the basics for almost anything that's built and will be built.
Just focus on them in the beginning.
(5/7) Start to learn about your provider's core services and basic networking.
For AWS this would be for example:
· Virtual Private Cloud (VPC)
· Identity and Access Management (IAM)
· Elastic Compute 2 (EC)
· Simple Storage Service (S3)
· Lambda
· DynamoDB
Go step by step.
(6/7) There are countless free tutorials for each service out there you can use to get your first insights.
Always try to apply your gained knowledge by creating something on your own.
It doesn't need to have some actual use case.
It's only about the journey of creating.
(7/7) Recap
Your journey has to be a mix of gaining knowledge through resources and applying them.
Don't get stuck in tutorial hell or overwhelming feelings.
Everybody started at some point and if you're having some burning desire paired with consistency, you'll make it! 🔥
• • •
Missing some Tweet in this thread? You can try to
force a refresh
But they are only useful if you're able to make sense out of them.
Most important for that: using log levels consistently!
· ℹ️ Trace
· 💡 Debug
· ⚪️ Info
· 🟠 Warn
· 🔴️ Error
· ⚡️ Fatal
A small thread about when to use what 🧵↓
(1/7) ℹ️ Trace
Your most verbose logs containing the most fine-grained information.
It gives you detailed insights into what's happening - not only in your code but also in third-party libraries.
Can go as far as documenting every step in a single algorithm.
(2/7) 💡 Debug
Less information than 'trace' level, but still extended to a way that's needed to troubleshoot problems in detail.
Majorly used for pre-production/testing environments and often logs out sensitive information that can't be logged on production.
AWS is growing its number of services at a fast pace.
If we're counting namespaces, the statistics over the past decade are mind-boggling:
· 2013: 25
· 2015: 46
· 2017: 78
· 2019: 182
How to keep up with what's new?
A small thread about sources to keep you up-to-date 🧵👇
(1/4) The AWS News Blog
Guarantees to not miss out on new features or services, but also contains interesting statistics and other insights from AWS itself.
Gets updated very regularly, sometimes several times a day.
If you're only focusing on keeping up with the new capabilities AWS provides, that's your major source.
You'll learn about small or big improvements to existing services, introductions of new ones as well as region expansions.
Scared of getting your hands on at AWS because you're in fear of unexpected costs for the cloud?
You don't have to be!
A small thread about steps you can take to sleep better on your journey to becoming an AWS expert 🧵👇
(1/6) AWS Free Tier #1
AWS grants you a lot of room for experiments for different services each month:
- 1m Lambda Requests
- 25 GB of DynamoDB storage
- 100 build minutes on CodeBuild
... and much more!
Even better: if you've recently created your account, you also have additional free limits for the next 12 months, including for example running a EC2 t2 or t3 micro instance without any costs.