AWS CloudFront
Last updated
Last updated
If your site is using Amazon CloudFront CDN you can use it to easily implement traffic split, delegating specific paths to be served by Glopal.
Select your existing CloudFront distribution that is serving content from your website domain.
On the Origin tab click the [Create origin] button and enter following details:
Origin domain: Protocol: HTTPS only HTTPS port: 443 Minimum Origin SSL protocol: TLSv1.2 Origin path: (empty) Name: Glopal
Under Add custom header section define one header: Name: X-Forwarded-Host Value:
Make sure to replace GLOPAL_HOSTNAME placeholder with the value you receive from Glopal, and to replace TARGET_HOSTNAME with the domain of your website, as set in the CloudFront distribution alternate domain name value.
On the Behaviors tab click the [Create behavior] button and enter following details:
Path pattern: PATH/*
Origin: Glopal
Compress objects automatically: Any (recommended: Yes)
Viewer protocol policy: Any (recommended: Redirect HTTP to HTTPS)
Allowed HTTP methods: GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE
Restrict viewer access: No
Cache policy: Caching disabled
Origin request policy: All viewer except Host header
Response header policy: (empty)
Make sure to replace PATH placeholder with the path you want to delegate to Glopal like “de”. It is important to end path pattern with the * to delegate all sub-pages in the prefix.
We recommend to use the trailing slash, requiring local sites to be visited as "https://example.com/de/" (with a slash). Omitting the slash and entering "de*" may conflict with your existing pages such as "https://example.com/delivery-options". If it is important to support URLs without a slash, add one behavior for PATH/* and another for just the PATH
Click the [Save changes] button.
To delegate multiple paths to Glopal, configure additional behaviors for each path prefix.
We recommend starting with cache policy "Caching disabled" allowing Glopal to setup your localized sites not worrying about clearing the cache as initial configuration and translations are created. Later, after the initial setup, you can choose to align cache policy with Glopal, having cache in your AWS CloudFront before requests are forwarded to Glopal to match performance of your existing site.
