🦈 Hello Storage Sharks!

May all your files get accommodated in S3 and your bucket be filled forever! 🪣📁

📚 All code, docs, and resources are available in my GitHub repository:

🗂️ Working with AWS S3 Cloud Storage Services 💾

Madhurima Rawat ・ Apr 4

#tutorial #cloudcomputing #aws #s3

we explored AWS S3, understanding how to create buckets, upload files, and access files.

Now, let’s move on to the next exciting chapter: Cloud Networking and Configuration! 🌐🛠️

We’ll start by breaking down what cloud networking really means — how resources interact, how traffic flows, and how configurations like security groups, subnets, and VPCs come into play. Then we’ll dive straight into hands-on examples to set up and configure networking for your cloud environment.

Stay tuned — we’re about to get connected in the cloud! 🚀🌩️

1. Overview of Virtual Private Cloud (VPC)

A VPC is a customizable virtual network within the AWS cloud. It allows you to manage networking resources securely and privately.

• Allows the creation of isolated networks in the cloud.
• Provides control over IP address ranges and routing.
• Enables creating public and private subnets.
• Facilitates secure, private communication between instances.

2. Key Components of a VPC

The VPC is made up of several essential components for creating a robust networking environment:

• Subnets: Segment the network into smaller, manageable sections.
• Internet Gateway (IGW): Provides internet access for public-facing resources.
• Route Tables: Direct traffic within the VPC and between the internet.
• NAT Gateway: Allows private subnet instances to access the internet.
• Security Groups & Network ACLs: Define inbound and outbound traffic permissions for resources.

3. Networking Flow and Communication

The VPC enables seamless communication between instances and secure internet access.

• Public Subnets: These subnets have internet access via an IGW, making them suitable for web servers.
• Private Subnets: Isolated subnets that don't directly connect to the internet; they access the internet via a NAT Gateway.
• Route Tables: Manage the routing of network traffic within the VPC, to/from the internet or between subnets.
• Security Layers: Using Security Groups and Network ACLs to filter traffic and secure resources.

4. LocalStack for VPC Simulation

LocalStack simulates AWS services locally, allowing you to test cloud configurations without needing actual AWS resources.

• Simulates AWS Cloud Services: Enables local testing for cloud networking and services like VPC.
• Supports Full AWS Environment: Includes EC2, S3, VPC, and more.
• Custom Endpoints: Interact with LocalStack through custom endpoint URLs, mimicking real AWS behavior.
• Ideal for Development and Testing: Provides a cost-effective solution for developers to test network setups.

5. Use Cases of VPCs

VPCs can be used for various networking purposes to create secure, scalable architectures.

• Web Hosting: Deploy secure web applications with public-facing and private backends.
• Hybrid Cloud: Extend on-premise networks into the cloud via VPN or Direct Connect.
• Big Data & Machine Learning: Isolate workloads for processing and analysis.
• Multi-Tier Architectures: Separate frontend, application, and database tiers for better security.

🖥️ All Components of a VPC Implemented in LocalStack

LocalStack is a local AWS cloud emulator that allows developers to create and test AWS services, including Virtual Private Cloud (VPC), on their local machines.

🌐 1. Virtual Private Cloud (VPC)

• Definition: A logically isolated network where cloud resources like EC2 instances, databases, and load balancers are deployed.
• Key Attributes:
  • VPC ID: Unique identifier (e.g., vpc-12345678).
  • CIDR Block: Defines the IP range for the VPC (e.g., 10.0.0.0/16).
  • Default vs. Custom VPC:
  • Default VPC: Automatically provided by AWS.
  • Custom VPC: User-defined network configuration.

🛠️ CIDR (Classless Inter-Domain Routing) & CIDR Block Explained

CIDR stands for Classless Inter-Domain Routing, a method used to allocate IP addresses efficiently and manage network traffic. It replaces the traditional class-based addressing (Class A, B, C) with a more flexible prefix-based system.

📌 What is a CIDR Block?

A CIDR block defines a range of IP addresses that can be used within a network, such as a VPC or Subnet. It consists of:

1. Base IP Address → The starting point of the network (e.g., 192.168.1.0).
2. Subnet Mask (Slash Notation /X) → Determines how many IPs are in the range.

🔢 How CIDR Works (Subnet Mask & IP Ranges)

• CIDR notation looks like:

192.168.1.0/24

• 192.168.1.0 → Base IP Address

• /24 → Subnet Mask (Means first 24 bits are fixed for network, remaining bits for hosts)

  • IP Address Calculation:

• /24 allows 256 total IPs (2^(32-24) = 256), but usable IPs are 254 because:

  • 1st IP (192.168.1.0) → Network Address
  • Last IP (192.168.1.255) → Broadcast Address

📊 Common CIDR Blocks & Their Usages

📌 Real-World Example

🏢 Company Network Setup in LocalStack

• A company wants two separate environments:
  1. Public Subnet for web servers → 192.168.1.0/24
  2. Private Subnet for databases → 192.168.2.0/24
