YouTube Transcript:
AWS Cloud Was HARD Until I Learned These 5 Secrets!
Skip watching entire videos - get the full transcript, search for keywords, and copy with one click.
Share:
Video Transcript
View:
look at all of these services that you
need to understand to learn Cloud
engineering it can be really hard and
I'll be honest it was for me as well
until I learned these five Secrets which
nobody really teaches you although
everyone should know them hi I'm slan
I've worked in tech for a decade and
today I run my own AI Cloud security
consultancy the truth is these secrets
took me way too long to figure out on my
own and in this video I'm going to
reveal them to you so you don't have to
struggle for as long as I did but first
let me share the single biggest mistake
almost everyone makes they don't know
where to start so they try to learn and
memorize every single service AWS alone
has over 200 services with constant
updates and new ones being added all of
the time it's a NeverEnding race now the
good thing is there is a solution and it
begins with secret number one Focus your
learning on a handful of foundational
components that appear in nearly every
cloud infrastructure I call these the
core four comput storage networking and
security but why these four well because
every major application that we all use
like Netflix or Airbnb is built on these
foundational components mastering the
core 4 gives you a solid grasp of what
most Cloud applications need everything
else like serers containers or
specialized databases Builds on top of
these fundamental layers the second
secret to learning cloud engineering is
developing what I call a first principal
mindset set that might sound very
complex but it's not and here is why
when you're learning a new service or
feature you want to strip away the fancy
names or any marketing fluff in order to
understand the core problem it was
designed to solve you see nearly every
cloud service that exists falls into the
core four we just mentioned now adopting
a first principal mindset means you
concentrate on the Y behind each service
let's take serverless functions as an
example what's the problem well
traditional servers require you to set
aside resources that might go unused
leading to inefficiency and unnecessary
costs why does this problem exist well
because full-time servers waste energy
rack up high bills and need ongoing
maintenance especially during low
traffic how does this service solve this
problem well servess functions let you
run code on demand scaling automatically
when traffic spikes this eliminates idle
resources and shifts much of the
operational work to the cloud provider
like AWS Now by sticking to these
fundamentals and adopting a first
principal's mindset you can evaluate any
new service using this criteria what's
the problem why does it exist and how
does this service solve it so you become
a first principles engineer secret
number three learn by doing no matter
how many tutorials you watch there comes
a point where you simply have to roll up
your sleeves and build something I used
to spend hours watching YouTube
tutorials and following along with demos
thinking that I was on my way to
becoming a cloud engineer but here is
the brutal truth I was coping when the
time came to deploy a real application
or troubleshoot an actual issue I got
stuck and I didn't know where to begin
this happens because Hands-On practical
experience teaches you far more about
real life projects than any video you
watch The Learning only happens when you
apply what you know and build projects
not when you are watching tutorial
videos of someone else doing it and no
you don't have to build the next chat
gbt start very small deploy static
website spin up a virtual machine or a
basic database once you've done the
basics you want to link your projects
together host a small web application or
your virtual machine connect it to your
new database and store logs or upload
images into object storage and if you're
eager to build projects and you're still
finding it hard then you should know
that I am running a special cohort right
now and we're taking on new students for
my cloud engineer Academy look if you're
working in Tech like mac who after
joined my Academy landed a six-figure
job as a systems Eng at AWS maybe you're
in cyber security and you know you need
Cloud skills to keep up with your role
to be honest you could even have a non-
tech related career but you're ready to
take action just like Jay Martinez who
was laid off and got Cloud hired in just
a few months if you fall into any of
these categories then click the link in
the description to book a call with my
team but just know this isn't for
everyone because it's simply not
possible for us to bring on you know 50
100 200 people at once because we simply
don't have the capacity for it so spots
are actually very Li limited so if
you're serious about starting your Cloud
Journey today click the link below book
a call with my team and see how we can
help you the fourth secret often
triggers people when I say it you don't
need four five six Cloud certifications
to land a job certifications do hold a
little bit of value especially early in
your career or if you're changing fields
and need a structured learning path but
here is the Trap many beginners fall
into chasing certifications without ever
gaining significant hands-on experience
and even worse they get into their own
head that they must get CER before they
can even start building or applying for
jobs and that's the completely wrong way
to go about it think about these two
candidates for a cloud engineering role
candidate a has five different
certifications foundational associate
professional speciality on their
LinkedIn candidate B has one
foundational certification but also has
built fre working projects each one
showcasing key skills like deploying
cicd pipelines writing infrastructures
code and integrating for data analytics
who's more likely to land a job well
it's obviously candidate B they've
actually built real projects that matter
and also debugs along the way now
candidate a might have spent free 400
hours studying for exams memorizing best
practices and quiz questions but never
touch an actual production environment
or build anything of value now this
doesn't mean that certifications are
worthless having at least one
foundational or an associate
certification shows you understand the
fundamentals of Any Given cloud provider
it can also help you pass initial HR
screenings and demonstrate your
initiative but the thing is in
interviews you'll get asked questions
like can you walk me through how you
built X or how you did y to fix this
issue if all you've done is memorize
Theory you're never Landing your first
job secret number five is that you need
to adopt a business mindset this
separates Junior Cloud Engineers from
the pros it's easy to focus on the
technical details and while those do
matter they are just a means to an end
the real value comes when you connect
your technical decisions to business
outcomes like cost savings B user
experience or faster time to market for
example let's say your team is tasked
with deploying a new e-commerce platform
a junior Cloud engineer might focus on
how many servers or instances are needed
to handle the traffic which tool to use
for managing multiple Services the exact
rules for scaling during peak hours now
a senior engineer with a business
mindset would explain how a certain load
balancing strategy will keep the site
online during big sales so preventing
loss Revenue The Chosen service
architecture which helps release new
features twice as fast and how
autoscaling saves money by turning off
unused resources when traffic is low now
why does this all matter well because
Executives and shareholders only care
about results and not the tools that you
use if you can translate your technical
blueprint into real numbers you'll be
viewed not just as an implementor but as
a strategic partner that's the kind of
thinking that leads to raises promotions
and Leadership roles and if you're
wondering how do you even adopt this
business mindset the key is to practice
your technical decisions to business
impact and here's a simple three-step
framework that I use for my clients
firstly identify the business problem
ask yourself what problem does this
solve for the business for example maybe
the problem is losing customers during
peak hours because of slow loading times
secondly tie it to financial outcomes
consider how your solution will save or
generate money a more stable platform
that handles traffic spikes could
increase sales and improve brand
reputation and finally focus on customer
experience think about how your solution
reduces friction for users faster low
times and smoother interactions will
lead to better reviews higher customer
satisfaction and repeat purchases that
said these five Secrets aren't enough
you need to know everything that it
takes to become a cloud engineer in
20125 which is why I've created this
step-by-step road map that anyone can
follow so just click right here and
watch the video to make sure that you
don't fall behind
Click on any text or timestamp to jump to that moment in the video
Share:
Most transcripts ready in under 5 seconds
One-Click Copy125+ LanguagesSearch ContentJump to Timestamps
Paste YouTube URL
Enter any YouTube video link to get the full transcript
Transcript Extraction Form
Most transcripts ready in under 5 seconds
Get Our Chrome Extension
Get transcripts instantly without leaving YouTube. Install our Chrome extension for one-click access to any video's transcript directly on the watch page.
Works with YouTube, Coursera, Udemy and more educational platforms
Get Instant Transcripts: Just Edit the Domain in Your Address Bar!
YouTube
←
→
↻
https://www.youtube.com/watch?v=UF8uR6Z6KLc
YoutubeToText
←
→
↻
https://youtubetotext.net/watch?v=UF8uR6Z6KLc