forked from hashicorp/terraform-aws-vault-starter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathvariables.tf
65 lines (52 loc) · 1.56 KB
/
variables.tf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
variable "vpc_id" {
description = "VPC ID"
}
variable "allowed_inbound_cidrs" {
type = list(string)
description = "List of CIDR blocks to permit inbound Vault access from"
}
variable "vault_version" {
description = "Vault version"
}
variable "owner" {
description = "value of owner tag on EC2 instances"
}
variable "name_prefix" {
description = "prefix used in resource names"
}
variable "elb_internal" {
description = "make LB internal or external"
default = true
}
variable "key_name" {
description = "SSH key name for Vault instances"
}
variable "instance_type" {
default = "m5.large"
description = "Instance type for Vault instances"
}
variable "vault_nodes" {
default = "5"
description = "number of Vault instances"
}
variable "vault_cluster_version" {
default = "0.0.1"
description = "Custom Version Tag for Upgrade Migrations"
}
# The following CIDR blocks are being declared for subnets that
# must be created for the NAT gateway and lambda functions
# they are unlikely ton conflict with default subnets in
# default VPCs, but you should change these if you are using a custom
# VPC or have modified your default subnets configuration
variable "nat_gateway_subnet_cidr" {
description = "CIDR block for NAT gateway subnet"
default = "172.31.160.0/20"
}
variable "lambda_primary_subnet_cidr" {
description = "CIDR block for primary lambda subnet"
default = "172.31.128.0/20"
}
variable "lambda_secondary_subnet_cidr" {
description = "CIDR block for secondary lambda subnet"
default = "172.31.144.0/20"
}