I read this http://docs.apigee.com/api-services/content/performance-and-availability-between-edge-and-aws which talks about "Performance and availability between Edge and AWS".
There's no easy way to check in which zone was my organization deployed, and the IP whitelisting link is unavailable.
What shall I do if I want to know or even change my zone?
Solved! Go to Solution.
Dear @Jay Peng,
Thanks,
Amar
The variable system.region.name holds the region name for where a request was handled. See variables reference here: http://docs.apigee.com/api-services/reference/variables-reference
The following policy will add a 'region' header to your responses containing the region name. Attach to the proxy postflow, for example.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <AssignMessage async="false" continueOnError="false" enabled="true" name="Set-Region-Header"> <DisplayName>Set Region Header</DisplayName> <Properties/> <Set> <Headers> <Header name="region">{system.region.name}</Header> </Headers> </Set> <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables> <AssignTo createNew="false" transport="http" type="response"/> </AssignMessage>
Here's a snap of what that looks like in trace:
To change your zone would require contacting Apigee Support and/or your sales team.
Dear @Jay Peng,
Thanks,
Amar
Apologies for the bad link, @Jay Peng. It's fixed now. Here it is:
http://docs.apigee.com/api-services/content/security-guidelines-between-edge-and-aws#whitelist
Thank you @Floyd Jones
The variable system.region.name holds the region name for where a request was handled. See variables reference here: http://docs.apigee.com/api-services/reference/variables-reference
The following policy will add a 'region' header to your responses containing the region name. Attach to the proxy postflow, for example.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <AssignMessage async="false" continueOnError="false" enabled="true" name="Set-Region-Header"> <DisplayName>Set Region Header</DisplayName> <Properties/> <Set> <Headers> <Header name="region">{system.region.name}</Header> </Headers> </Set> <IgnoreUnresolvedVariables>true</IgnoreUnresolvedVariables> <AssignTo createNew="false" transport="http" type="response"/> </AssignMessage>
Here's a snap of what that looks like in trace:
To change your zone would require contacting Apigee Support and/or your sales team.
I got the region by this policy.
That's a good example of AssignMessage policy and the use of variables.