Amazon Virtual Private Cloud Reviews

Compared to that of on-premises solutions, the performance of Amazon Virtual Private Cloud is much better.

Billing and technical support should be better.

There is a steep learning curve as well.

I've been using this solution for about three years. We are migrating all of our critical production applications, management information systems, and legacy on-premises applications to this solution. We have 80,000 to 90,000 users at any point in time.

Amazon Virtual Private Cloud has been stable after we resolved some of the issues during deployment.

Amazon's technical support has not been very helpful. I was left to figure things out on my own. Therefore, I would rate technical support at four on a scale from one to ten.

Neutral

I had to figure out the initial setup myself. The documentation is available, but technical support was not helpful. There was a lot of trial and error.

I have handled the maintenance of the solution myself. However, for proper maintenance, backups, backup tools, and CDNs, I would prefer a service that's not native AWS.

Amazon is not very transparent with pricing. It's quite complicated to see where you're spending and how you can track it. I was spending $30,000 a year and $3600 monthly on top of that initial payment. However, I have been able to bring the cost down for this year.

This is not a solution for large production environments that are implementing it for the first time. It is not very user-friendly, and there is a lot of documentation that you have to take the time to go through.

However, having the features hosted on AWS is so much better than having them on-premises. Therefore, compared to on-premises solutions but not Azure or GCP I would rate Amazon Virtual Private Cloud at nine 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.

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.

Amazon Virtual Private Cloud gives you security. If you put something inside Virtual Private Cloud, then you can add rules to that Virtual Private Cloud, and allow connections from IP addresses and allow connections to an IP address. The inbound and outbound connections can be limited based on IP address. Thereby it adds security. It's a feature of security groups, but that is another AWS service. We put a resource inside a Virtual Private Cloud and then connect a security group to that Virtual Private Cloud, in which we define the traffic rules. In the aforementioned manner, we can limit the IP address that we connect to, so it adds to security.

There is some difference between the route tables of public and private subnets, which is something that is not properly documented. Basically, if you add a route to an Internet Gateway in the private subnet's route table, then it should be able to connect to the Internet. But this doesn't happen. You have to use a NAT gateway instead.

I have been using Amazon Virtual Private Cloud for more than one year.

It is a very stable product.

The solution is used by only two people in my company. It is a very scalable solution.

We never had any issues with this tool.

The initial setup is easy. It is easier now, actually, since they have changed their UI.

There is no way for you to not use it. If you are using EFS or EC2, then you have to use Virtual Private Cloud. There might be other services too, but these are the two I can remember now. Also, it is safer to put things inside of Virtual Private Cloud because it is more secure. I would advise you to do it, but you have to configure it correctly. If it is not needed, then don't use it.

When I tried to modify the route table of a private subnet, it didn't become a public subnet.

I rate the overall 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. 

We use the solution to create virtual private networks for our customers. We use it for connectivity and traffic control. We also use subnets.

The solution enables us to provide a private cloud for our customers. The solution is secure. We use it for the security purposes. We can do networking and create routes. Subnetting is good for security purposes. We can add inbound and outbound groups. We can allow the traffic. We can decide whether to allow inbound or outbound traffic according to the customers’ needs.

If something needs to be highlighted, peering must be maintained.

I have been using the solution for the past two years.

I haven’t had any bugs or breakdown issues. I rate the stability an eight out of ten.

The support is good.

The deployment is easy. The UI is user-friendly.

I will recommend the product to others. People can use the tool as a secure private network for their systems. Overall, I rate the product an eight out of ten.

We use Amazon VPC primarily for our organization's security needs. It helps us maintain isolation and control over our cloud services, similar to our Microsoft cloud service. We use it to communicate with our analytics securely and easily.

The main feature I like about Amazon VPC is its security capabilities, including security groups and subnets. It is easy to implement and manage our systems within specific subnets. Additionally, using Terraform for management tasks simplifies the process, and VPC's provision of basic details makes managing the infrastructure straightforward.

In terms of VPC itself, I haven't encountered any major areas for improvement. However, one concern is the cost, which can be relatively high compared to other cloud providers like Azure and Google Cloud. This can sometimes lead to considerations of switching to a different provider for cost optimization.

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

I would rate the stability of the solution as a ten out of ten.

VPC's scalability is excellent because there are no limitations on deploying VPCs. I would rate the scalability as a ten out of ten.

I haven't encountered any issues with Amazon's technical support team. I would rate them as a nine out of ten.

Positive

Setting up a network in Amazon VPC is straightforward and beginner-friendly. Deployment took about ten minutes. The user interface is easy to navigate, and Amazon provides comprehensive guidelines and resources to help users understand the setup process. Additionally, updates and new features are regularly provided.

We use Amazon VPC to scale our resources efficiently. We employ horizontal auto-scaling with auto-scaling groups to automatically adjust capacity based on fluctuations in traffic. By setting scaling policies and planning ahead, we ensure seamless resource allocation as traffic increases or decreases. While we primarily use horizontal scaling, we also consider vertical scaling when necessary.

Integrating VPC with other AWS services is seamless and essential for most AWS deployments. Whenever we create resources in Amazon, such as EC2 instances or Auto Scaling Groups, we rely on VPC to provide the necessary networking configuration, like IP address ranges and subnets. This integration simplifies the setup process and is easy to understand and manage.

I would recommend Amazon VPC, but it is essential to consider the cost compared to other cloud services like Azure and Google Cloud. For those using VPC for the first time, understand basic networking concepts like IP addressing and subnetting, prioritize security measures, and plan your VPC deployment based on your specific requirements.

Overall, I would rate Amazon VPC as a ten 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 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.