Amazon Virtual Private Cloud Reviews

We use VPC to create a virtual private network. They provide the IP address of each system on each mission. We can configure public and private subnets and modify the configuration of IP addresses for other VPN tunnels. We can also manage network subnets and other related resources with VPC.

We pay for AWS services as we go. Whatever we need, we can get it directly from Amazon without having to release it. This is sufficient for our needs.

I have been using Amazon Virtual Private Cloud for four years.

The product is stable.

The solution’s scalability is good.

We have 15+ accounts set up for VPC. We are managing the entire VPC setup.

The initial setup is not too much difficult. If you know very well about the network configuration setup, we can directly configure it.

VPC is a chargeable service. If you configure it incorrectly, you may be charged for unnecessary resources. Therefore, it is essential to understand the different VPC configurations before making any changes. VPC can be challenging to setup for someone new.

Amazon VPC pricing is based on the data transferred to your VPC. The cost varies depending on the specific resources we are using, such as instances and RDS databases. We have multiple AWS accounts, each paying around $400-500 monthly for VPCs. We have completed a lot of things in use because there is another configuration. If you don't want to do anything, the chargeable rate will apply. The configuration setup is very minimal, which means that the VPC pricing level is very good.

Many things are available in VPC. I don't know everything about VPC, so I must learn more first.

We have many things in VPC. Before setting up a configuration, we need the network thing. So, we are using the VPC. We are using private IP addresses because we need to arrange for multiple servers to be on the same network.

If you are configuring anything at a major level, you should use it. You should assign your IP address. Imagine you will be providing the default IP address, but it's not secure. You should consider your IP within your region.

If you go with the cloud, you should be able to network things.

Overall, I rate the solution a ten out of ten.

VPC is basically about networking and how you are setting up the networks.

VPC, or Virtual Private Cloud, is like a secure portion of AWS's public cloud. So, if you want to secure your dedicated network areas, we use VPCs. Traffic should be slow, and no unwanted people should enter your network, especially because we work at an enterprise level. That is why we must be thoughtful and careful about using VPCs.

We use VPC as a service provided by AWS. So, Amazon keeps enhancing the product.  

In Amazon VPC, there's a service called VPC Peering, where we can connect multiple VPCs from different accounts. However, AWS also introduced new tools like Transit Gateway, based on the Hub and Spoke model. At a single hub, you can route from multiple locations, and that is more efficient. So, this is how it goes.

The subnetting feature has impacted our network design. So, subnetting is very, very important and crucial when it comes to your infrastructure design and presentation. 

Subnetting is completely crucial. For example, suppose I'm an enterprise customer. I have to be very thoughtful and decide, like, "Okay, how many route tables am I going to have?" Let's say you are company XYZ, and you want to make sure that, out of one million IP addresses, let's say, 50,000 should be on a round table. Also, 50,000 IP addresses should go to external ones, and the rest should be for internal use only. Like, you have other third-party software that you have hosted as an enterprise customer. 

In this case, subnetting plays a vital role. You have to be thoughtful, like, "Okay, are you going to use 32 bits? How many IPs do you want to use?" And you have to be very thoughtful about choosing the application. For example, in Kubernetes, we are very thoughtful about using the IPs. They can easily exhaust the IPs. So we have to be very thoughtful about that. So,  subnet skills play a very vital role.

It's all about networking. So VPC, VPC peering, and those features. That's all about the networking aspect of VPC. I like it. 

For network security, Network Access Control Lists (NACLs). They work very well. For example, instead of leaving a resource open to the world with something like 0.0.0.0/0, we can use NACLs to be much more specific with our network traffic rules. It adds an important security layer to our infrastructure.

There is always room for improvement. It can be in support. 

I've been using it for more than three years. 

The stability of VPC itself is incredibly high. AWS guarantees 99.9999999% uptime; it's super reliable.

