PoPs for Google Cloud Platform (GCP) customers
Citrix DaaS customers who have purchased subscriptions from the Google Cloud marketplace and are running their workloads on Google Cloud can use GCP PoPs.
Note:
It is recommended to configure firewalls and Secure Web Gateways as mentioned in System and Connectivity Requirements.
Support for PoPs in commercial regions
Support for PoPs in commercial regions for GCP customers is planned in the upcoming service release. With this support you can use the PoPs in commercial regions located across 5 continents. This support offers the following benefits:
-
Improved global access: Reduced latency and improved performance for the GCP users worldwide.
-
Greater flexibility: Choose the PoPs that best fit your needs and enhance cloud resiliency.
To use the PoPs in commercial regions, configure the firewall rules in VDA, Citrix Cloud Connector, and Citrix Workspace app (client) according to the following instructions:
-
Configure the firewall to establish connectivity between your resources and Citrix Cloud. For more information, see System and Connectivity Requirements.
-
Configure the firewall for Citrix Cloud Connector. For more information, see Citrix Cloud Connector proxy and firewall configuration.
-
Enable access to commercial region PoP FQDNs in Azure and AWS.
Global FQDNs with defined set of PoPs
Type | FQDN | Purpose |
---|---|---|
GCP only | gcp.g.nssvc.net | Global FQDN with GCP and commercial region PoPs |
Global | reg.c.nssvc.net | Connectors/VDA to register to Citrix Cloud |
PoP FQDNs
PoP code | PoP FQDN | Cloud service provider | Country | Location |
---|---|---|---|---|
gcp-us-sc | gcp-us-sc-rdvz.g.nssvc.net | GCP | USA | South Carolina |
gcp-sz-zu | gcp-sz-zu-rdvz.g.nssvc.net | GCP | Switzerland | Zurich |
gcp-us-la | gcp-us-la-rdvz.g.nssvc.net | GCP | USA | Los Angeles |
gcp-uk-ln | gcp-uk-ln-rdvz.g.nssvc.net | GCP | UK | London |
gcp-us-or | gcp-us-or-rdvz.g.nssvc.net | GCP | USA | The Dalles, Oregon |
az-asia-hk | az-asia-hk-rdvz.g.nssvc.net | Azure | Hong Kong | Hong Kong |
az-asia-se | az-asia-se-rdvz.g.nssvc.net | Azure | Singapore | Singapore |
az-aus-e | az-aus-e-rdvz.g.nssvc.net | Azure | Australia | New South Wales |
az-bz-s | az-bz-s-rdvz.g.nssvc.net | Azure | Brazil | Sao Paulo |
az-ca-c | az-ca-c-rdvz.g.nssvc.net | Azure | Canada | Toronto |
az-eu-n | az-eu-n-rdvz.g.nssvc.net | Azure | Ireland | Dublin |
az-eu-w | az-eu-w-rdvz.g.nssvc.net | Azure | Netherlands | Amsterdam |
az-in-s | az-in-s-rdvz.g.nssvc.net | Azure | India | Chennai |
az-jp-e | az-jp-e-rdvz.g.nssvc.net | Azure | Japan | Tokyo |
az-nw-e | az-nw-e-rdvz.g.nssvc.net | Azure | Norway | Oslo |
az-uae-n | az-uae-n-rdvz.g.nssvc.net | Azure | UAE | Dubai |
az-us-e | az-us-e-rdvz.g.nssvc.net | Azure | USA | Virginia |
az-us-sc | az-us-sc-rdvz.g.nssvc.net | Azure | USA | Texas |
az-us-w | az-us-w-rdvz.g.nssvc.net | Azure | USA | California |
az-za-n | az-za-n-rdvz.g.nssvc.net | Azure | South Africa | Johannesburg |
aws-aus-e | aws-aus-e-rdvz.g.nssvc.net | AWS | Australia | Sydney |
aws-bz-s | aws-bz-s-rdvz.g.nssvc.net | AWS | Brazil | Sao Paulo |
aws-ca-e | aws-ca-e-rdvz.g.nssvc.net | AWS | Canada | Montreal |
aws-eu-c | aws-eu-c-rdvz.g.nssvc.net | AWS | Germany | Frankfurt |
aws-in-w | aws-in-w-rdvz.g.nssvc.net | AWS | India | Mumbai |
aws-uk-se | aws-uk-se-rdvz.g.nssvc.net | AWS | UK | London |
aws-us-e | aws-us-e-rdvz.g.nssvc.net | AWS | USA | North Virginia |
aws-us-nc | aws-us-nc-rdvz.g.nssvc.net | AWS | USA | Ohio |
aws-us-w | aws-us-w-rdvz.g.nssvc.net | AWS | USA | North California |