Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 729f7d5

Browse files
authored
Updated Fastly shield locations (#5071)
Updated AWS region list for Fastly shield locations in the Backend settings section
1 parent c998cf1 commit 729f7d5

File tree

1 file changed

+17
-13
lines changed

1 file changed

+17
-13
lines changed

guides/v2.2/cloud/cdn/configure-fastly.md

Lines changed: 17 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -168,19 +168,23 @@ If you need to integrate additional backends into your site such as a backend to
168168
The following list shows which Fastly shield locations to use based an AWS
169169
region:
170170

171-
- ap-northeast-1 => tokyo-jp2
172-
- ap-southeast-1 => singapore-sg
173-
- ap-southeast-2 => sydney-au
174-
- ap-south-1 => singapore-sg
175-
- eu-central-1 => frankfurt-de
176-
- eu-west-1 => london-uk, london_city-uk
177-
- eu-west-2 => london-uk, london_city-uk
178-
- eu-west-3 => cdg-par-fr
179-
- sa-east-1 => gru-br-sa
180-
- us-east-1 => iad-va-us
181-
- us-east-2 => iad-va-us
182-
- us-west-1 => sjc-ca-us
183-
- us-west-2 => sea-wa-us
171+
- ap-east-1 => hongkong-hk
172+
- ap-northeast-1 => tyo-tokyo-jp, hnd-tokyo-jp
173+
- ap-northeast-2 => tyo-tokyo-jp, hnd-tokyo-jp
174+
- ap-southeast-1 => singapore-sg
175+
- ap-southeast-2 => sydney-au
176+
- ap-south-1 => singapore-sg
177+
- ca-central-1 => yul-montreal-ca, iad-va-us, dca-dc-us, bwi-va-us
178+
- eu-central-1 => frankfurt-de, hhn-frankfurt-de
179+
- eu-north-1 => stockholm-bma
180+
- eu-west-1 => london-uk, london_city-uk
181+
- eu-west-2 => london-uk, london_city-uk
182+
- eu-west-3 => cdg-par-fr
183+
- sa-east-1 => gru-br-sa
184+
- us-east-1 => iad-va-us, dca-dc-us, bwi-va-us
185+
- us-east-2 => iad-va-us, dca-dc-us, bwi-va-us
186+
- us-west-1 => sjc-ca-us, pao-ca-us
187+
- us-west-2 => sea-wa-us
184188

185189
1. Modify the timeout values (in microseconds) for the connection to the
186190
shield, time between bytes, and time for the first byte. We recommend keeping the default timeout settings.

0 commit comments

Comments
 (0)