Is it mandatory to pay for AWS VpcEndPoint?
I am running simple webserver on AWS
How are there two main route tables in VPC?
I want to setup a route table system something like:
curl request succeeded but JS fetch failed
I have two AWS EC2 instance, one for JS web page and one for Django server.
Access internal API inside AWS VPC
I have two AWS EC2 instances in the same VPC, Region, and Subnet. On instance A I have a very simple Web API setup in IIS on say port 12345. What I would like to do is have instance B be able to access the Web API on instance A without leaving the VPC. I have tried to access the API from instance B using the private IP (10.0.x.x:12345/api/) but it doesn’t work. Both servers are part of the same Security Group as well, and I have a rule allowing all traffic on all ports for the source 10.0.0.0/16. I know I am missing something, just not quite sure what. Any help or pointing me in the right direction is appreciated.
Why is a route table not invoked, when entering a VPC in AWS?
When entering a VPC and invoking for example a load balancer, I would expect, that the main route table is invoked before entering the load balancer, but this is not the case.
NLB with public subnet configured, but scheme is internal – does this make any sense?
Does it make any sense to have a AWS NLB configured with public subnets, but also configure the scheme to be internal?