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