Apigee Terraform Modules

This repository provides terraform modules and ready to use end-to-end examples for Apigee.

Modules

Currently the following modules are a available and can be used either as part of the end-to-end examples or as part of your own scripting:

Apigee X Core Configures a complete Apigee X organization with multiple instances, environment groups, and environments.
Apigee X Bridge MIG Configures a managed instance group of network bridge GCE instances (VMs) that can be used as a load balancer backend and forward traffic to the internal Apigee X endpoint.
Apigee X mTLS MIG Configures a managed instance group of Envoy proxies that can be used to terminate mutual TLS and forward traffic to the internal Apigee X endpoint.
L7 external LB for MIG Configures an external HTTPS Cloud Load Balancer that fronts a managed instance groups.
Routing Appliance Configures a routing appliance and custom routes to overcome transitive peering problems.
HTTPbin Development Backend Configures an example HTTP backend based on a locally hosted httpbin.org service and an internal load balancer.
NIP.io Development Hostname Configures an external IP address and hostname based on the IP and the nip.io mechanism as well as a Google-managed SSL certificate.

Deploying End-To-End Samples

Set the project ID where you want your Apigee Organization to be deployed to:

PROJECT_ID=my-project-id

Select one of the available sample deployments:

X Basic for a basic Apigee X setup with the raw instance endpoints exposed as internal IP addresses.
X with external L7 LB for an Apigee X setup that is exposed via a global external L7 load balancer.
X with internal L4 LB and mTLS for a basic Apigee X setup plus exposure via regional L4 load balancer and envoy proxy to terminate mTLS.
X with network appliance for transitive peering for an Apigee X organization that is peered to a network is transitively peered to another VPC that contains the backend. To deploy the sample, first create a copy of the example variables and edit according to your requirements.
X with DNS peering for a basic Apigee X setup with DNS peering with a private DNS Zone containing records for Apigee and an example backend.

cd samples/... # Sample from above
cp ./x-demo.tfvars ./my-config.tfvars

Decide on a backend and create the necessary config. To use a backend on Google Cloud Storage (GCS) use:

gsutil mb "gs://$PROJECT_ID-tf"

cat <<EOF >terraform.tf
terraform {
  backend "gcs" {
    bucket  = "$PROJECT_ID-tf"
    prefix  = "terraform/state"
  }
}
EOF

Validate your config:

terraform init
terraform plan --var-file=./my-config.tfvars -var "project_id=$PROJECT_ID"

and provision everything (takes roughly 25min):

terraform apply --var-file=./my-config.tfvars -var "project_id=$PROJECT_ID"

Known issues

Currently, there are no known issues specific to this module.
Feel free to create an issue if you came across anything.
Please also see the list of open issues in the upstream terraform provider that could be inherited by this module.

License

All solutions within this repository are provided under the Apache 2.0 license. Please see the LICENSE file for more detailed terms and conditions.

Disclaimer