Skip to content

Latest commit

 

History

History
74 lines (61 loc) · 5.08 KB

README.md

File metadata and controls

74 lines (61 loc) · 5.08 KB
Raw

opencbdc-tctl Environment

Configuration in this directory can be used to provision an environment mirroring that used in the paper.

Usage

  1. Complete the pre-provisioning steps. Please be sure that you are authenticated with AWS.
  2. Set appropriate values for inputs. These are mainly vars that will be specific to your environment. Each is defaulted to an empty string. You can overwrite the values directly in variables.tf or in another way of your choosing.
  3. Execute:
$ terraform init
$ terraform plan
$ terraform apply


WARNING This will create resources in your AWS account which will cost money. Be sure to run terraform destroy when you don't need these resources.
WARNING Running Terraform commands within this example configuration will create several files locally. Do not edit or delete these files until you have torn down the environment via terraform destroy. Terraform uses them to keep track of resources within your environment. Tampering them can put your enviornment in an inconsistent state.

Requirements

No requirements.

Providers

No providers.

Modules

Name Source Version
opencbdc_tctl ../../ n/a

Resources

No resources.

Inputs

Name Description Type Default Required
base_domain Base domain to use for ACM Cert and Route53 record management. string "" no
ec2_public_key SSH public key to use in EC2 instances. string "" no
environment AWS tag to indicate environment name of each infrastructure object. string "" no
lets_encrypt_email Email to associate with let's encrypt certificate string "" no
test_controller_github_access_token Access token for cloning test controller repo string "" no

Outputs

Name Description
azs_use1 Availability zones used by VPC located in us-east-1 region
azs_use2 Availability zones used by VPC located in us-east-2 region
azs_usw2 Availability zones used by VPC located in us-west-2 region
ecs_cluster_id ECS cluster id
ecs_cluster_name ECS cluster name
private_subnets_use1 Private subnet Ids associated with VPC in us-east-1 region
private_subnets_use2 Private subnet Ids associated with VPC in us-east-2 region
private_subnets_usw2 Private subnet Ids associated with VPC in us-west-2 region
public_subnets_use1 Public subnet Ids associated with VPC in us-east-1 region
public_subnets_use2 Public subnet Ids associated with VPC in us-east-2 region
public_subnets_usw2 Public subnet Ids associated with VPC in us-west-2 region
route53_endpoints Route53 endpoints generated by test controller services
s3_vpc_interface_endpoint_use1 S3 service interface endpoint asscoiated with VPC in us-east-1 region
s3_vpc_interface_endpoint_use2 S3 service interface endpoint asscoiated with VPC in us-east-2 region
s3_vpc_interface_endpoint_usw2 S3 service interface endpoint asscoiated with VPC in us-west-2 region
vpc_id_use1 Id of VPC in us-east-1 region
vpc_id_use2 Id of VPC in us-east-2 region
vpc_id_usw2 Id of VPC in us-west-2 region