VPC is not about scaling up the world; it's about securing the infrastructure. For example, you start in AWS by creating an EC2 instance to deploy infrastructure for an application, which is good. 

But maybe not today or tomorrow, but in a year, you'll need to ensure security. Since you work in enterprise scenarios, you have to be very thoughtful. 

Whatever system you create on the cloud, the type of VPC we use will ensure that the infrastructure I create is accessible only by my team members and not by the outside world. We use a NAT gateway for part of the private cloud, which adds a lot of complexities to the model.

So, scaling up or down is handled by Auto Scaling groups and launch templates.

My company and the enterprise clients I work with all use it.  

I ran into some issues. I created a support ticket with AWS, and they set up a call with me on AWS Chime. Their networking architect helped me troubleshoot the errors. They were really helpful.

Positive

I use many tools, like infrastructure services, software services, and Platform as a Service. As a DevOps engineer, I have touched base with all the services. 

Starting from the basic ones like EC2, VPC, subnets, to Lambda functions, API gateways, CloudWatch, AWS Glue, Athena, SageMaker, DynamoDB—all these things I have used.

If you have knowledge of network ACLs and security groups, then you can easily set up network ACLs and security groups in VPC. 

In layman's terms: think of a security group as the front door of an EC2 instance. It controls what comes in and goes out of your EC2. A NACL is like security at the subnet level – it controls what can enter your subnet via the NACL. So, security groups are on EC2 instances, NACLs are on subnets.

The process of integrating VPC with other AWS services is easy and seamless. That's the beauty of AWS – the services are tightly integrated within the AWS console. You can switch between them easily and do what you need. You can manage it directly from the console or automate it with Terraform, it's up to you.

The pricing depends on usage. 

I would definitely recommend using it. If you're working at an enterprise level, or even if you're a startup building software or a website, and you want to ensure security and long-term stability, then absolutely use VPC and configure your network carefully.

Overall, I would rate the solution a nine out of ten. There is always room for improvement. 

The solution is being used as a VPN. 

This solution provides us with a lot of performance-conducive and effective accelerators, which we can use to enter the marketplace as well.

It is an user-friendly solution.

The solution has to be more robust and scalable. 

I have been using Amazon Virtual Private Cloud for seven to eight years. 

The stability of the solution is good. 

The scalability needs improvement. It is mostly an enterprise solution.  I rate the scalability a seven out of ten. 

The technical support team is helpful. 

Positive

The initial setup is straightforward. It takes a few days to get deployed. 

The solution is reasonably priced. 

I would say it's one of the leading tools in the space to provide cloud services. The team is quite responsive as well. I rate the overall solution an eight out of ten. 

We have to install and configure AWS resources with the solution. 

Amazon Virtual Private Cloud isolates networks and offers robust network security. It also adds two network security layers. 

The solution has separate subnets and routing tables.  

The performance insights and VPC flow logs should be in the form of GUI or dashboards. The solution needs to work on integration with the transit gateway and multiple accounts. 

I have been using the tool since 2016. 

I rate the product's stability a nine out of ten. 

I rate Amazon Virtual Private Cloud's scalability a nine out of ten. 

Amazon Virtual Private Cloud has good engineers. 

Positive

Amazon Virtual Private Cloud's deployment is straightforward. 

We have seen ROI with the solution's use. 

The solution is pricey but worth its money. 

It would be best to have a proper architecture before setting up Amazon Virtual Private Cloud. You must discuss beforehand whether you will have a single-VPC or multi-VPC environment. It will stand as a pillar for future needs and growth. Therefore, planning and documentation is very critical. I rate it a ten out of ten. 

The solution can be used to isolate a cloud within a cloud infrastructure. It allows us to have an isolated or air-gapped environment.

The product can be used to isolate environments. It's good for security. It is a very good feature irrespective of which cloud provider we use. It also allows us to connect two VPCs in different zones. We haven’t had any issues with the solution. It satisfies all our requirements.