• The VPC is created in LocalStack, ensuring a controlled environment where services can be tested without real AWS costs.

🌟 Summary

• CIDR Block defines IP ranges within a network (VPC, Subnet).
• The suffix (/X) determines subnet size, affecting the number of IPs.

• Real-world usage: Efficiently dividing networks for different applications (web, database, internal services, etc.).

• 📌 Real-World Example:

  • A company needs a private network for its applications.
  • The VPC is created in LocalStack with 192.168.1.0/24 as the IP range, ensuring complete control over networking and security.

📌 2. Subnet (Public & Private)

• Definition: A segment of the VPC that organizes resources and determines how IPs are assigned.
• Key Attributes:
  • Subnet ID: Unique identifier (e.g., subnet-98765432).
  • CIDR Block: The subnet's IP range (e.g., 10.0.1.0/24).
  • Types of Subnets:
  • 🌍 Public Subnet: Connected to the Internet Gateway for external access.
  • 🔒 Private Subnet: No direct internet access, used for internal applications.
  • Availability Zone (AZ): Each subnet belongs to a specific AWS Availability Zone (e.g., us-east-1a).
• 📌 Real-World Example:
  • A company hosts a web application with two components:
  • Public Subnet (10.0.1.0/24) → Hosts a web server that users can access.
  • Private Subnet (10.0.2.0/24) → Stores a database that should not be directly exposed to the internet.

🛣️ 3. Route Table

• Definition: A set of rules (routes) that direct traffic within the VPC.
• Key Attributes:
  • Route Table ID: Unique identifier (e.g., rtb-56789).
  • Routes: Define paths for network traffic (e.g., 0.0.0.0/0 → Internet Gateway).
  • Subnet Association: Subnets are linked to a specific route table.
• 📌 Real-World Example:
  • The public subnet is associated with a route table that contains:
  • 0.0.0.0/0 → Internet Gateway (igw-12345), allowing internet access.
  • The private subnet is associated with a route table that contains:
  • 10.0.0.0/16 → Local Traffic, ensuring internal communication only.

🛜 4. Internet Gateway (IGW) & NAT Gateway

• 🌍 Internet Gateway (IGW):
  • Allows resources in the public subnet to connect to the internet.
  • Real-World Example: A web server in a public subnet needs to fetch updates from the internet.
• 🔒 NAT Gateway (for private subnets):
  • Enables outgoing internet traffic from private resources without exposing them to inbound requests.
  • Real-World Example: A backend server in a private subnet needs to download software updates, but should not be directly accessible.

⚡ 5. Security Group (SG) & Network ACL (NACL)

• 🔒 Security Group (SG):
  • Acts as a firewall that controls inbound/outbound traffic at the instance level.
  • Real-World Example: A web server has an SG allowing inbound traffic on port 80 (HTTP) but blocks everything else.
• 📜 Network ACL (NACL):
  • Controls traffic at the subnet level and applies rules in order.
  • Real-World Example: A company sets a rule to block all traffic from a specific IP range to prevent malicious access.

🔗 6. Elastic IP (EIP) & Private IP

• 📍 Elastic IP (EIP):
  • A static public IP assigned to an instance, ensuring it remains the same even after reboot.
  • Real-World Example: A company assigns an EIP to a critical web server to maintain a consistent IP for users.
• 🏠 Private IP:
  • Assigned inside a VPC for internal communication.
  • Real-World Example: A database only allows connections from a specific private IP assigned to an application server.

🎯 7. VPC Peering & VPN Connection

• 🤝 VPC Peering:
  • Connects two VPCs privately without needing an internet connection.
  • Real-World Example: A company connects its production and development environments in different VPCs for seamless data sharing.
• 🛡️ VPN Connection:
  • Connects on-premises networks to AWS securely.
  • Real-World Example: A company uses a VPN to access its AWS resources securely from its office.

🛠️ 8. Load Balancer & Auto Scaling

• ⚖️ Load Balancer (LB):
  • Distributes traffic across multiple instances to improve availability.
  • Real-World Example: A web application with high traffic uses an Elastic Load Balancer (ELB) to route requests efficiently.
• 📈 Auto Scaling:
  • Dynamically adjusts the number of instances based on demand.
  • Real-World Example: An e-commerce website increases server capacity automatically during sales events.

Step-by-Step Guide: Setting Up a VPC in LocalStack

Step 1: Start LocalStack

Start LocalStack using one of the following methods:

Using the CLI

localstack start

Using Docker

docker run --rm -it -p 4566:4566 localstack/localstack

Ensure Docker is Running

• Open Docker Desktop and wait until it displays "Docker is running."
• LocalStack will simulate AWS services on port 4566, allowing local development without needing an actual AWS account.

Step 2: Create a Virtual Private Cloud (VPC)

Create a VPC (Virtual Private Cloud) to define a private network:

aws ec2 create-vpc --cidr-block 10.0.0.0/16
--endpoint-url=%AWS_ENDPOINT_URL%

What This Does:

