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.

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.

Amazon EKS and a few particular services are used with the help of Amazon Virtual Private Cloud in our company. In our organization, we have a few dedicated services on Amazon Virtual Private Cloud.

The most valuable features of the solution stem from the security groups it provides. Network access control is also a beneficial feature of the product. With the security group as a part of Amazon Virtual Private Cloud, users can access any particular URL or IP address to which access has been assigned. The benefits provided by the product include enhanced security features along with customizable policies that can be adapted or changed whenever required.

From an improvement perspective, the product's initial setup phase should be easy for those who are not experienced in creating VPCs.

I have experience with Amazon Virtual Private Cloud.

Stability-wise, I rate the solution a ten out of ten.

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

The product's initial setup phase is easy if you have a certain amount of experience in creating VPCs.

In our company's cloud architecture, we have two Amazon Virtual Private Clouds used in multiple regions. Amazon Virtual Private Cloud also has multiple subnets, consisting of four public subnets and four private subnets. In public and private subnets, my company has multiple services. Our company's main database is maintained in the private subnet. The normal services are used on the public subnet. An internet gateway is present on a public subnet. If my company needs to access any data from the public subnet, we can use the internet gateway and access any services we want. If my company wants to access any database, then we will have to maintain it on the private subnet. In our company, we have to attach the NAT gateways to the public subnet. Within those NAT gateways, we can access the data in private subnets.

Scaling resources is not a part of Amazon Virtual Private Cloud. Resources would be a part of the services available in subnets.

In subnetting, that is, public subnets and private submits. Public subnets have internet access. Users can access any kind of data from the public subnet with the internet. In private subnets, users don't have any internet access. If you need to access data on the internet from private subnets, you can use NAT gateways.

It is easy to deal with the setup process of network ACLs and security groups in Amazon Virtual Private Cloud.

In terms of the integration of AWS services with Amazon Virtual Private Cloud, most of the services in our company are created inside Amazon Virtual Private Cloud. For any of the services that we use in our company, we select Amazon Virtual Private Cloud. My company has the option to choose the product's default and dedicated version, and we choose the dedicated Amazon Virtual Private Cloud. Whatever we use or create in our company is assigned to the dedicated Amazon Virtual Private Cloud chosen by us.

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

My company deals with many Amazon Virtual Private Clouds available in multiple zones. If we need to access data in an Amazon Virtual Private Cloud from a separate Amazon Virtual Private Cloud, the company can use VPC peering to connect them.

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

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. 

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.