Pebellslearn by building
0%
RoadmapsMatrixCoursesSandboxSign in
Introduction to the Cloud and AWS  ›  Lesson

Public, Private and Hybrid Cloud

Public vs Private vs Hybrid Cloud 12 minDeployment models describe who owns and uses the cloud: public clouds are shared provider fleets, private clouds serve one organisation, and hybrid clouds connect the two.

Public, Private and Hybrid Cloud

Inkwell happily moves its shop website to AWS. Its sister company, a small publisher, is not so sure: a contract says unpublished manuscripts must stay on machines the publisher controls. Does that rule out the cloud? Not necessarily. It depends on which deployment model you pick: the question of where the cloud lives and who shares it.

The rule

Public is shared, private is yours alone, hybrid joins the two.

  • Public cloud. A provider such as AWS runs a vast fleet and rents it to anyone. Customers share the physical hardware but are isolated from each other in software. You get huge scale, many services and no hardware to buy.
  • Private cloud. Cloud-style self-service and automation, but used by only one organisation. It usually runs in your own data centre, sometimes in a hosting provider's building on hardware reserved for you. You get full control, and you pay for all of the hardware and the staff who run it.
  • Hybrid cloud. A private environment and a public cloud connected so they work as one system. Sensitive or legacy workloads stay private; bursty or new workloads go public.

AWS supports hybrid designs with secure links such as a site-to-site VPN over the internet or AWS Direct Connect, a dedicated private line, and with AWS Outposts, which puts AWS-managed racks inside your own building.

You will also meet multi-cloud: using more than one public provider. That is a different axis; hybrid is about mixing private and public.

The shortcut

Ask "Is there anything that must not leave our building?"

  • No → public cloud is the simple default.
  • Yes, and it is everything → private cloud.
  • Yes, but only some of it → hybrid cloud.
The publisher's decisionStep 1 of 4
  1. Must anything stay on-site?

    Yes: manuscripts, because of the contract.

The trap is assuming "private" means "safer" automatically. A private cloud is only as secure as the team that runs it; a small publisher may patch servers less reliably than a large provider. Choose private for a real reason such as a legal rule, not a vague feeling.

Drills

Answer fast — trust the rule.

quick drill

Inkwell runs everything on AWS and owns no servers. Which deployment model is this?

quick drill

A bank keeps customer records in its own data centre and runs its marketing site on AWS, with a link between them. Which model?

quick drill

What is the main trade-off of a private cloud?

quick drill

A startup uses AWS for servers and a second public provider for analytics. What is this called?

Remember

  • Public is shared, private is yours alone, hybrid joins the two.
  • Shortcut: "must anything stay in our building?" No, all, or some.
  • Trap: private is not automatically safer, and multi-cloud is not the same as hybrid.

Practice — level up

0/1 solved

Write your answer, then compare it with a rubric and a model answer.

ExplainChoose a deployment model

Inkwell's sister company, a publisher, must keep manuscripts on machines it controls in its own building for contract reasons, but wants its public website to scale on AWS. Name the deployment model that fits, explain why neither pure public nor pure private cloud works, and name one thing the setup needs to make the two sides work together.