Configure your network for Genesys-defined Autonomous System Numbers (ASNs)
If you have route-path requirements, you can use the Genesys-defined Autonomous System Number (ASN) feature to identify, filter, or steer Genesys Cloud routes by region.
An ASN is a globally unique number that identifies a network on the internet. Networks use the Border Gateway Protocol (BGP) to advertise their routes, and every route carries an AS_PATH — the list of ASNs the traffic passes through. Previously, Genesys Cloud traffic was reaching you over AWS Direct Connect or your ISP, both of which advertise their own ASN. So there was no Genesys-specific marker you could match on to tell Genesys routes apart by region.
AWS advertises Genesys Cloud’s prefixes using the AWS Bring Your Own ASN (BYOASN) system to originate routes with a Genesys -defined ASN. Using BYOASN, allows Genesys to advertise its regional prefixes under Genesys-defined ASNs. A Genesys ASN appears in the AS_PATH of the routes you receive, giving you a stable, Genesys-owned identifier for Genesys Cloud traffic per region. Furthermore, having a Genesys-defined ASN provides you with a reference point that you can use in your own routing policies.
The table below, which is sorted by the ASN, shows each Genesys Cloud AWS region and its Genesys-defined ASN.
| AWS region | Region code | ASN |
|---|---|---|
US East (N. Virginia) | us-east-1 | 402867 |
Africa (Cape Town) | af-south-1 | 402868 |
Asia Pacific (Hong Kong) | ap-east-1 | 402869 |
Asia Pacific (Tokyo) | ap-northeast-1 | 402870 |
Asia Pacific (Seoul) | ap-northeast-2 | 402871 |
Asia Pacific (Osaka) | ap-northeast-3 | 402872 |
Asia Pacific (Mumbai) | ap-south-1 | 402873 |
Asia Pacific (Singapore) | ap-southeast-1 | 402874 |
Asia Pacific (Sydney) | ap-southeast-2 | 402875 |
Asia Pacific (Jakarta) | ap-southeast-3 | 402876 |
Canada (Central) | ca-central-1 | 402877 |
Europe (Frankfurt) | eu-central-1 | 402878 |
Europe (Zurich) | eu-central-2 | 402879 |
Europe (Ireland) | eu-west-1 | 402880 |
Europe (London) | eu-west-2 | 402881 |
Europe (Paris) | eu-west-3 | 402882 |
Middle East (UAE) | me-central-1 | 402883 |
Mexico (Central) | mx-central-1 | 402884 |
South America (Sao Paulo) | sa-east-1 | 402885 |
US West (Oregon) | us-west-2 | 402886 |
US East (Ohio) – FedRAMP | us-east-2 | 402887 |
EU Sovereign Cloud (Germany East) | eusc-de-east-1 | 218990 |
When can I begin to apply route filtering?
You can begin to apply the Genesys ASN in your route policies after your region has migrated. The region migration will roll-out on a weekly basis throughout the month of January. For specific dates of the region migration roll-out, see Genesys Cloud – Planned network maintenance for Genesys Cloud Autonomous System Numbers.
Overview
To understand how ASN works, it’s helpful to break it down a bit. To begin with, an Autonomous System (AS) is a collection of IP networks under a single administrative and routing policy. Each AS is identified by an ASN, which is a globally unique value assigned by a Regional Internet Registry, such as ARIN, RIPE, or APNIC.
To exchange reachability and path information between Autonomous Systems, you need the Border Gateway Protocol (BGP). More specifically, the BGP is the routing protocol that exchanges reachability information between autonomous systems on the internet. As a route is advertised from one AS to the next, the BGP records the sequence of ASNs it has traversed in an attribute called the AS_PATH. The first ASN added to the AS_PATH, either the innermost or the right-most, is the originating ASN for that prefix.
There are four reasons to use ASNs:
- Identity: An ASN identifies who originated a route, independent of the specific IP prefixes involved.
- Loop prevention: The BGP rejects a route whose AS_PATH already contains the receiving AS.
- Policy: Network operators make routing decisions (accept, reject, prefer, de-prefer) based on the ASNs in the path.
- Stability: Prefixes behind an AS can change over time, but the ASN that originates them stays constant.
How an ASN enables route filtering
Now that you have a general idea of what an ASN is, let’s take a look at how an ASN enables route filtering. Every route that AWS advertises for a given Genesys Cloud region originates with that region’s ASN. This allows a network operator to write a routing policy, or routing filter, that matches the ASN in the AS_PATH. A typical filter has two parts:
- An AS _PATH match, which is often a regular expression that identifies routes carrying a specific Genesys Cloud ASN.
- A policy action, that permits the matched routes and denies the rest of the routes, or applies the necessary attributes, such as local preference.
There are a two main methods that you can use to write the AS_PATH match and they differ in how they specify the ASN’s position in the path. The two methods are: unanchored and end-anchored.
Unanchored
An unanchored AS_PATH can match the Genesys Cloud ASN wherever it appears in the route. An unanchored AS_PATH uses the “_” character on either side of the ASN to match a path boundary, or separator. For example, an unanchored AS_PATH for Europe (Frankfurt) would be formatted “_402878_”.
End-anchored
An end-anchored AS_PATH provides customers with a strict placement option as it only matches the ASN as the origin (the end of the AS_PATH). In other words, it only matches a route that Genesys Cloud currently originates. An end-anchored AS_PATH uses the “_” character at the beginning of ASN and a “$” at the end of the ASN to mark the end of the path. For example, an end-anchored AS_PATH for Europe (Frankfurt) would be formatted “_402878$”.
Reading the AS_PATH where Genesys Cloud is the origin
Customers do not peer with Genesys Cloud directly. Your BGP session is with a peer through AWS Direct Connect or with your ISP so your BGP neighbor’s ASN is that of AWS or your ISP. The Genesys Cloud ASN only appears inside the AS_PATH, as the origin of the route.
With AWS BYOASN, AWS inserts the Genesys Cloud ASN as the innermost, or originating, entry in the AS_PATH for a prefix advertised from that region. The AS_PATH is built as a route propagates: each AS prepends its own ASN to the front of the path. As a result, the left-most (outermost) ASN is the AS nearest to you, the receiver, and the right-most (innermost) ASN is the origin. Because AWS originates the route on Genesys Cloud’s behalf, the Genesys Cloud ASN is always the innermost, right-most entry, sitting behind the ASN(s) of your peer and any transit networks in between.
Filtering by region
With BYOASN, a region’s Genesys Cloud ASN is carried as the origin in the AS_PATH of each route. This means that a customer who receives those routes over BGP with the AS_PATH intact, can filter by region by matching the ASN. This offers several advantages:
- The ASN identifies the region – no regional CIDR knowledge required.
- You configure one ASN per region – you match the region’s ASN, not its prefixes
- ASN filtering works on any BGP session that delivers the Genesys Cloud routes with their AS_PATH – not limited to Direct Connect and community strings.
- Self-updating scope. When the prefixes in a region change, AWS still originates them with the same Genesys Cloud ASN, so your filter keeps matching them with no change on your side.
- Lower operational risk. There is no route list to fall out of date and no window where new prefixes are unintentionally blocked or old ones unintentionally allowed.
Receiving AWS advertised routes
ASN filtering can only act on routes you actually receive over BGP. The match reads the AS_PATH of each Genesys Cloud prefix, so those specific prefixes carrying the Genesys Cloud ASN must be present in the routes your peer advertises to you.
As long as you receive the Genesys Cloud routes, the ASN gives you a unique identifier for every Genesys Cloud route in a region. You can scope your filtering to that region by matching the ASN alone. No dependence on Direct Connect community strings.
Route filtering examples by vendor
To help you get started, let’s take a look a some filter examples for a couple common vendors. These examples show how to permit routes carrying a specific Genesys Cloud region ASN and deny the rest. Two ASNs appear in each example: the neighbor (remote-as / peer-as) is your BGP peer; AWS or your ISP shown as the placeholder 64500, while the ASN in the AS_PATH match is the Genesys Cloud region ASN you want to accept. Replace the neighbor IP address, the peer ASN, and the Genesys Cloud ASN with the values for your peering and target region.
Each example uses the the Genesys recommended unanchored method, which matches the Genesys Cloud ASN wherever it appears in the AS_PATH. We’ll point out the end-anchored, strict origin, method in a comment.
Cisco IOS / IOS-XE
Match the Genesys Cloud ASN in the AS_PATH with a regular expression, then reference that path list from a route map applied inbound on the BGP session to your peer (AWS or your ISP). The example permits the Frankfurt region (AS402878) and denies everything else, using the preferred unanchored match. To match only the origin position instead, use “_402878$”. The neighbor’s remote-as is the peer’s ASN (shown here as 64500), not the Genesys Cloud ASN.
! Permit routes carrying Genesys Cloud eu-central-1 (Frankfurt), AS402878 ! Preferred: unanchored, matches the ASN anywhere in the AS_PATH ip as-path access-list 10 permit _402878_ ! Strict option (origin only): ip as-path access-list 10 permit _402878$ ip as-path access-list 10 deny .* ! route-map GENESYS-EUC1-IN permit 10 match as-path 10 ! router bgp 65001 ! 64500 = your BGP peer (AWS or ISP), NOT the Genesys Cloud ASN neighbor 192.168.59.1 remote-as 64500 neighbor 192.168.59.1 route-map GENESYS-EUC1-IN in !
Juniper Junos
Define an AS-path regular expression, reference it from a policy term, and apply the policy as an import filter on the BGP session to your peer (AWS or your ISP). This example accepts routes carrying AS402880 (eu-west-1, Ireland) using the preferred unanchored match. To match only the origin position instead, use “.* 402880”. The peer-as is the peer’s ASN (shown here as 64500), not the Genesys Cloud ASN.
policy-options {
/* Preferred: unanchored, matches AS402880 anywhere in the path */
as-path genesys-euw1 ".* 402880 .*";
/* Strict option (origin only): as-path genesys-euw1 ".* 402880"; */
policy-statement GENESYS-EUW1-IN {
term accept-euw1 {
from as-path genesys-euw1;
then accept;
}
term reject-rest {
then reject;
}
}
}
protocols {
bgp {
group PEER {
import GENESYS-EUW1-IN;
neighbor 192.168.59.1 {
# 64500 = your BGP peer (AWS or ISP), NOT the Genesys Cloud ASN
peer-as 64500;
}
}
}
}Fortinet FortiOS (FortiGate)
Create an as-path access-list that matches the target ASN, bind it to a route-map, then apply the route-map inbound on the BGP session to your peer (AWS or your ISP). This example permits AS402881 (eu-west-2, London) using the preferred unanchored match. To match only the origin position instead, use “_402881$”. The neighbor’s remote-as is the peer’s ASN (shown here as 64500), not the Genesys Cloud ASN.
config router aspath-list edit "genesys-euw2" config rule edit 1 set action permit # Preferred: unanchored, matches the ASN anywhere in the path set regexp "_402881_" # Strict option (origin only): set regexp "_402881$" next end next end config router route-map edit "GENESYS-EUW2-IN" config rule edit 1 set match-as-path "genesys-euw2" next end next end config router bgp config neighbor edit "192.168.59.1" set remote-as 64500 set route-map-in "GENESYS-EUW2-IN" next end end
Check Point (Gaia clish)
On Gaia, define a routemap that matches the Genesys Cloud AS and set it as the inbound policy for the BGP session to your peer (AWS or your ISP). This example accepts AS402886 (us-west-2, Oregon) and restricts the remainder. Matching by AS number matches the ASN wherever it appears in the path (the preferred, position-independent behavior); if your platform supports an AS-path regular expression and you want strict origin-only matching, anchor it with “_402886$”. The peer’s remote-as is the peer’s ASN (shown here as 64500), not the Genesys Cloud ASN.
set routemap GENESYS-USW2-IN id 10 on ! match as-path by AS number: matches AS402886 anywhere in the path (preferred) set routemap GENESYS-USW2-IN id 10 match as-path 402886 set routemap GENESYS-USW2-IN id 10 action permit set routemap GENESYS-USW2-IN id 20 on set routemap GENESYS-USW2-IN id 20 action deny ! 64500 = your BGP peer (AWS or ISP), NOT the Genesys Cloud ASN set bgp external remote-as 64500 peer 192.168.59.1 import-routemap GENESYS-USW2-IN preference 10 on
FAQs
What is BYOASN?
Bring Your Own Autonomous System Number (BYOASN) is an AWS capability that lets AWS advertise an organization’s AWS hosted prefixes using an ASN that an organization owns rather than an Amazon owned ASN. Genesys Cloud uses BYOASN so that when AWS advertises Genesys Cloud prefixes for each AWS region, those routes originate with a Genesys Cloud owned ASN.
Do I need to know Genesys Cloud’s regional CIDR blocks to filter by region?
No. Genesys Cloud does not publish its region to CIDR mappings. With ASN based filtering, you match on the ASN in the BGP AS_PATH so your policy stays correct even when Genesys Cloud adds or removes the prefixes behind that ASN.
How did region filtering work before BYOASN?
The only prior method to filter Genesys Cloud routes by region without knowing the CIDR blocks was over an AWS Direct Connect, where AWS appends BGP community strings to the advertised routes. Customers could match those communities to identify the region. That approach required Direct Connect; BYOASN removes that requirement by carrying the region’s ASN as the route origin, so ASN based region filtering works on any BGP path that exposes the AS_PATH.
Does the ASN change if Genesys adds new CIDR blocks to a region?
No. Each region maps to a unique Genesys Cloud ASN. When AWS advertises new Genesys Cloud prefixes for that region it originates them with the same ASN. An ASN based filter picks them up automatically.
Does ASN filtering replace prefix (CIDR) filtering?
It does not have to. ASN filtering is the lower maintenance option because it survives prefix changes. You can still combine it with prefix filters if your routing policy calls for both.
Does ASN filtering replace AWS Direct Connect community strings?
It does not have to. If you use Direct Connect, you can continue to match on the BGP community strings, use ASN filtering, or combine the two. ASN filtering can be the better option because it keys on the region’s ASN itself, so your policy identifies the region the same way no matter which region your Direct Connect is associated with.
Can I use ASN filtering if I peer with my ISP for internet access?
Only if your ISP session delivers the AWS advertised Genesys Cloud routes with their AS_PATH. Many internet access ISP sessions provide only a default route (0.0.0.0/0), which carries no per-prefix AS_PATH, so there is nothing for an ASN filter to match. If you receive the Genesys Cloud prefixes (for example via a full or partial BGP table), ASN filtering works over the ISP. If you receive only a default route, it does not. You must arrange to receive the routes or use an AWS Direct Connect.
Do I configure the Genesys Cloud ASN as my BGP neighbor’s ASN?
No. You would never use the Genesys Cloud ASN as your BGP neighbor’s ASN. You do not peer with Genesys Cloud. Whether you connect over AWS Direct Connect or through your internet provider, your BGP neighbor is AWS or your ISP. Your neighbor’s ASN is the one AWS or your ISP provides. The Genesys Cloud ASN only appears inside the AS_PATH of the routes you receive, which is what your filter matches on.
Is the Genesys Cloud ASN guaranteed to be the origin in the AS_PATH?
AWS, not Genesys Cloud, controls how the ASN and prefixes are advertised. Today AWS inserts the Genesys Cloud ASN as the origin (innermost) entry, but AWS could change this in the future. Although a change is considered unlikely, it is outside Genesys Cloud’s control. For that reason the examples use an unanchored match (for example “_402878_”) that matches the ASN wherever it appears in the path, so it keeps working regardless of position. If you specifically want to match the origin position, use the origin-anchored form (for example “_402878$”) instead, and revisit it if AWS ever changes where the ASN sits.
[NEXT] Was this article helpful?
Get user feedback about articles.