# Use Bring Your Own ASN (BYOASN) to enforce data sovereignty on AWS Direct Connect public VIFs

DevFeed: [Use Bring Your Own ASN (BYOASN) to enforce data sovereignty on AWS Direct Connect public VIFs](<https://devfeed.tech/articles/use-bring-your-own-asn-byoasn-to-enforce-data-sovereignty-on-aws-direct-connect-public-vifs-117600.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/use-bring-your-own-asn-byoasn-to-enforce-data-sovereignty-on-aws-direct-connect-public-vifs/>)

Author: Gonzalo Escarrá

Published: 2026-11-03T19:38:28Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [data-sovereignty](<https://devfeed.tech/tags/data-sovereignty.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [saas](<https://devfeed.tech/tags/saas.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

## AI overview

SaaS providers can use AWS VPC IPAM to associate a distinct Bring Your Own ASN (BYOASN) with each Region where they advertise Bring Your Own IP (BYOIP) prefixes over Direct Connect public VIFs. The region-specific ASN appears as the origin in BGP AS_PATH, giving customers a standard signal to accept routes only from a permitted Region without relying on provider-maintained prefix lists. The provider needs IPAM with regional public pools, qualifying RIR-registered IP ranges and ASNs, matching authorization and ROA records, and public VIF advertisements. Customers need Direct Connect public VIFs and routers that support AS_PATH filtering. On public VIFs, AWS prepends ASN 7224, so the path is `7224 <your-ASN>`. Existing advertised prefixes can switch ASN without withdrawal or downtime; switching from Amazon ASN to a customer ASN is limited to once per hour, and authorizations and ROAs require renewal and maintenance.

## Source excerpt

SaaS providers can use Bring Your Own ASN (BYOASN) on AWS Direct Connect public VIFs to assign a distinct ASN per Region, giving end customers a standard BGP AS_PATH signal to enforce data sovereignty without relying on fragile per-Region prefix lists.