Skip to main content
TrustRadius
Amazon Virtual Private Cloud (VPC)

Amazon Virtual Private Cloud (VPC)

Overview

What is Amazon Virtual Private Cloud (VPC)?

Amazon Virtual Private Cloud (Amazon VPC) lets users provision a logically isolated section of the AWS Cloud where they can launch AWS resources in a virtual network. Users have control over the virtual networking environment, including selection of one's IP…

Read more
Recent Reviews
Read all reviews
Return to navigation

Pricing

View all pricing

IP Address Manager (IPAM)

$0.00027 per active IP address managed by IPAM

Cloud
Hourly

Traffic Monitoring

$0.015 per ENI ($/hour)

Cloud
Hourly

NAT Gateway

$0.045 per NAT gateway

Cloud
Hourly

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://aws.amazon.com/vpc/pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $0.05 per month per NAT gateway
Return to navigation

Product Details

What is Amazon Virtual Private Cloud (VPC)?

Amazon Virtual Private Cloud (VPC) Video

Amazon VPS Overview

Amazon Virtual Private Cloud (VPC) Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(15)

Reviews

(1-2 of 2)
Companies can't remove reviews or game the system. Here's why
Md Khandoker Alif | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
VPC of AWS package [is] really suitable for early-stage startups company to Industries Corporation level architectural infrastructure development under an appropriate budget. Amazon VPC [is] really giving the freedom for developing the MVP development and Scaling it according to on-demand. I also prefer to use the add-ons from the VPC sections services dropDown list.
  • Pricing model & On demand service commitment.
  • Well, architectural infrastructure development processing before spending the money.
  • AWS VPC are providing hassle-free using with all others services from AWS very easily.
  • AWS business support is very helpful & [gives] the right direction according to client’s situations.
  • Need customizable multiple OS installation
  • Dual or multiple OS upgrading at real time using perhaps
  • I think Windows OS Prices need to optimization for new startup based company.
Amazon Virtual Private Cloud (VPC) is well suited for Early-stage IT-based startups company & Corporate highly cloud scaling-based software [companies].
Infrastructure-as-a-Service (IaaS) (9)
80%
8.0
Service-level Agreement (SLA) uptime
70%
7.0
Dynamic scaling
80%
8.0
Elastic load balancing
80%
8.0
Pre-configured templates
80%
8.0
Monitoring tools
90%
9.0
Pre-defined machine images
90%
9.0
Operating system support
50%
5.0
Security controls
90%
9.0
Automation
90%
9.0
  • Yes
  • Not so good for very early-stage startups company. Because it's cutting too much money for them.
  • After using & testing the VPC services then every user should go for 1-3 years Reserve instance-based VPC services. It will help to optimize their cost.
AWS Auto Scaling, Amazon Simple Email Service, Amazon Elastic Compute Cloud (EC2)
Score 10 out of 10
Vetted Review
Verified User
Incentivized
An AWS VPC is in use by default when you create your first account. The VPC is a virtual network within your deployment at AWS. As with any network, you should split up your resources into multiple networks for segmentation/isolation/protection of resources. Through the use of VPCs, we were able to successfully divide up our resources into logically separated areas, providing access to areas based on the role of the user/application/system, instead of full access across the board.
  • Protection of resources based on how roles/access should be allocated.
  • Easy to allocate network CIDR block and split up as needed for IP subnets within the VPC.
  • Used to create public and private networks within the VPC.
  • The biggest issue with VPC networks is knowing how you can leverage VPC endpoints to ensure your resources within the VPC are not reaching out over the Internet to get to AWS services such as S3 and others.
If you are going to deploy within AWS, you need to know how to leverage VPCs. VPCs have several items you must configure for them to be usable and to even link one VPC to another. If you are only going to deploy a few resources or use some of the default configurations, you still need to have working knowledge of how a VPC functions. If you are used to working with VLANs and the ideology behind those, that is the best direct reference to how a VPC can be described, but with additional layers on top of that with route tables, internet gateways, etc.
Infrastructure-as-a-Service (IaaS) (8)
62.5%
6.3
Service-level Agreement (SLA) uptime
100%
10.0
Dynamic scaling
100%
10.0
Elastic load balancing
N/A
N/A
Pre-configured templates
100%
10.0
Monitoring tools
100%
10.0
Pre-defined machine images
N/A
N/A
Operating system support
N/A
N/A
Security controls
100%
10.0
  • AWS VPCs are actively used for following various compliance and regulatory needs such as network separation for PCI DSS. The ability to keep resources and access to those resources controlled through the initial steps of creating VPCs has helped tremendously.
We utilize both AWS and Azure resources for our cloud deployments. The deployment of resources initially was smoother through AWS VPC due to their powerful CLI and Powershell cmdlets. In the past couple of years, the differences between some of the features of AWS VPC and Azure Vnet have diminished. However, the ease of putting things together in a logical flow still belongs in my opinion to AWS.
Return to navigation