• Defines a private network (10.0.0.0/16) for AWS resources.
• Returns a VPC ID (e.g., "VpcId": "vpc-123456"), which is required for the next steps.

Step 3: Create a Subnet

A subnet allows instances to communicate within the VPC.

aws ec2 create-subnet --vpc-id vpc-123456
--cidr-block 10.0.1.0/24 --endpoint-url=%AWS_ENDPOINT_URL%

What This Does:

• Creates a smaller network (10.0.1.0/24) within the VPC for organizing resources.
• A Subnet ID (e.g., "SubnetId": "subnet-123456") is returned, which is needed for later steps.

Step 4: Create and Attach an Internet Gateway

An Internet Gateway (IGW) allows resources in the subnet to access the internet.

Create the Internet Gateway:

aws ec2 create-internet-gateway --endpoint-url=%AWS_ENDPOINT_URL%

Attach the Internet Gateway to the VPC:

aws ec2 attach-internet-gateway --internet-gateway-id
igw-123456 --vpc-id vpc-123456 --endpoint-url=%AWS_ENDPOINT_URL%

What This Does:

• Enables instances in the VPC to communicate with the internet.
• Returns an Internet Gateway ID (e.g., "InternetGatewayId": "igw-123456").

Step 5: Configure Routing for Internet Access

To allow traffic to and from the internet, a Route Table must be created and updated.

Create a Route Table for the VPC:

aws ec2 create-route-table --vpc-id vpc-123456
--endpoint-url=%AWS_ENDPOINT_URL%

Add a Default Route to Enable Internet Access:

aws ec2 create-route --route-table-id rtb-123456
--destination-cidr-block 0.0.0.0/0 --gateway-id
igw-123456 --endpoint-url=%AWS_ENDPOINT_URL%

Associate the Route Table with the Subnet:

aws ec2 associate-route-table --route-table-id rtb-123456
--subnet-id subnet-123456 --endpoint-url=%AWS_ENDPOINT_URL%

What This Does:

• Defines a default route (0.0.0.0/0), allowing traffic to flow to the internet.
• Links the route table to the subnet so instances can use the IGW.

Step 6: Verify the Configuration

List All VPCs:

aws ec2 describe-vpcs --endpoint-url=%AWS_ENDPOINT_URL%

List All Subnets:

aws ec2 describe-subnets --endpoint-url=%AWS_ENDPOINT_URL%

What This Does:

• Confirms the VPC and subnets have been successfully created and configured.
• Ensures all components (VPC, subnet, IGW, and routing) are correctly set up.

Useful Resources for Learning about Virtual Private Cloud (VPC)

1. Spiceworks - What is Virtual Private Cloud?

What Is Virtual Private Cloud (VPC)? Definition, Key Components, Best Practices, and Providers - Spiceworks

A virtual private cloud (VPC) is an isolated and secured cloud environment usually created within a public cloud. Click here to understand VPC, its key components, and best practices.

spiceworks.com

A comprehensive guide explaining the concept of Virtual Private Cloud (VPC), its benefits, and how it enhances network security and control over cloud resources.

2. Medium - Deep Dive into Amazon Virtual Private Cloud (VPC)

Amazon VPC: Core Features Explained | Medium

Alexander Obregon ・ Jan 6, 2024 ・

Medium

3. Medium - AWS VPC: Virtual Private Cloud

AWS VPC(Virtual Private Cloud). Amazon Web Services (AWS) Virtual… | by Deepeshjaiswal | Medium

Deepeshjaiswal ・ Feb 19, 2023 ・

Medium

4. Dev.to - A Beginner's Guide to AWS Virtual Private Cloud (VPC) Security

A Beginner's Guide to AWS Virtual Private Cloud (VPC) Security

Sedat SALMAN for AWS Community Builders ・ Mar 20 '23

#aws #cloud #security #vpc

📄 Want to see the output step by step? Check it out here:

🔗 Experiment 4 Output (PDF)

🧠 Want to see the input and output for each command in the Command Prompt along with a clear explanation? Check it out here:

🖥️ Command Prompt Input & Output Explanation (PDF)

🎉 And that’s a wrap! Congrats and kudos—you have successfully configured a cloud network! 🎖️

You’ve now understood the foundations of cloud networking and AWS VPC.

💡 I hope this guide helped you! I know this one was a bit long—but that’s because I was super curious and a little confused myself while exploring so many new concepts. 😅

So, I added lots of detailed explanations to make it easier for anyone else diving into it. Do let me know your thoughts and feedback!

🔥 Stay tuned for the next article!

We’re going to explore the heart of the cloud: Serverless Computing with AWS Lambda — the saviour of developers and servers alike! 🦸‍♂️☁️

It’s going to be super exciting, so make sure to stay connected and drop your comments, questions, or even your own cool resources!

💬 Did you like this guide?

Leave a comment if it helped, share your favorite cloud networking diagrams, or anything else you found useful!

Let’s continue exploring the cloud—one byte at a time! 🌟💛