Amazon Virtual Private Cloud Reviews

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.

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.

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.

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

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

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.