AWS vs Azure vs Google Cloud: How Beginners Should Choose
Compare learning access and project needs without assuming a universal winner.
Part of the Cloud Computing track: modules, projects and first roles →
By the GullyMentor team · 5 min read · Published 2026-10-18 · Updated 2026-11-06 · Sources listed at the end. Not a promise about mentorship outcomes.
Choose one cloud platform that lets you practise the fundamentals with reliable guidance and a manageable budget. There is no universal best choice for every beginner. The skills that matter, such as compute, storage, networking and identity, carry across all three, so finishing one small project matters more than the first pick.
How do the platforms compare for a learner?
| Dimension | AWS | Azure | Google Cloud |
|---|---|---|---|
| Starting concepts | Compute, storage, networking and identity | Compute, storage, networking and identity | Compute, storage, networking and identity |
| Useful context | Projects or teams using AWS services | Projects or teams using Microsoft and Azure services | Projects or teams using Google Cloud services |
| What to check | Account eligibility, service pricing and region | Subscription access, pricing and region | Billing account, project access and region |
| Portfolio goal | A documented, secure small environment | A documented, secure small environment | A documented, secure small environment |
The service interfaces and permission models differ. Familiarity with one platform helps you ask better questions on another, but does not remove the need to learn its details.
How do you decide step by step?
1. Write your constraints: laptop, budget, whether you can use a payment method for account verification, and who can help you. 2. Check what your college lab, workplace or mentor already supports. Existing support removes setup friction. 3. Look at five job descriptions or team pages for roles you want and note which platforms they mention. Treat this as a hint, not a rule. 4. Read the official getting-started documentation for your top two choices, such as the Google Cloud overview, and see which feels clearer to you. 5. Pick one and commit to a single small project.
Use a small decision exercise
Choose a fictional static website with no private data. For each platform, identify a suitable hosting option, how access is controlled, how costs are estimated and how the resources are removed.
Compare the clarity of available documentation and the support you can access. If your mentor or college lab already supports one platform, that can reduce setup friction.
Consider role context
Inspect actual responsibilities in roles you are considering. A specific platform may be relevant to a target team, but learning only product names will not prepare you to troubleshoot.
Working professionals moving from a Windows or Microsoft-heavy workplace may find an existing connection to one platform. Students with no constraint can choose by documentation quality and budget.
Avoid choosing solely from claims that one platform guarantees better salaries or employment. Your ability to explain infrastructure and operate it responsibly matters.
Budget carefully
Pricing, trial credits and free allowances change. Check official pages before creating resources. Alerts are not necessarily hard spending caps; see AWS Budgets for how cost monitoring is described. Stop and remove the environment after practice, then inspect retained resources.
What are the common mistakes?
- Switching platforms every week and finishing nothing.
- Starting a paid resource without a budget alert or a teardown plan.
- Collecting certificates before building anything.
- Assuming skills do not transfer between platforms.
- Using a shared or employer account without permission.
How do you check you got it?
After your first project, redraw the same architecture on one other platform without building it. List which service names change and which concepts stay identical. If most of your list is naming differences, you learned concepts, not just one console.
Recommendation
If you have no strong constraint, pick the platform with the clearest supported learning path available to you and finish one small project. Afterward, redraw the same architecture for another platform and identify what changes.
Worked scenario: two students, two choices
A final-year student in a college where the lab provides a shared Azure subscription chooses Azure, because access, guidance and a mentor are already there. A working tester in a company that runs its test environments on AWS chooses AWS, because she can read her team's real architecture and ask colleagues questions.
Neither chose from a ranking. Both chose by access and support, then built one small documented environment. Six months later, either can read the other platform's documentation and map the concepts across.
What should you build next?
Follow the Cloud Computing Roadmap for the order of topics, and learn the four core layers in Cloud Compute, Storage, Networking and IAM Explained. The Cloud Computing track covers the wider path.
This comparison concerns educational platform choice; it does not establish which tools or account costs are included in a GullyMentor programme.
Sources & further reading
Examples and practice recommendations are educational illustrations. Tool documentation and programme inclusions should be checked for your intended use.