Amazon Virtual Private Cloud Reviews

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.

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. 

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.

The most valuable features of the solution are its security groups and NACL, which allows users to configure the routing tables and other related areas.

The overall integration capabilities of Amazon Virtual Private Cloud with third-party tools need to improve.

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

It is a stable solution. Stability-wise, I rate the solution a nine and a half out of ten.

Scalability-wise, I rate the solution a nine and a half out of ten.

Around 250 people in my company use the product.

Though Amazon Virtual Private Cloud is a leading tool in the market, Microsoft Azure's cloud services can be considered one of its competitors. Amazon Virtual Private Cloud is better than Microsoft Azure since it provides easy integrations, support, and multiple services.

The product's initial setup phase is simple since my company manages it with the use of Terraform.

When it comes to Amazon Virtual Private Cloud, my company had opted for a canary deployment.

Compared to the other products in the market, Amazon Virtual Private Cloud is available at a low price.

My company uses Amazon Virtual Private Cloud for our corporate data center.

There are some problems with the third-party tools that are used for integration, but I don't see many problems with the areas involving AWS and Kubernetes.

The product has enhanced our company's operations activities since its network configuration is very handy, and in a few steps, our company can set it up between the microservices.

It is easy to integrate Amazon Virtual Private Cloud with AWS services.

I recommend the product to others who plan to use it.

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

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. 

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.