Tags down


Error when creating private subnets within AWS VPC

By : Venkat Dabbara
Date : August 01 2020, 04:00 PM
To fix the issue you can do A /21 is quite an unusual netmask to be using. It contains 2048 IP addresses.
The netmask for /21 would be:
code :
CIDR            First address   Last address  Good!  Invalid  Invalid  Invalid

Share : facebook icon twitter icon

Private subnets options in AWS

By : Christian
Date : March 29 2020, 07:55 AM
it fixes the issue It appears that your requirements are:
Run some Amazon EC2 instances Keep them "private" from the Internet (no direct access from the Internet to the instances) Allow the instances to access the Internet (eg to download updates, or to communicate with AWS API endpoints)

Error in creating multiple subnets in AWS VPC

By : Wolfy
Date : March 29 2020, 07:55 AM
Hope that helps A VPC range of means that all addresses starting with 10.0.x.x are part of the VPC.
When you create the subnet, you want it to be a portion of the VPC. People typically assign an address like -- the /24 means that the subnet has every IP address starting with 10.0.1.x.

Multiple private subnets?

By : user2955951
Date : March 29 2020, 07:55 AM
fixed the issue. Will look into that further You are correct. You should only need one Public subnet and one Private subnet per Availability Zone.
And, in fact, you could just use public subnets by configuring Security Groups to restrict traffic.

AWS NLB in public subnets with EC2 in private subnets

By : Zoodel
Date : March 29 2020, 07:55 AM
I wish did fix the issue.
Since you cannot associate a Security Group to a NLB, how could you accomplish this with the same type of security?
code :
Recommended Rules

Inbound Source      Port Range        Comment
Client IP addresses instance listener Allow traffic from clients on the instance listener port

VPC CIDR            health check      Allow traffic from the load balancer on the health check port

Two Public subnets can not communicate with private ip

By : Ankush Shingade
Date : March 29 2020, 07:55 AM
I hope this helps you . Even though you run the React code and the NodeJs code in the same VPC, when you run the program, the React code gets pushed to the browser. So when the end-user tries to use the app and starts calling the backend API through the private IP from a browser which is outside your VPC, the call won't reach the Node server. One solution for this is to create a reverse proxy using something like Nginx. Nginx will sit inside the VPC(Public subnet 1) and handle the communication between the browser and the backend API.
code :
server {
  listen 80;
  listen [::]:80;

  server_name example.com;

  location /api/getitems {
      proxy_pass https://yourprivatip/api/getitems;
Privacy Policy - Terms - Contact Us © voile276.org