traffic from on-premisses to private subnet through DNS and ELB

Asked Jul 15 '22 at 19:40

Active Jul 15 '22 at 19:40

Viewed 39 times

We have AWS Direct connect and routing set up to allow connectivity from on-premise to the VPCs and the other way around.

We need to access some application running on multiple EC2 from on-premise network only and not from internet.

My understanding is that we need:

DNS forwarding to a private Route 53 Hosted zone which will resolve all request to a
Internal ELB (not external) which in turn will serve request to the application hosted on private subnet EC2s.

So I do not see any need for any public Route 53 zones and no need for an external ELB.

Is my understanding correct or am I missing something about this architecture?

asked Jul 15 '22 at 19:40

Greg Hill

2

That is correct provided that your internal systems have DNS setup correctly to resolve private hosted zones. – John Hanley Jul 15 '22 at 20:10
Thank you for confirming. Is there any better/easier way of securing that app is accessed only internally and traffic goes only through direct connect? – Greg Hill Jul 16 '22 at 21:49
Create a new question as more details are required. – John Hanley Jul 16 '22 at 22:48

0 Answers0