Skip to content

f5devcentral/terraform-xc-aws-ce

Repository files navigation

Overview

Terraform templates to create F5XC AWS cloud CE (manual mode deployment).

Requirements

Name Version
terraform >= 1.3.0
curl >= 1.7
git >= 8.0
jq latest

OS Platform

Name Status
Linux supported
Mac OS (Sonoma) supported
Windows unsupported

Installation

Usage

  • Clone this repo with: git clone --recurse-submodules https://github.com/f5devcentral/terraform-xc-aws-ce
  • Enter repository directory with: cd terraform-xc-aws-ce
  • Follow usage description in topologies section
  • Multiple examples in example directory are available. Change to example directory that is to be deployed with cd examples/<example_dir_name>

Input variables

Description of available input variables. Used input variables will change per topology example:

Name Description
SLO Site local outside interface (external interface / egress interface)
SLI Site local inside interface (internal interface ( ingress interface)
owner Tag aws objects with creator / owner email address
project_prefix String added at the beginning of various AWS / F5 XC object identifier. <project_prefix>_<object>
project_suffix String added at the end of various AWS / F5 XC object identifier. <project_prefix>_<object>_<project_suffix>
Example prefix + suffix for F5XC site name project_prefix_cluster_name_project_suffix
f5xc_tenant Full f5 xc tenant name e.g. playground-abcdefg
f5xc_api_url F5 XC API URL e.g. https://playground.console.ves.volterra.io/api
f5xc_aws_region AWS region to deploy site in e.g. "us-west-2"
f5xc_cluster_name F5 XC cluster name e.g. "aws-ce-test"
f5xc_api_p12_file Path to F5 XC exported API cert file
f5xc_aws_availability_zone AWS availability zone to deploy object in
aws_existing_vpc_id Id of existing AWS VPC e.g. vpc-089de438436174ab7
aws_existing_sg_slo_ids SLO comma separated list of security group id strings e.g. ["id-1", "id-2", "id-3"]. Leave empty to omit injection
aws_existing_sg_sli_ids SLI comma separated list of security group id strings e.g. ["id-1", "id-2", "id-3"]. Leave empty to omit injection
aws_slo_subnet_id_nodeX Per node slo (outside interface) existing subnet id
aws_sli_subnet_id_nodeX Per node sli (inside interface) existing subnet id
aws_existing_key_pair_id Inject existing ssh key pair id
aws_existing_iam_profile_name Inject existing iam profile name

Topologies

Name Description
Single Node Single NIC new VPC / subnet Description
Single Node Multi NIC new VPC / subnet Description
Single Node Single NIC Existing VPC / new subnet Description
Single Node Multi NIC Existing VPC / new subnet Description
Single Node Single NIC existing VPC / subnet Description
Single Node Multi NIC existing VPC / subnet Description
Single Node Multi NIC existing VPC / new subnet with SLO no EIP / AWS NAT GW Description
Single Node Single NIC existing VPC / subnet and 3rd party NAT GW Description
Single Node Multi NIC existing VPC / subnet and 3rd party NAT GW Description
Single Node Appstack Cluster new VPC / subnet Description
Single Node Appstack Cluster existing VPC / new subnet Description
Three Node Cluster Single NIC new VPC / subnet Description
Three Node Cluster Single NIC existing VPC / new subnet Description
Three Node Cluster Single NIC existing VPC / subnet Description
Three Node Cluster Multi NIC new VPC / subnet Description
Three Node Cluster Multi NIC existing VPC / new subnet Description
Three Node Appstack Cluster new VPC / subnet Description
Three Node Appstack Cluster existing VPC / new subnet Description

Feature specific examples

Name Description
Single Node with offline survivability mode and l3 performance enhancement mode Description
Single Node single NIC new VPC and subnet with custom security group Description

ClickOps

Find CE cloud-config example for ClickOps deployment at Cloud-Config

Support

For support, please open a GitHub issue. Note, the code in this repository is community supported and is not supported by F5 Networks. For a complete list of supported projects please reference SUPPORT.md.

Community Code of Conduct

Please refer to the F5 DevCentral Community Code of Conduct.

License

Apache License 2.0

Copyright

Copyright 2014-2020 F5 Networks Inc.

F5 Networks Contributor License Agreement

Before you start contributing to any project sponsored by F5 Networks, Inc. (F5) on GitHub, you will need to sign a Contributor License Agreement (CLA).

If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise, by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.

If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.

If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.