46f694be08
* wip * urlmaps * wip * tested * fix managed certificate names * simple HTTP and HTTPS examples * gce and hybrid neg examples * internet NEG example * serverless NEG and backend bucket examples * certificate example * fix example tests * remove stale test module * module test * adfs blueprint * add support for non-classic GLB and PSC NEGs * apigee blueprint * glb and cloud armor blueprint * deprecate non-working nginx reverse cluster * api gateway blueprint * tfdoc * fix top-level READMEs * switch to new tests * only/at most |
||
---|---|---|
.. | ||
function | ||
README.md | ||
diagram.png | ||
main.tf | ||
outputs.tf | ||
spec.yaml | ||
variables.tf |
README.md
Creating multi-region deployments for API Gateway
This tutorial shows you how to configure an HTTP(S) load balancer to enable multi-region deployments for API Gateway. For more details on how this set up work have a look at the article here.
The diagram below depicts the architecture that this blueprint sets up.
Running the blueprint
Clone this repository or open it in cloud shell, then go through the following steps to create resources:
terraform init
terraform apply -var project_id=my-project-id
Testing the blueprint
-
Copy the IP address returned as output
-
Execute the following command
curl -v http://<IP_ADDRESS>/hello
Once done testing, you can clean up resources by running terraform destroy
.
Variables
name | description | type | required | default |
---|---|---|---|---|
project_id | Identifier of the project. | string |
✓ | |
regions | List of regions to deploy the proxy in. | list(string) |
✓ | |
project_create | Parameters for the creation of the new project. | object({…}) |
null |
Outputs
name | description | sensitive |
---|---|---|
ip_address | The reserved global IP address. |