The tool is not scalable.

I have been using the solution for around three years.

The tool is stable.

The number of users depends on each project. We might have three to four people from DevOps and more than 100 users from the project teams.

The initial setup is very easy and quick.

The solution is worth the money.

The pricing is okay. The solution is not very expensive. Compared to other solutions, it is fine.

The tool is used for the isolation of our environment. It is a set of rules within our cloud environment to separate whatever we have created as a virtual cloud. I highly recommend the solution. Overall, I rate the solution a ten out of ten.

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.

The product’s firewall is very good. It is a very strong tool. The solution works without any issues with other AWS services.

The initial setup is complex. We need to configure each link, check that it's connected, and virtualize it. The complexity is in the preparation to implement the configuration inside the cloud. It takes a lot of time to migrate the configuration from the physical to the virtual network.

I have been using the solution for three to four months.

The product is stable.

The product is scalable. The solution is suitable for small, medium, and large companies.

The technical support is very good. The team is responsive and always gives us the optimal solution.

Positive

We use some tests and check configurations to deploy the solution.

We can use the tool for free. However, there is a cost associated with traffic outside the cloud. We do not have to pay for an extra license for the product.

I recommend the solution to our customers. We use the solution because our customer uses AWS, and they want to use a native AWS solution. People who want to implement the tool must implement it in the right way and check with support regarding the recommended actions. Overall, I rate the product an eight out of ten.

Amazon Virtual Private Cloud is the heart of the application, and we use it for our private network.

The solution's subnetting feature is good and has impacted our network design. We can create multiple machines with subnetting services. We can divide the CIDR with the help of subnets. It provides security, and we can create subnets in public and private.

When we create instances without public IP, the paid services provided by the solution, NAT gateway, are costly.

I have been using Amazon Virtual Private Cloud for three years.

I rate the solution a nine out of ten for stability.

Around 50 users are using the solution in our organization.

I rate the solution’s scalability a nine out of ten.

The solution’s initial setup is easy.

It takes two or three hours to deploy Amazon Virtual Private Cloud.

In our environment, we have public and private infrastructure. The public front-end applications are directly accessible to the client. In a private network, we use database machines, like RDS machines.

It's easy to set up security groups in the new versions of Amazon Virtual Private Cloud. AWS also provides options to create subnets with the solution. I would recommend the solution to other users. A client using AWS needs to create an Amazon Virtual Private Cloud.

Overall, I rate the solution a nine out of ten.

The tool helps to deploy on AWS. As a company, you may want to deploy or migrate your services from a data center to AWS. 

You can get a direct link to AWS to your data even if you are a large organization with a huge data center. 

The tool needs to improve its stability and support which should be faster. The product's pricing is also expensive. When we scale up, we have to pay more. 

I am using the product since 2018. 

I would rate the solution's stability a seven out of ten. 

I would rate the product's scalability a five out of ten. My company has 20 users for the solution. We use the solution on a daily basis. 

The tool's setup is easy and I would rate it a nine out of ten. It's easy to setup and onboard to AWS. However, you would need technical knowledge to troubleshoot. The tool's deployment took one to two weeks to complete. We first conducted a cost-benefit analysis and presented it to the management. Once it was approved, it had a look at the service offerings from AWS and worked on the design based on the AWS architecture framework. We used the Lambda function for the deployment and Terraform to automate the process. We had a five-member deployment team that consisted of demo guys, solution architects, DevOps solution architects, etc. I supervised the overall deployment. 

AWS offers 100 percent ROI for a startup. 

I would rate the solution's pricing a six out of ten. 

I have evaluated Azure where the approach and terminologies is very different from AWS. 

I would rate the product a seven out of ten. You need to sit down with your stakeholder and identify the advantages of migrating to AWS. You need to conduct an analysis on whether you really need to migrate to AWS. You need to be also aware that when the number of services deployed on the cloud increases, the cost also increases.