You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| <aname="input_access_logs_s3_bucket_name"></a> [access\_logs\_s3\_bucket\_name](#input\_access\_logs\_s3\_bucket\_name)| The name to use for the S3 bucket where the NLB access logs will be stored. If you set this to null, a name will be generated automatically based on var.nlb\_name. |`string`|`null`| no |
26
+
| <aname="input_custom_nlb_access_logs_s3_prefix"></a> [custom\_nlb\_access\_logs\_s3\_prefix](#input\_custom\_nlb\_access\_logs\_s3\_prefix)| Prefix to use for access logs to create a sub-folder in S3 Bucket name where NLB logs should be stored. Only used if var.enable\_custom\_nlb\_access\_logs\_s3\_prefix is true. |`string`|`null`| no |
27
+
| <aname="input_enable_cross_zone_load_balancing"></a> [enable\_cross\_zone\_load\_balancing](#input\_enable\_cross\_zone\_load\_balancing)| Set enable\_cross\_zone\_load\_balancing |`bool`|`false`| no |
28
+
| <aname="input_enable_custom_nlb_access_logs_s3_prefix"></a> [enable\_custom\_nlb\_access\_logs\_s3\_prefix](#input\_enable\_custom\_nlb\_access\_logs\_s3\_prefix)| Set to true to use the value of nlb\_access\_logs\_s3\_prefix for access logs prefix. If false, the nlb\_name will be used. This is useful if you wish to disable the S3 prefix. Only used if var.enable\_nlb\_access\_logs is true. |`bool`|`false`| no |
29
+
| <aname="input_enable_deletion_protection"></a> [enable\_deletion\_protection](#input\_enable\_deletion\_protection)| Enable deletion protection |`bool`|`false`| no |
30
+
| <aname="input_enable_http2"></a> [enable\_http2](#input\_enable\_http2)| enable\_http2 |`bool`|`false`| no |
31
+
| <aname="input_enable_internal"></a> [enable\_internal](#input\_enable\_internal)| Enable internal load balancer |`bool`|`true`| no |
32
+
| <aname="input_enable_nlb_access_logs"></a> [enable\_nlb\_access\_logs](#input\_enable\_nlb\_access\_logs)| This is Optional, Only used to output the NLB logs to S3. we need to input bucket\_name and bucket\_prefix to the list. if left empty it will not output the logs to S3 |`list(any)`|`[]`| no |
33
+
| <aname="input_force_destroy"></a> [force\_destroy](#input\_force\_destroy)| A boolean that indicates whether the access logs bucket should be destroyed, even if there are files in it, when you run Terraform destroy. Unless you are using this bucket only for test purposes, you'll want to leave this variable set to false. |`bool`|`false`| no |
34
+
| <aname="input_nlb_access_logs_s3_bucket_name"></a> [nlb\_access\_logs\_s3\_bucket\_name](#input\_nlb\_access\_logs\_s3\_bucket\_name)| The S3 Bucket name where NLB logs should be stored. If left empty, no NLB logs will be captured. Tip: It's easiest to create the S3 Bucket using the Gruntwork Module https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/logs/load-balancer-access-logs.|`string`|`null`| no |
35
+
| <aname="input_nlb_access_logs_s3_prefix"></a> [nlb\_access\_logs\_s3\_prefix](#input\_nlb\_access\_logs\_s3\_prefix)| nlb\_access\_logs\_s3\_prefix |`string`|`null`| no |
36
+
| <aname="input_nlb_name"></a> [nlb\_name](#input\_nlb\_name)| The name of the NLB. Do not include the environment name since this module will automatically append it to the value of this variable. |`string`| n/a | yes |
37
+
| <aname="input_nlb_s3_bucket_name"></a> [nlb\_s3\_bucket\_name](#input\_nlb\_s3\_bucket\_name)| nlb\_s3\_bucket\_name |`string`|`null`| no |
| <aname="input_num_days_after_which_archive_log_data"></a> [num\_days\_after\_which\_archive\_log\_data](#input\_num\_days\_after\_which\_archive\_log\_data)| After this number of days, log files should be transitioned from S3 to Glacier. Enter 0 to never archive log data. |`number`| n/a | yes |
41
+
| <aname="input_num_days_after_which_delete_log_data"></a> [num\_days\_after\_which\_delete\_log\_data](#input\_num\_days\_after\_which\_delete\_log\_data)| After this number of days, log files should be deleted from S3. Enter 0 to never delete log data. |`number`| n/a | yes |
42
+
| <aname="input_should_create_access_logs_bucket"></a> [should\_create\_access\_logs\_bucket](#input\_should\_create\_access\_logs\_bucket)| If true, create a new S3 bucket for access logs with the name in var.access\_logs\_s3\_bucket\_name. If false, assume the S3 bucket for access logs with the name in var.access\_logs\_s3\_bucket\_name already exists, and don't create a new one. Note that if you set this to false, it's up to you to ensure that the S3 bucket has a bucket policy that grants Elastic Load Balancing permission to write the access logs to your bucket. |`bool`|`true`| no |
description="The name of the NLB. Do not include the environment name since this module will automatically append it to the value of this variable."
15
+
type=string
16
+
# AWS imposes a 32 character limit on the names of NLBs, so here we catch any overages client-side
17
+
validation {
18
+
condition=length(var.nlb_name) <=32
19
+
error_message="Your nlb_name must be 32 characters or less in length."
20
+
}
21
+
}
22
+
23
+
variable"enable_nlb_access_logs" {
24
+
description="This is Optional, Only used to output the NLB logs to S3. we need to input bucket_name and bucket_prefix to the list. if left empty it will not output the logs to S3"
25
+
type=list(any)
26
+
default=[]
27
+
}
28
+
29
+
variable"nlb_access_logs_s3_bucket_name" {
30
+
description="The S3 Bucket name where NLB logs should be stored. If left empty, no NLB logs will be captured. Tip: It's easiest to create the S3 Bucket using the Gruntwork Module https://github.com/gruntwork-io/terraform-aws-monitoring/tree/master/modules/logs/load-balancer-access-logs."
31
+
type=string
32
+
default=null
33
+
}
34
+
35
+
variable"custom_nlb_access_logs_s3_prefix" {
36
+
description="Prefix to use for access logs to create a sub-folder in S3 Bucket name where NLB logs should be stored. Only used if var.enable_custom_nlb_access_logs_s3_prefix is true."
description="Set to true to use the value of nlb_access_logs_s3_prefix for access logs prefix. If false, the nlb_name will be used. This is useful if you wish to disable the S3 prefix. Only used if var.enable_nlb_access_logs is true."
43
+
type=bool
44
+
default=false
45
+
}
46
+
47
+
variable"access_logs_s3_bucket_name" {
48
+
description="The name to use for the S3 bucket where the NLB access logs will be stored. If you set this to null, a name will be generated automatically based on var.nlb_name."
49
+
type=string
50
+
default=null
51
+
}
52
+
53
+
variable"should_create_access_logs_bucket" {
54
+
description="If true, create a new S3 bucket for access logs with the name in var.access_logs_s3_bucket_name. If false, assume the S3 bucket for access logs with the name in var.access_logs_s3_bucket_name already exists, and don't create a new one. Note that if you set this to false, it's up to you to ensure that the S3 bucket has a bucket policy that grants Elastic Load Balancing permission to write the access logs to your bucket."
55
+
type=bool
56
+
default=true
57
+
}
58
+
59
+
variable"num_days_after_which_archive_log_data" {
60
+
description="After this number of days, log files should be transitioned from S3 to Glacier. Enter 0 to never archive log data."
61
+
type=number
62
+
}
63
+
64
+
variable"num_days_after_which_delete_log_data" {
65
+
description="After this number of days, log files should be deleted from S3. Enter 0 to never delete log data."
66
+
type=number
67
+
}
68
+
69
+
variable"force_destroy" {
70
+
description="A boolean that indicates whether the access logs bucket should be destroyed, even if there are files in it, when you run Terraform destroy. Unless you are using this bucket only for test purposes, you'll want to leave this variable set to false."
0 commit comments