- Newest
- Most votes
- Most comments
Yes, the ASN for BGP peering with AWS is 7224.
When establishing a BGP peering session with AWS over a public Virtual Interface (VIF) for a Direct Connect connection, you should use the ASN 7224 to establish the BGP session on the AWS side.
This ASN is used by AWS for all public Virtual Interfaces, regardless of the AWS region or whether you're using a hosted or dedicated connection.
It's important to note that you need to configure your own unique ASN on your router or customer gateway device, which should be different from 7224, to establish the BGP peering session successfully.
I would recommend once you create the Direct Connect Public Virtual Interface, download the router configuration file. This file should have the AWS side of the BGP ASN, Peer IPs etc information. While in the dropdown you may not see the exact Vendor/Platform/Software that you are using but you should be able to locate the ASN etc info in this file.
Thank you, Tushar J. I will do that. As you can tell, I am new to that thing. Sorry, It seemed only allowing mark one as Accepted Answer.
Frank
Relevant content
asked 6 months ago- asked 9 months ago
- asked a year ago
- AWS OFFICIALUpdated 7 months ago
Thank you, emned, for the confirmation. A related question. Once I set up the peer link, we need accept some Genesys routes from AWS, but the routes are not advertised from AS 7224, but from AS14618 and AS16509, which are owned by Amazon. If I peer the link to AS7224, do I see the Genesys routes in my peer router?