How to Create and Configure a VPC in Thalassa Cloud
This guide walks you through creating and configuring a Virtual Private Cloud (VPC) in Thalassa Cloud with internet access. You’ll learn how to set up a secure network environment for your applications.
A Virtual Private Cloud (VPC) provides a logically isolated network where you can launch and manage your resources securely. This guide covers:
- Creating a VPC
- Setting up subnets
- Configuring internet access
- Managing routing
Creating a VPC
- Navigate to the VPC section in the Thalassa Cloud Console
- Click “Create VPC”
- Configure the VPC:
- Name: Choose a descriptive name
- CIDR Block: Select a CIDR range (e.g.,
10.0.0.0/16
) - Region: Choose your preferred region
- Enable Internet Access: Check this option for public internet access
Note: Choose a CIDR block that’s large enough for your future subnet needs. A
/16
block gives you 65,536 IP addresses.
Configuring Subnets
Create subnets based on your application’s needs:
- Create a subnet in your VPC
- Choose a CIDR block (e.g.,
10.0.1.0/24
) - Name your subnet based on its intended role (e.g., “web”, “app”, “database”)
- Repeat for additional subnets as needed
Note: Subnet names are used to indicate their role in your architecture. For example, you might name subnets “web”, “app”, or “database” to reflect their purpose.
Setting Up Internet Access
For Subnets
Create a NAT Gateway:
- Select a subnet for the NAT Gateway
- Allocate a public IP
- Create the NAT Gateway
Configure routing:
- Go to the route table for your subnet
- Add a route:
0.0.0.0/0
→ NAT Gateway - This allows outbound internet access while keeping resources private
Best Practices
Network Planning
- Use separate subnets for different tiers (web, app, database)
- Plan CIDR ranges to avoid overlap
- Consider future growth when choosing CIDR blocks
Security
- Use security groups to control traffic
- Regularly review and update security rules
- Implement least privilege access
Cost Optimization
- NAT Gateways incur costs, so plan their placement
- Consider using multiple NAT Gateways for additional high availability
- Monitor network traffic and costs
Example Architecture
VPC (10.0.0.0/16)
├── Web Subnet (10.0.1.0/24)
│ ├── NAT Gateway
│ └── Load Balancers
└── App Subnet (10.0.2.0/24)
├── Application Servers
└── Databases
Next Steps
Troubleshooting
Common issues and solutions:
Internet Access Issues
- Verify NAT Gateway is running
- Check route table configurations
- Ensure security groups allow required traffic
Subnet Connectivity
- Confirm CIDR ranges don’t overlap
- Verify route table associations
- Check security group rules
NAT Gateway Problems
- Ensure public IP is allocated
- Verify NAT Gateway is in the correct subnet
- Check route table configurations
For additional help, contact Thalassa Cloud support.