Cloud deployment models (public, private, hybrid) in AWS - Commands & Configuration

Introduction

Cloud deployment models describe where and how your computing resources are hosted and managed. They help you choose the best way to run your applications based on your needs for control, security, and cost.

When you want to use shared cloud resources managed by a provider to save costs and scale easily (public cloud).

When you need full control over your infrastructure for sensitive data or compliance reasons (private cloud).

When you want to combine both public and private clouds to balance flexibility and security (hybrid cloud).

When your company must keep some data on-premises but also use cloud services for other workloads.

When you want to gradually move your applications to the cloud without fully leaving your current setup.

Commands

This command lists your current virtual machines in AWS, showing resources in the public cloud you control.

Terminal

aws ec2 describe-instances

Expected Output

Reservations: []

→

--region - Specify the AWS region to query

Creates a private virtual network (VPC) in AWS where you can launch resources isolated from the public internet.

Terminal

aws ec2 create-vpc --cidr-block 10.0.0.0/16

Expected Output

{

    "Vpc": {

        "VpcId": "vpc-0abcd1234efgh5678",

        "State": "pending",

        "CidrBlock": "10.0.0.0/16",

        "IsDefault": false

    }

}

Lists all your private virtual networks (VPCs) to verify your private cloud setup.

Terminal

aws ec2 describe-vpcs

Expected Output

{

  "Vpcs": [

    {

      "VpcId": "vpc-0abcd1234efgh5678",

      "State": "available",

      "CidrBlock": "10.0.0.0/16"

    }

  ]

}

Creates a VPN connection to securely link your private cloud (VPC) with your on-premises network, enabling a hybrid cloud setup.

Terminal

aws ec2 create-vpn-connection --type ipsec.1 --customer-gateway-id cgw-0a1b2c3d4e5f6g7h8 --vpn-gateway-id vgw-0a1b2c3d4e5f6g7h8

Expected Output

{

    "VpnConnection": {

        "VpnConnectionId": "vpn-0a1b2c3d4e5f6g7h8",

        "State": "pending",

        "Type": "ipsec.1"

    }

}

Key Concept

If you remember nothing else from this pattern, remember: public clouds share resources openly, private clouds keep resources isolated, and hybrid clouds connect both for flexibility.

Common Mistakes

Trying to run sensitive workloads directly on public cloud without isolation.

This can expose data to security risks and compliance violations.

Use private clouds or hybrid models with secure connections for sensitive data.

Assuming private cloud means on-premises only.

Private clouds can also be hosted in the cloud provider's data centers but isolated for your use.

Understand private cloud as isolated resources regardless of physical location.

Not setting up VPN or direct connections when using hybrid cloud.

Without secure links, data transfer between clouds can be insecure or impossible.

Always configure VPN or dedicated connections to link private and public clouds.

Summary

Use 'aws ec2 describe-instances' to see your public cloud resources.

Create private clouds with 'aws ec2 create-vpc' and verify with 'aws ec2 describe-vpcs'.

Set up hybrid clouds by creating VPN connections to link private and public environments.