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.

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

VPC is basically about networking and how you are setting up the networks.

VPC, or Virtual Private Cloud, is like a secure portion of AWS's public cloud. So, if you want to secure your dedicated network areas, we use VPCs. Traffic should be slow, and no unwanted people should enter your network, especially because we work at an enterprise level. That is why we must be thoughtful and careful about using VPCs.

We use VPC as a service provided by AWS. So, Amazon keeps enhancing the product.  

In Amazon VPC, there's a service called VPC Peering, where we can connect multiple VPCs from different accounts. However, AWS also introduced new tools like Transit Gateway, based on the Hub and Spoke model. At a single hub, you can route from multiple locations, and that is more efficient. So, this is how it goes.

The subnetting feature has impacted our network design. So, subnetting is very, very important and crucial when it comes to your infrastructure design and presentation. 

Subnetting is completely crucial. For example, suppose I'm an enterprise customer. I have to be very thoughtful and decide, like, "Okay, how many route tables am I going to have?" Let's say you are company XYZ, and you want to make sure that, out of one million IP addresses, let's say, 50,000 should be on a round table. Also, 50,000 IP addresses should go to external ones, and the rest should be for internal use only. Like, you have other third-party software that you have hosted as an enterprise customer. 

In this case, subnetting plays a vital role. You have to be thoughtful, like, "Okay, are you going to use 32 bits? How many IPs do you want to use?" And you have to be very thoughtful about choosing the application. For example, in Kubernetes, we are very thoughtful about using the IPs. They can easily exhaust the IPs. So we have to be very thoughtful about that. So,  subnet skills play a very vital role.

It's all about networking. So VPC, VPC peering, and those features. That's all about the networking aspect of VPC. I like it. 

For network security, Network Access Control Lists (NACLs). They work very well. For example, instead of leaving a resource open to the world with something like 0.0.0.0/0, we can use NACLs to be much more specific with our network traffic rules. It adds an important security layer to our infrastructure.

There is always room for improvement. It can be in support. 

I've been using it for more than three years. 

The stability of VPC itself is incredibly high. AWS guarantees 99.9999999% uptime; it's super reliable.

VPC is not about scaling up the world; it's about securing the infrastructure. For example, you start in AWS by creating an EC2 instance to deploy infrastructure for an application, which is good. 

But maybe not today or tomorrow, but in a year, you'll need to ensure security. Since you work in enterprise scenarios, you have to be very thoughtful. 

Whatever system you create on the cloud, the type of VPC we use will ensure that the infrastructure I create is accessible only by my team members and not by the outside world. We use a NAT gateway for part of the private cloud, which adds a lot of complexities to the model.

So, scaling up or down is handled by Auto Scaling groups and launch templates.

My company and the enterprise clients I work with all use it.  

I ran into some issues. I created a support ticket with AWS, and they set up a call with me on AWS Chime. Their networking architect helped me troubleshoot the errors. They were really helpful.

Positive

I use many tools, like infrastructure services, software services, and Platform as a Service. As a DevOps engineer, I have touched base with all the services. 

Starting from the basic ones like EC2, VPC, subnets, to Lambda functions, API gateways, CloudWatch, AWS Glue, Athena, SageMaker, DynamoDB—all these things I have used.

If you have knowledge of network ACLs and security groups, then you can easily set up network ACLs and security groups in VPC. 

In layman's terms: think of a security group as the front door of an EC2 instance. It controls what comes in and goes out of your EC2. A NACL is like security at the subnet level – it controls what can enter your subnet via the NACL. So, security groups are on EC2 instances, NACLs are on subnets.

The process of integrating VPC with other AWS services is easy and seamless. That's the beauty of AWS – the services are tightly integrated within the AWS console. You can switch between them easily and do what you need. You can manage it directly from the console or automate it with Terraform, it's up to you.

The pricing depends on usage. 

I would definitely recommend using it. If you're working at an enterprise level, or even if you're a startup building software or a website, and you want to ensure security and long-term stability, then absolutely use VPC and configure your network carefully.

Overall, I would rate the solution a nine out of ten. There is always room for improvement. 

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 the solution to create virtual instances for our customers' environments.

The solution is beneficial for us overall.

We are unable to edit the instances due to our license's limitation. They should release a trial version. It would be helpful for users.

We have been using the solution for a long time.

I have used Google Cloud before. It is far better than AWS.

The solution's initial setup process is complicated. It would be best if you have expertise in AWS, or you have gone through its documentation for a better idea about the process.

It is a good tool. I advise others to use the solution if they have its license. I rate it as a ten.

I use Amazon Virtual Private Cloud for deploying servers on EC2. It helps with data migration from the on-premise setup to the cloud. It connects resources to the internet through services like Amazon Internet Gateways. It enables us to create software-defined network environments as well.

The product is flexible and easy to use.

There could be better documentation for specific services. It has a lot of technical processes, including outbound and inbound rules. It is complicated for a new user to understand the product’s usability. They should break down the processes with effective explanations.

We have been using Amazon Virtual Private Cloud for two years.

I rate the product’s stability a ten out of ten.

We have a large number of user base for Amazon Virtual Private Cloud. It is a scalable application. I rate its scalability a ten out of ten.

The initial setup is easy for executives with prior experience using the product. It takes a few seconds to complete the process.

It is a free-to-use service.

I rate Amazon Virtual Private Cloud a ten out of ten.