Introduction
In project meetings, I could usually follow the general idea, but I’d often find myself Googling terms later to make sense of what I’d heard. At first, I told myself it was fine. But over time, that knowledge gap started to wear on me. It chipped away at my confidence and made it harder to keep up with conversations the team was having that really mattered.
As a digital project manager, that’s not a great place to be. I started second-guessing whether I was asking the right questions, or worse, missing something important altogether. I didn’t need to become a cloud engineer, but I did need to build enough of a foundation to speak the language, ask better questions, and bridge the gap between technical teams and business goals.
Why I Decided to Learn the Cloud Basics
The issue wasn’t just technical; it was about trust and credibility. When you can’t keep up with the conversation, it’s harder to contribute, and it slows everything down. Misunderstandings increase, meetings stretch longer, and you start to question your instincts when you don’t understand the facts.
That’s what led me to pursue two cloud certifications made for professionals like me, people who work closely with engineers, but don’t come from an engineering background.
I earned both the AWS Certified Cloud Practitioner and CompTIA Cloud Essentials+ certifications. Each brought something unique to the table, and together they gave me the solid footing I needed to show up more confidently and contribute more effectively in cloud-related projects.
What Made These Certifications the Right Fit
There are a ton of cloud certifications out there, but most are geared toward deep technical roles, such as developers, system administrators, and cloud architects. I wasn’t looking to deep-dive into infrastructure or scripting. I simply wanted a clear, business-savvy view of how cloud systems work so I could make smarter decisions and support my team.
Here’s what stood out about each one:
AWS Certified Cloud Practitioner gave me a helpful overview of AWS services, billing models, and shared responsibility concepts. It was a great starting point, but a little too focused on AWS alone. Here’s what stood out:
Service overview that explained key tools that I’ve repeatedly heard, like EC2, S3, CloudWatch, and Lambda in a digestible way.
Cost clarity through a breakdown of pricing models, billing practices, and support tiers.
The shared responsibility model, which describes what AWS handles vs. what you handle.
CompTIA Cloud Essentials+ felt broader and more balanced. It was:
Business-focused, aimed at people like me—project managers, decision-makers, and non-tech professionals.
Foundational, with just enough detail to be useful without being overwhelming.
Vendor-neutral, so I learned core concepts that apply across AWS, Microsoft Azure, Google Cloud, and beyond.
Although my AWS certification has since expired, the knowledge stuck. The principles I learned from both certifications still help me every week on the job.
The Concepts That Stuck (and Still Matter)
Some ideas from those certifications really clicked, and they’ve made a lasting impact on how I lead and collaborate. These are the ones I still come back to in my digital projects, especially when working with operations or support:
- Networking and content delivery: I learned how virtual networks, virtual private clouds (VPCs), subnets, and services like Amazon Route 53 (a domain name system, or DNS) and Amazon CloudFront (a content delivery network, or CDN) help systems stay secure and fast across global environments.
- Cloud storage and databases: Concepts like Amazon S3 (a cloud object storage service), Amazon RDS (a relational database service), and Amazon DynamoDB (a fully managed, serverless NoSQL database) helped me understand how we store, access, and scale data in modern systems, which is crucial when managing digital products or migrations.
- Cloud migration strategies: Knowing terms like “lift and shift” and “rip and replace” made migration conversations make sense. I could finally follow why certain decisions were made and what risks we were balancing.
- Compute options: I learned the basics of Amazon EC2 (Elastic Compute Cloud), which supply users with virtual servers (or instances) in the AWS cloud. They provide scalable and secure computing power. Amazon Lambda, on the other hand, is a serverless compute service that lets you run code without provisioning or managing servers.
In a project I’m leading to analyze the resiliency of an e-commerce platform and its connected components, a few other concepts have stood out as especially helpful:
Resiliency and availability: I learned what redundancy, failover, and multi-zone deployment actually meant, how they relate to SLAs, and why they matter to business continuity.
Backup and recovery strategy: I connected the dots between RTO (Recovery Time Objective), RPO (Recovery Point Objective), and technologies like snapshots and data replication that support them.
Monitoring and alerting: I could follow conversations about performance metrics using tools like Amazon CloudWatch. I also learned about alert thresholds and improving visibility across systems.
🎬 Wrapping It Up
I didn’t walk away from these certifications as a cloud architect, but that was hardly my goal. What I did gain was something far more valuable to me: the vocabulary, confidence, and perspective to navigate cloud conversations and support my team more effectively.
If you’re in project management or in a similar role where you need to understand the basics of cloud architecture and services, you don’t have to code to contribute. You just need a solid enough foundation to connect with the experts around you and guide the conversation between business outcomes and technical solutions.
Note: AWS Certified Cloud Practitioner is a trademark of Amazon Web Services, Inc. CompTIA Cloud Essentials+ is a trademark of the Computing Technology Industry Association (CompTIA). This article is not affiliated with or endorsed by either organization.
💬 Have you taken a cloud certification as a non-engineer? I’d love to hear how it helped you show up differently in your role.
