DevOps Engineer at Upperthrust Technologies Private Limited
Real User
Top 5
2024-03-20T14:58:34Z
Mar 20, 2024
It would be beneficial to introduce more managed features and enhance customization options in the product. It could be more versatile and easy to use.
VPC itself is pretty good, but understanding it well is key. One of the challenges for beginners is understanding IP address ranges and subnet concepts. For example, why use a /16 CIDR block for a VPC versus a /24? It's important to understand these concepts before creating a VPC. Once you understand the basics, you can leverage VPC features based on your architecture. For example, a three-tier architecture (web application, database, etc.) can benefit from public and private subnets. The web application can reside in a public subnet for internet access, while the database can reside in a private subnet for security, only accessible through the web application. This helps isolate resources and improve performance. So, the first step is understanding VPC creation and then using subnets (public and private) based on your architecture. Public subnets can connect to the internet, while private subnets cannot by default. For internet access in a private subnet, you can use a NAT Gateway and route tables. Other components include the internet gateway (for public subnet internet access), Elastic IPs (static IP addresses), and more advanced options like VPN connections, AWS PrivateLink, etc. Once you grasp these basic concepts, you can explore the more advanced features.
Consultant at a computer software company with 5,001-10,000 employees
Consultant
Top 20
2023-09-21T15:19:11Z
Sep 21, 2023
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.
While creating a VPC, you can create a private and public subnet. If you forget to automatically assign a public IP address when creating an EC2 instance, the instance will not be able to access the internet. You can enable automatic public IP assignment for your public subnet to avoid this. This is something one always forgets while creating a VPC in infrastructure.
The product is restricted to a particular region. They should provide a global architecture. So that it will save a lot of time considering repeated configuration tasks.
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.
This solution is not fully compatible with every vendor that we use regarding firewalls and networking equipment. They provide you with the option and details on how to configure this on your premises but it would be good to have an easier way to do this.
Amazon Virtual Private Cloud (Amazon VPC) lets you provision a logically isolated section of the AWS Cloud where you can launch AWS resources in a virtual network that you define. You have complete control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways. You can use both IPv4 and IPv6 in your VPC for secure and easy access to resources and applications.
It would be beneficial to introduce more managed features and enhance customization options in the product. It could be more versatile and easy to use.
VPC itself is pretty good, but understanding it well is key. One of the challenges for beginners is understanding IP address ranges and subnet concepts. For example, why use a /16 CIDR block for a VPC versus a /24? It's important to understand these concepts before creating a VPC. Once you understand the basics, you can leverage VPC features based on your architecture. For example, a three-tier architecture (web application, database, etc.) can benefit from public and private subnets. The web application can reside in a public subnet for internet access, while the database can reside in a private subnet for security, only accessible through the web application. This helps isolate resources and improve performance. So, the first step is understanding VPC creation and then using subnets (public and private) based on your architecture. Public subnets can connect to the internet, while private subnets cannot by default. For internet access in a private subnet, you can use a NAT Gateway and route tables. Other components include the internet gateway (for public subnet internet access), Elastic IPs (static IP addresses), and more advanced options like VPN connections, AWS PrivateLink, etc. Once you grasp these basic concepts, you can explore the more advanced features.
The solution needs to add step-by-step tutorials for its services.
The tool is not scalable.
The solution has to be more robust and scalable.
There is room for improvement in UI.
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.
While creating a VPC, you can create a private and public subnet. If you forget to automatically assign a public IP address when creating an EC2 instance, the instance will not be able to access the internet. You can enable automatic public IP assignment for your public subnet to avoid this. This is something one always forgets while creating a VPC in infrastructure.
The product is restricted to a particular region. They should provide a global architecture. So that it will save a lot of time considering repeated configuration tasks.
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.
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.
Billing and technical support should be better. There is a steep learning curve as well.
You should be able to toggle off some cloud services when you don't need them and switch them on when necessary.
This solution is not fully compatible with every vendor that we use regarding firewalls and networking equipment. They provide you with the option and details on how to configure this on your premises but it would be good to have an easier way to do this.