Executive summary
- What changed: The Dev Dashboard IP allowlist now accepts networks by autonomous system number, not just IP addresses and CIDR ranges, with up to 10 ASNs and 10 countries per app.
- Why it matters: Apps on serverless platforms had no workable way to meet the allowlist requirement, since egress addresses change. ASN rules close that gap before the November deadlines.
- Who should act: Teams running apps on serverless or autoscaling infrastructure, and anyone reviewing vendor allowlist setups.
What changed
The IP allowlist section of an app's Settings page now offers two rule types: IP addresses and Networks by ASN. An ASN identifies a network run by one organisation, typically a hosting provider or ISP. You can enter up to 10 ASNs, as numbers with or without an AS prefix, and narrow them to 10 countries. Requests from outside the allowed networks fail with a 403.
Matching is done by lookup. Shopify resolves each request's source address to an ASN and country using MaxMind GeoLite data, then allows it when the ASN is listed and, if you list countries, the country matches. Where the data has no ASN, or no country while you filter by country, the request is rejected. You can test a rule set against recent traffic before enabling enforcement.
IP address rules remain the narrower option: up to 100 entries, public addresses only, and the gateway address where servers sit behind NAT.
Why it matters
This is what makes the November requirement achievable for modern app architectures. Without it, every app on a serverless platform faced a requirement it could not technically meet, pushing otherwise healthy vendors toward the delisting date.
The tradeoff deserves naming. An ASN is a shared network: anyone else running servers inside an ASN you allow, holding a stolen token for your app, can use it from there. ASN rules are a real improvement over no allowlist and a clear step down from specific addresses. When evaluating a vendor, the useful question is not whether they have an allowlist but which rule type they use and whether it is constrained by country. The same discipline applies to the monitoring and alerting around your integrations, because a 403 from a misconfigured rule looks exactly like an outage.
Role-specific impact
- Marketers: No direct action. Note that if a vendor enables enforcement with an incomplete rule set, the symptom is a data sync that stops with no storefront error.
- Developers: Prefer IP rules wherever you can pin egress, via a NAT gateway or your platform's static egress option. Where you cannot, find your real ASNs from provider documentation or from client addresses in Dev Dashboard logs, always add the country filter, and test before enforcing. A provider can operate several ASNs and add more over time.
- Store admins: When reviewing app security posture in the admin, treat allowlist presence as baseline and rule type as the quality signal.
Use-case example
Real-world scenario
An integration app on a serverless platform handles order webhooks and writes fulfilment updates back through the Admin API. Its egress addresses rotate across a provider range, so IP rules are unusable. The team pulls two weeks of Dev Dashboard logs, finds client addresses resolving to three provider ASNs across two countries, enters all three with both countries, and tests against recent traffic. The test surfaces a fourth ASN carrying roughly 4 percent of requests from a newly added region, which would have failed silently. Catching that before enforcement is the difference between a clean cutover and a day of dropped fulfilment updates.
Implementation checklist
- Check whether your egress addresses are genuinely dynamic, or whether your platform offers a static egress or NAT gateway option instead.
- Collect client addresses of recent Admin API requests from Dev Dashboard logs and resolve them to ASNs.
- Cross check that list against your provider's published ASNs, allowing for more than one.
- Enter up to 10 ASNs and add the countries your app runs in, since an unfiltered ASN is allowed from anywhere.
- Test against recent traffic and investigate every unmatched request before enforcing.
- Alert on Admin API 403 responses so a rule gap surfaces in minutes, not at the next reconciliation.
FAQ
Q: Is allowing an ASN as safe as allowing specific IP addresses?
A: No. An ASN covers a provider network shared with other customers, so a stolen token could still be used from inside it. Use IP rules when you can pin egress, and narrow ASNs by country.
Q: What if our provider adds a new ASN after we configure the list?
A: Requests from it are rejected with a 403. Re check your logs after any platform or region change, and keep alerting on 403 responses so gaps surface quickly.
Resources
Restrict API access with an IP allowlist
Need guidance? Talk to Makro.