Refer to this policy information when configuring your Direct Connect router.

Inbound (towards Akamai)

• You can use your own public Autonomous System Number (ASN). This is used to identify a network node for routing purposes.
• There is a prefix filter and a maximum prefix limit of 30 per BGP session. When the session reaches the maximum prefix limit, BGP is shut down.
• You can announce up to a /32 IPv4 prefix and up to a /64 IPv6 prefix.
• You can deploy NAT, but at least one prefix has to be announced via BGP. Don't use the WAN IP for NAT.
• All prefix filter update requests are validated against the well known RIR (ARIN / APNIC / AFRINIC / LACNIC / RIPENCC / RADB)
• Direct Connect can only be used for traffic towards the global CDN.
• In order to comply with the BCP 38 standard, you can either announce the source IP via BGP, or deploy Source based NAT (SNAT).
• The BGP well-known community (RFC1997) is not supported. Any non-Akamai supported BGP communities are ignored and overwritten.
• You can use AS Path prepend, MED and BGP communities (20189:330 low local preference (default) medium local preference 20189:385 high local preference) to adjust the return traffic between multiple Direct Connect connections.

Outbound (from Akamai)

• Only the public prefixes of Akamai Aggregated Block will be announced. You'll need to filter more specific routes from Peering or full routes IP Transit.
• All public prefixes are announced with IANA well-known community No-Export, AS Path prepend three times. Do not override or ignore this.
• Don't re-advertise the Akamai Public prefix beyond the network boundary such as public internet. Otherwise, Akamai reserves the right to terminate the service without prior notice.