# Allowed Domains
<a name="allowed-domains"></a>

For WorkSpaces Applications users to access streaming instances, you must allow the following domain on the network from which users initiate access to the streaming instances.
+ Streaming Gateway: \$1.amazonappstream.com
**Note**  
Instead of using a wildcard to allowlist all streaming gateways, you can create a VPC endpoint and allowlist only that specific endpoint. For more information, see [WorkSpaces Applications Interface VPC Endpoints](interface-vpc-endpoints.md).

For IPV4 support, you must allow the following domain on the network from which users initiate access to the streaming instances. It is region based and follows the following format: `*.streaming.{region}.appstream2.amazonappstream.com` and `*.dcv-streaming.{region}.appstream2.amazonappstream.com`. If its a FIPS compliant region, it will also need another endpoint with the format `*.streaming.{region}.appstream2-fips.amazonappstream.com` and `*.dcv-streaming.{region}.appstream2-fips.amazonappstream.com`. Check table below.


| Region | Domain | 
| --- | --- | 
| US East (N. Virginia) |  \$1.streaming.us-east-1.appstream2.amazonappstream.com \$1.dcv-streaming.us-east-1.appstream2.amazonappstream.com \$1.streaming.us-east-1.appstream2-fips.amazonappstream.com \$1.dcv-streaming.us-east-1.appstream2-fips.amazonappstream.com  | 
| US East (Ohio) |  \$1.streaming.us-east-2.appstream2.amazonappstream.com \$1.dcv-streaming.us-east-2.appstream2.amazonappstream.com  | 
| US West (Oregon) |  \$1.streaming.us-west-2.appstream2.amazonappstream.com \$1.dcv-streaming.us-west-2.appstream2.amazonappstream.com \$1.streaming.us-west-2.appstream2-fips.amazonappstream.com \$1.dcv-streaming.us-west-2.appstream2-fips.amazonappstream.com  | 
| Asia Pacific (Mumbai) |  \$1.streaming.ap-south-1.appstream2.amazonappstream.com \$1.dcv-streaming.ap-south-1.appstream2.amazonappstream.com  | 
| Asia Pacific (Seoul) |  \$1.streaming.ap-northeast-2.appstream2.amazonappstream.com \$1.dcv-streaming.ap-northeast-2.appstream2.amazonappstream.com  | 
| Asia Pacific (Singapore) |  \$1.streaming.ap-southeast-1.appstream2.amazonappstream.com \$1.dcv-streaming.ap-southeast-1.appstream2.amazonappstream.com  | 
| Asia Pacific (Sydney) |  \$1.streaming.ap-southeast-2.appstream2.amazonappstream.com \$1.dcv-streaming.ap-southeast-2.appstream2.amazonappstream.com  | 
| Asia Pacific (Tokyo) |  \$1.streaming.ap-northeast-1.appstream2.amazonappstream.com \$1.dcv-streaming.ap-northeast-1.appstream2.amazonappstream.com  | 
| Canada (Central) |  \$1.streaming.ca-central-1.appstream2.amazonappstream.com \$1.dcv-streaming.ca-central-1.appstream2.amazonappstream.com  | 
| Europe (Frankfurt) |  \$1.streaming.eu-central-1.appstream2.amazonappstream.com \$1.dcv-streaming.eu-central-1.appstream2.amazonappstream.com  | 
| Europe (London) |  \$1.streaming.eu-west-2.appstream2.amazonappstream.com \$1.dcv-streaming.eu-west-2.appstream2.amazonappstream.com  | 
| Europe (Ireland) |  \$1.streaming.eu-west-1.appstream2.amazonappstream.com \$1.dcv-streaming.eu-west-1.appstream2.amazonappstream.com  | 
| Europe (Paris) |  \$1.streaming.eu-west-3.appstream2.amazonappstream.com \$1.dcv-streaming.eu-west-3.appstream2.amazonappstream.com  | 
| AWS GovCloud (US-East) |  \$1.streaming.us-gov-east-1.appstream2.amazonappstream.com \$1.dcv-streaming.us-gov-east-1.appstream2.amazonappstream.com \$1.streaming.us-gov-east-1.appstream2-fips.amazonappstream.com \$1.dcv-streaming.us-gov-east-1.appstream2-fips.amazonappstream.com  | 
| AWS GovCloud (US-West) |  \$1.streaming.us-gov-west-1.appstream2.amazonappstream.com \$1.dcv-streaming.us-gov-west-1.appstream2.amazonappstream.com \$1.streaming.us-gov-west-1.appstream2-fips.amazonappstream.com \$1.dcv-streaming.us-gov-west-1.appstream2-fips.amazonappstream.com  | 
| South America (São Paulo) |  \$1.streaming.sa-east-1.appstream2.amazonappstream.com \$1.dcv-streaming.sa-east-1.appstream2.amazonappstream.com  | 

