AWS PrivateLink (Ingress)

You can use AWS PrivateLink to establish a private connection from your systems to Guidewire Cloud.

AWS PrivateLink provides private connections between AWS Virtual Private Clouds (VPCs), with no data transmitted over the public network. A private connection increases security and also reduces latency. Guidewire Cloud Platform supports inbound (Ingress) PrivateLink connections.
AWS PrivateLink (Ingress) architecture diagram

PrivateLink connections support accessing InsuranceSuite APIs from your AWS account as described in Cloud Platform.

To set up PrivateLink, first work with your AWS architects and solution partners. Working with AWS ensures that your PrivateLink solution is consistent with AWS best practices and standards. Once you are ready to set up PrivateLink, request provisioning using the Community Case Template Create New InsuranceSuite PrivateLink (Ingress) (TEN-0120) and then submit the request in Salesforce.

Note the following regarding using PrivateLink with Guidewire Cloud:
  • Your PrivateLink Endpoint must be in the same region as your application running in Guidewire Cloud.
  • You can have only one PrivateLink endpoint service per Guidewire Cloud quadrant.
  • Guidewire Cloud supports PrivateLink using only HTTPS (port 443).
  • You are responsible for DNS and routing on your VPC for requests going to Guidewire domains.
  • Guidewire provides only VPC endpoint services (ES), and does not provide any other network configuration to support PrivateLink connectivity.

For more information about AWS PrivateLink, see https://aws.amazon.com/privatelink.