By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Ensuring AWS isn't blocking the specific routes

0

I have connected DX hosted connection to connect to S3 and the public VIF is up and BGP is also up. How do I ensure that AWS is not blocking the routes to router peer IP? Currently I cannot see the return traffic for ping from the MCN firewall. Do we need to whitelist the MCN firewall public ip from AWS side? The router peer IP and amazon router peer IP have been provided by AWS.

Topics
Security, Identity, & ComplianceNetworking & Content Delivery
Tags
AWS Network FirewallAWS Direct ConnectNetworking & Content DeliveryNetwork Security
Language
English
Suvekshya
asked 4 months ago440 views
1 Answer
0

Ping is probably not an accurate test for connectivity. I've just tried pinging a S3 endpoint and I don't get a response yet I can connect to it fine (using curl or some other tool that connects on TCP/443).

To directly answer your question: No, there's no other process where you need to register the IP address given to you on the public VIF.

profile pictureAWS
EXPERT
Brettski-AWS
answered 4 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content