Unitel Group at a comms service provider with 1,001-5,000 employees
Real User
Top 5
Sep 1, 2025
Our main use case for Amazon Virtual Private Cloud is that it is our main network solution. It is mainly used to connect our nodes and also connect our on-premise nodes to the AWS VPC using the site-to-site connection.
CloudOps Expert at a tech vendor with 501-1,000 employees
MSP
Top 20
May 29, 2025
Currently, I am in operations. We have clients that we support with their infrastructure and multi-cloud operations. We use AWS, Azure, and some parts of Google. Mainly we are using EC2, RDS, S3, VPC Network components.
I'm working with EC2 and AWS S3 buckets. I have created an architecture featuring a whole VPC that contains EC2 instances and databases. It is a multi-tier architecture, including components such as security groups handling inbound and outbound traffic. I know where to direct the traffic. I have used AWS Guard, AWS Shield, and more in terms of security. I was creating an application for an events company, and we made a VPC with traditional infrastructure. We built instances connected via load balancers to manage traffic. We created security groups on different instances, including the EC2 instances using m3.large. We used T2.large for databases, managing traffic for a local infrastructure without needing CloudFront. Traffic was directed from portals to EC2 instance servers, and information was stored in the database. We set up lifecycle policies in the database for data retention, moving data to Glacier state when needed using S3 buckets. We transitioned objects from the initial stage to the Glacier stage. Our infrastructure included EC2, a database engine using MySQL, and security measures as described earlier.
I use Amazon VPC because whenever I need to isolate some services or components of the architecture, I start with the VPC. Then, I create some public or private subnets in it.
Learn what your peers think about Amazon Virtual Private Cloud. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
Deputy General Manager at a tech services company with 10,001+ employees
Real User
Top 5
Apr 15, 2024
All our general workloads are being hosted in the AWS public cloud. Our analytics workload is in GCP. We have web servers, application servers, and databases in the general workload. Generally, three-tier architectures are hosted in AWS.
I have been working on various projects including ERP solutions and data projects where we need a robust and versatile environment setup. due to its seamless integration options, network isolation and private endpoints, we found it as the best for our projects.
My company runs multiple services on AWS EKS, and to create a network and communication between such services, we use Amazon Virtual Private Cloud. In general, my company uses the tool for multiple services.
Whenever we launch an instance, it depends on the requirements of the customers. They might use a default VPC. We always recommend that customers or anyone customize the VPC. We'll want to create a VPC with subnets, routes, and an internet gateway. We also use the AWS console, GUI, and CloudFormation to set it up. We can also trigger it from Terraform. Three methods we use.
Based on processing data, we find VPC is very important. Every network is isolated from the outside and private as well. Our plan involves the provisioning of a private network using a VPC. In this process, we will distinctly segregate private and public components. This includes the creation of private subnets and the integration of services such as Amazon RDS. The implementation of databases, be it for work or other purposes, will occur within these private subnets. This configuration is designed to cater to various stakeholders—clients, the public, users, and applications. This architectural approach extends beyond public communication. So communicating could be within applications and via Net Gateway, or we will use some VPC endpoint as well. So this could be an architecture.
Consultant at a computer software company with 5,001-10,000 employees
Consultant
Sep 21, 2023
We use the solution to make network connections between instances, VMs, databases, or other services present in the cloud. We have a connection to both private and public clouds.
We use Amazon Virtual Private Cloud for different requirements. When it comes to building a virtual cloud platform for our infrastructure, my team and I are interested in gateways because they are the foundation of VPCs. This is how you will access the internet or data. Gateways and subnets are the most important features. Subnets help you save network and routing traffic.
You cannot provision an EC2 server or an EFS instance in AWS without putting them inside a Virtual Private Cloud. If the EFS is connected to a Lambda, then the Lambda also has to be inside the same Virtual Private Cloud. By adding inbound rules to the Virtual Private Cloud's Security Group, you can tighten the security of the resources within it.
IT Systems Administrator at a tech services company with 1-10 employees
Real User
May 29, 2022
Amazon VPC's provides a cloud environment that can be private for any company. This means you can have services and servers running in a private environment, isolated from any services on prem. This gives you the capabilities of interconnecting specific services and ports to your internal network. You are able to keep data in a secure environment where no one can access it without being responsible for the power consumption, cooling of hosts or a disaster recovery scenario. You can avoid any destructive situations. We are using a hybrid infrastructure in our own server room, in combination with cloud instances that we replicate in our zone in a secure way. We use encrypted panels from our premises to Amazon, transferring data and storing it safely.
Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can use both IPv4 and IPv6 in your VPC for secure and easy access to resources and applications.
Our main use case for Amazon Virtual Private Cloud is that it is our main network solution. It is mainly used to connect our nodes and also connect our on-premise nodes to the AWS VPC using the site-to-site connection.
Currently, I am in operations. We have clients that we support with their infrastructure and multi-cloud operations. We use AWS, Azure, and some parts of Google. Mainly we are using EC2, RDS, S3, VPC Network components.
The main purpose of Amazon Virtual Private Cloud is to provide a virtual networking environment.
I'm working with EC2 and AWS S3 buckets. I have created an architecture featuring a whole VPC that contains EC2 instances and databases. It is a multi-tier architecture, including components such as security groups handling inbound and outbound traffic. I know where to direct the traffic. I have used AWS Guard, AWS Shield, and more in terms of security. I was creating an application for an events company, and we made a VPC with traditional infrastructure. We built instances connected via load balancers to manage traffic. We created security groups on different instances, including the EC2 instances using m3.large. We used T2.large for databases, managing traffic for a local infrastructure without needing CloudFront. Traffic was directed from portals to EC2 instance servers, and information was stored in the database. We set up lifecycle policies in the database for data retention, moving data to Glacier state when needed using S3 buckets. We transitioned objects from the initial stage to the Glacier stage. Our infrastructure included EC2, a database engine using MySQL, and security measures as described earlier.
I use Amazon VPC because whenever I need to isolate some services or components of the architecture, I start with the VPC. Then, I create some public or private subnets in it.
We use the solution to create virtual private networks for our customers. We use it for connectivity and traffic control. We also use subnets.
All our general workloads are being hosted in the AWS public cloud. Our analytics workload is in GCP. We have web servers, application servers, and databases in the general workload. Generally, three-tier architectures are hosted in AWS.
I have been working on various projects including ERP solutions and data projects where we need a robust and versatile environment setup. due to its seamless integration options, network isolation and private endpoints, we found it as the best for our projects.
My company runs multiple services on AWS EKS, and to create a network and communication between such services, we use Amazon Virtual Private Cloud. In general, my company uses the tool for multiple services.
Our primary use case for Amazon Virtual Private Cloud involves securely hosting our application and database servers within the private data center.
Whenever we launch an instance, it depends on the requirements of the customers. They might use a default VPC. We always recommend that customers or anyone customize the VPC. We'll want to create a VPC with subnets, routes, and an internet gateway. We also use the AWS console, GUI, and CloudFormation to set it up. We can also trigger it from Terraform. Three methods we use.
We use the solution to set up Virtual Private Networks.
The solution is being used as a VPN.
The solution can be used to isolate a cloud within a cloud infrastructure. It allows us to have an isolated or air-gapped environment.
Based on processing data, we find VPC is very important. Every network is isolated from the outside and private as well. Our plan involves the provisioning of a private network using a VPC. In this process, we will distinctly segregate private and public components. This includes the creation of private subnets and the integration of services such as Amazon RDS. The implementation of databases, be it for work or other purposes, will occur within these private subnets. This configuration is designed to cater to various stakeholders—clients, the public, users, and applications. This architectural approach extends beyond public communication. So communicating could be within applications and via Net Gateway, or we will use some VPC endpoint as well. So this could be an architecture.
We use the solution to make network connections between instances, VMs, databases, or other services present in the cloud. We have a connection to both private and public clouds.
We use Amazon Virtual Private Cloud for different requirements. When it comes to building a virtual cloud platform for our infrastructure, my team and I are interested in gateways because they are the foundation of VPCs. This is how you will access the internet or data. Gateways and subnets are the most important features. Subnets help you save network and routing traffic.
We have hosted 400 applications with the help of Amazon Virtual Private Cloud.
You cannot provision an EC2 server or an EFS instance in AWS without putting them inside a Virtual Private Cloud. If the EFS is connected to a Lambda, then the Lambda also has to be inside the same Virtual Private Cloud. By adding inbound rules to the Virtual Private Cloud's Security Group, you can tighten the security of the resources within it.
We use the solution to create virtual instances for our customers' environments.
We use Amazon VPC to host our EC2 instances.
Amazon VPC's provides a cloud environment that can be private for any company. This means you can have services and servers running in a private environment, isolated from any services on prem. This gives you the capabilities of interconnecting specific services and ports to your internal network. You are able to keep data in a secure environment where no one can access it without being responsible for the power consumption, cooling of hosts or a disaster recovery scenario. You can avoid any destructive situations. We are using a hybrid infrastructure in our own server room, in combination with cloud instances that we replicate in our zone in a secure way. We use encrypted panels from our premises to Amazon, transferring data and storing it safely.