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.

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.

Our company uses the solution to provide virtual private clouds for customers. It is the heart of AWS because it is the networking part of cloud services that includes a private subnet, public subnet, and private gateway. The solution represents everything from the network perspective. 

Within the solution, you create the network environment that includes provisions, services, the DB, the EKS, and zones. You set inbound and outbound traffic services. You enable security features and firewalls that are used by the solution. 

It is very easy to provision VPCs and build networks. 

The solution could have tighter security for traffic. 

I have been using the solution for four years. 

The stability is very good so is rated a ten out of ten. 

The scalability is good so is rated a ten out of ten. 

Technical support is highly supportive so is rated a nine out of ten. 

Positive

The setup is a little bit difficult. After creating the VPC, you have to create subnets based on your requirements for private or public. Then you have to create everything else including the NAT gateway. The final step is to configure both gateways for private and public subnets. The overall creation process takes about 40 minutes.  

The entire concept is networking. You have to figure out what things are important and create bridges. 

For example, one person with Vodafone services in the UK places a call to another person in India. The country and regional VPCs are in place and it takes permissions to cross them. The call's TCP response goes to the UK servers and the call is dialed using the VPC in the UK. It then hits the VPC in India where it is verified, pushed to the mobile network servers, and is rings through. 

Because the setup has complex steps, it is rated a four out of ten. 

We implement the solution for customers. 

The solution's pricing is on the higher side so is rated a five out of ten.  

The solution is a very, very good product and the heart of everything. I rate the solution a ten out of ten. 

We use Amazon VPC to host our EC2 instances. 

With an AWS virtual private cloud, you're in charge of what you use. It's pay-as-you-go.

You should be able to toggle off some cloud services when you don't need them and switch them on when necessary. 

We've been using Amazon VPC for about two or three years.

I rate Amazon VPC nine out of 10 for ease of setup. The basic setup is easy, but you can do some advanced configurations. It's straightforward overall. The standard deployment takes about one minute. However, the time needed to complete the rest of the configuration depends on your infrastructure and third-party applications. Four or five DevOps engineers work with the solution. 

You will see a return if you're using it correctly. For example, some people might use an improper family class for their EC2 instances.

The price is based on how long you want your VPCs to run. It also depends on the class and family of the VPCs and the resources running underneath. 

I'm not sure why the company adopted AWS. It's one of the most popular cloud platforms. Also, they have already deployed lots of resources on AWS, so it makes sense to continue with it. 

I rate AWS Virtual Private Cloud eight out of 10. I recommend it. We save money by not running an on-prem server, so it's definitely worth it. It's flexible and light, yeah.

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 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.