For IPV6 support, you must allow the following domain on the network from which users initiate access to the streaming instances. It is region based and follows the following format: `*.streaming.appstream2.{region}.on.aws` and `*.dcv-streaming.appstream2.{region}.on.aws`. If its a FIPS compliant region, it will also need another endpoint with the format `*.streaming.appstream2-fips.{region}.on.aws` and `*.dcv-streaming.appstream2-fips.{region}.on.aws`. Check table below.

In order to use IPV6 address your base images must be updated to the images published on September 05, 2025 or later. For more information check [managed image updates](https://docs.aws.amazon.com/appstream2/latest/developerguide/keep-image-updated-managed-image-updates.html).


| Region | Domain | 
| --- | --- | 
| US East (N. Virginia) |  \$1.streaming.appstream2.us-east-1.on.aws \$1.dcv-streaming.appstream2.us-east-1.on.aws \$1.streaming.appstream2-fips.us-east-1.on.aws \$1.dcv-streaming.appstream2-fips.us-east-1.on.aws  | 
| US East (Ohio) |  \$1.streaming.appstream2.us-east-2.on.aws \$1.dcv-streaming.appstream2.us-east-2.on.aws  | 
| US West (Oregon) |  \$1.streaming.appstream2.us-west-2.on.aws \$1.dcv-streaming.appstream2.us-west-2.on.aws \$1.streaming.appstream2-fips.us-west-2.on.aws \$1.dcv-streaming.appstream2-fips.us-west-2.on.aws  | 
| Asia Pacific (Mumbai) |  \$1.streaming.appstream2.ap-south-1.on.aws \$1.dcv-streaming.appstream2.ap-south-1.on.aws  | 
| Asia Pacific (Seoul) |  \$1.streaming.appstream2.ap-northeast-2.on.aws \$1.dcv-streaming.appstream2.ap-northeast-2.on.aws  | 
| Asia Pacific (Singapore) |  \$1.streaming.appstream2.ap-southeast-1.on.aws \$1.dcv-streaming.appstream2.ap-southeast-1.on.aws  | 
| Asia Pacific (Sydney) |  \$1.streaming.appstream2.ap-southeast-2.on.aws \$1.dcv-streaming.appstream2.ap-southeast-2.on.aws  | 
| Asia Pacific (Tokyo) |  \$1.streaming.appstream2.ap-northeast-1.on.aws \$1.dcv-streaming.appstream2.ap-northeast-1.on.aws  | 
| Canada (Central) |  \$1.streaming.appstream2.ca-central-1.on.aws \$1.dcv-streaming.appstream2.ca-central-1.on.aws  | 
| Europe (Frankfurt) |  \$1.streaming.appstream2.eu-central-1.on.aws \$1.dcv-streaming.appstream2.eu-central-1.on.aws  | 
| Europe (London) |  \$1.streaming.appstream2.eu-west-2.on.aws \$1.dcv-streaming.appstream2.eu-west-2.on.aws  | 
| Europe (Ireland) |  \$1.streaming.appstream2.eu-west-1.on.aws \$1.dcv-streaming.appstream2.eu-west-1.on.aws  | 
| Europe (Paris) |  \$1.streaming.appstream2.eu-west-3.on.aws \$1.dcv-streaming.appstream2.eu-west-3.on.aws  | 
| AWS GovCloud (US-East) |  \$1.streaming.appstream2.us-gov-east-1.on.aws \$1.dcv-streaming.appstream2.us-gov-east-1.on.aws \$1.streaming.appstream2-fips.us-gov-east-1.on.aws \$1.dcv-streaming.appstream2-fips.us-gov-east-1.on.aws  | 
| AWS GovCloud (US-West) |  \$1.streaming.appstream2.us-gov-west-1.on.aws \$1.dcv-streaming.appstream2.us-gov-west-1.on.aws \$1.streaming.appstream2-fips.us-gov-west-1.on.aws \$1.dcv-streaming.appstream2-fips.us-gov-west-1.on.aws  | 
| South America (São Paulo) |  \$1.streaming.appstream2.sa-east-1.on.aws \$1.dcv-streaming.appstream2.sa-east-1.on.aws  | 

One or more of the following domains must be allowed to enable user authentication. You must allow the domains and subdomains that correspond to the Regions where WorkSpaces Applications is deployed. 


| Region | Domain | 
| --- | --- | 
| US East (N. Virginia) | \$1.appstream2.us-east-1.aws.amazon.com | 
| US East (Ohio) | \$1.appstream2.us-east-2.aws.amazon.com | 
| US West (Oregon) | \$1.appstream2.us-west-2.aws.amazon.com | 
| Asia Pacific (Malaysia) | \$1.appstream2.ap-southeast-5.aws.amazon.com | 
| Asia Pacific (Mumbai) | \$1.appstream2.ap-south-1.aws.amazon.com | 
| Asia Pacific (Seoul) | \$1.appstream2.ap-northeast-2.aws.amazon.com | 
| Asia Pacific (Singapore) | \$1.appstream2.ap-southeast-1.aws.amazon.com | 
| Asia Pacific (Sydney) | \$1.appstream2.ap-southeast-2.aws.amazon.com | 
| Asia Pacific (Tokyo) | \$1.appstream2.ap-northeast-1.aws.amazon.com | 
| Canada (Central) | \$1.appstream2.ca-central-1.aws.amazon.com | 
| Europe (Frankfurt) | \$1.appstream2.eu-central-1.aws.amazon.com | 
| Europe (London) | \$1.appstream2.eu-west-2.aws.amazon.com | 
| Europe (Ireland) | \$1.appstream2.eu-west-1.aws.amazon.com | 
| Europe (Milan) | \$1.appstream2.eu-south-1.aws.amazon.com | 
| Europe (Paris) | \$1.appstream2.eu-west-3.aws.amazon.com | 
| Europe (Spain) | \$1.appstream2.eu-south-2.aws.amazon.com | 
| AWS GovCloud (US-East) | \$1.appstream2.us-gov-east-1.amazonaws-us-gov.com | 
| AWS GovCloud (US-West) | \$1.appstream2.us-gov-west-1.amazonaws-us-gov.com | 
| South America (São Paulo) |  \$1.appstream2.sa-east-1.aws.amazon.com  | 
| Israel (Tel Aviv) | \$1.appstream2.il-central-1.aws.amazon.com | 

**Note**  
If your users use a network proxy to access streaming instances, disable any proxy caching for the user auth domains in the table and the session gateway, \$1.amazonappstream.com.

AWS publishes its current IP address ranges, including the ranges that the Session Gateway and CloudFront domains may resolve to, in JSON format. For information about how to download the .json file and view the current ranges, see [AWS IP Address Ranges](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html) in the Amazon Web Services General Reference. Or, if you are using AWS Tools for Windows PowerShell, you can access the same information by using the `Get-AWSPublicIpAddressRange` cmdlet. For more information, see [Querying the Public IP Address Ranges for AWS](https://aws.amazon.com/blogs/developer/querying-the-public-ip-address-ranges-for-aws/).

For WorkSpaces Applications users that are accessing Elastic fleets, you must allow access to the domain for the Amazon Simple Storage Service (S3) bucket that contains the application icon.

**Note**  
If your S3 bucket has a “.” character in the name, the domain used is https://s3.<AWS Region>.amazonaws.com. If your S3 bucket does not have a “.” character in the name, the domain used is https://<*bucket name*>.s3.<*AWS Region*>.amazonaws.com.