WAF IP Restrictions Are Now Required for the Public Pattern (Important Notice)
Last updated: October 19, 2026
Sophisticated attacks targeting internet-facing domains have been increasing recently. In light of this, IP address restrictions (allow list) with AWS WAF are now required when AI-Starter is deployed in the public pattern and exposed to the internet. This post explains the background, what changes, and what we ask administrators to do.
Background
In the AI-Starter public pattern, single sign-on (SSO) authentication and AWS WAF have always been used to prevent unauthorized access. IP address restrictions, however, were optional and applied only on request, depending on each customer's environment.
The threat landscape for public domains has changed.
- A newly published domain becomes a target for automated scanning and vulnerability probing almost immediately
- Credential stuffing and brute-force attacks against login pages and authentication endpoints are becoming more sophisticated
The most effective countermeasure is to prevent anyone other than approved sources from reaching the application at all. By restricting access by IP address, we shrink the attack surface itself and no longer expose the pre-authentication surface to the internet. This configuration is now the standard.
What Changes
Affected Configurations
| Configuration | Reachable from the internet | IP restriction |
|---|---|---|
| Public pattern, configuration example 1 (access via the internet) | Yes | Required |
| Public pattern, configuration example 2 (access via a private network) | No (denied by security groups) | Not affected |
| Private pattern | No | Not affected |
This change applies to the public pattern where users access AI-Starter over the internet (configuration example 1). Configurations accessed via a private network already deny inbound traffic from the internet and are not affected. See Architecture for details on each configuration.
Configuration to Apply
The AWS WAF IP address restriction rule is applied in allow list mode.
- Only requests from IP addresses registered in the allow list are permitted
- Requests from any other IP address are blocked by WAF before they reach the login page
- The existing WAF protections remain in place
In terms of the WAF template parameters, this corresponds to the following combination.
| Parameter | Value |
|---|---|
| DefaultAction | block |
| IpRuleAction | allow |
| IpAddressList | Allowed IP addresses (CIDR notation, comma-separated) |
Timeline
- New deployments: For environments built from now on, applying IP restrictions is part of the deployment process. Please confirm and provide the IP addresses to allow before deployment
- Existing environments: If IP restrictions are not yet applied to your environment, please plan to apply them. Your account representative will contact you individually about the schedule and process
What We Ask of Administrators
1. Identify the IP Addresses to Allow
Identify the source global IP addresses from which your users access AI-Starter. Typical examples include the following.
- Static global IP addresses of your office or site internet connections
- Egress IP addresses of remote-access VPNs or cloud proxies (SASE / SWG, etc.)
- Source IP addresses of any external systems or integrations that access AI-Starter directly
Please provide the addresses in CIDR notation (e.g., 192.0.2.1/32). If an address may change in the future, let us know as well.
2. Notify Your Users
Once IP restrictions are applied, AI-Starter can no longer be accessed from environments not included in the allow list. Please notify users in advance, especially those who fall into the following cases.
- Access directly from home or a mobile network without going through a VPN
- Access from networks while traveling or working off-site
- Work at sites whose internet connections use different egress IP addresses
Ask these users to access AI-Starter through an allowed route, such as via the VPN.
3. Apply the WAF Settings
The IP restriction settings are part of the WAF template, so an infrastructure update is required to apply them. The update can be performed either by your account representative or by yourself. Your representative may provide the template or contact you about the update work.
Closing
Thank you for reading. This change strengthens the security foundation so that you can continue to use AI-Starter with confidence over the long term. We understand that some users may need to change how they connect, and we appreciate your understanding and cooperation. If you have any questions or requests, please reach out via Contact.