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
|[aws_availability_zones.available](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/availability_zones)| data source |
214
221
|[aws_ec2_instance_type.arch](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/ec2_instance_type)| data source |
222
+
|[aws_route_tables.aws_private_routes](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/route_tables)| data source |
215
223
216
224
## Inputs
217
225
@@ -229,6 +237,7 @@ In this module, we have implemented the following CIS Compliance checks for VPC:
229
237
| <aname="input_existing_ipam_managed_cidr"></a> [existing\_ipam\_managed\_cidr](#input\_existing\_ipam\_managed\_cidr)| The existing IPAM pool CIDR |`string`|`""`| no |
230
238
| <aname="input_flow_log_cloudwatch_log_group_kms_key_arn"></a> [flow\_log\_cloudwatch\_log\_group\_kms\_key\_arn](#input\_flow\_log\_cloudwatch\_log\_group\_kms\_key\_arn)| The ARN of the KMS Key to use when encrypting log data for VPC flow logs |`string`|`null`| no |
231
239
| <aname="input_flow_log_cloudwatch_log_group_retention_in_days"></a> [flow\_log\_cloudwatch\_log\_group\_retention\_in\_days](#input\_flow\_log\_cloudwatch\_log\_group\_retention\_in\_days)| Specifies the number of days you want to retain log events in the specified log group for VPC flow logs. |`number`|`null`| no |
240
+
| <aname="input_flow_log_cloudwatch_log_group_skip_destroy"></a> [flow\_log\_cloudwatch\_log\_group\_skip\_destroy](#input\_flow\_log\_cloudwatch\_log\_group\_skip\_destroy)| Set to true if you do not wish the log group (and any logs it may contain) to be deleted at destroy time, and instead just remove the log group from the Terraform state |`bool`|`false`| no |
232
241
| <aname="input_flow_log_enabled"></a> [flow\_log\_enabled](#input\_flow\_log\_enabled)| Whether or not to enable VPC Flow Logs |`bool`|`false`| no |
233
242
| <aname="input_flow_log_max_aggregation_interval"></a> [flow\_log\_max\_aggregation\_interval](#input\_flow\_log\_max\_aggregation\_interval)| The maximum interval of time during which a flow of packets is captured and aggregated into a flow log record. Valid Values: `60` seconds or `600` seconds. |`number`|`60`| no |
234
243
| <aname="input_intra_subnet_assign_ipv6_address_on_creation"></a> [intra\_subnet\_assign\_ipv6\_address\_on\_creation](#input\_intra\_subnet\_assign\_ipv6\_address\_on\_creation)| Assign IPv6 address on intra subnet, must be disabled to change IPv6 CIDRs. This is the IPv6 equivalent of map\_public\_ip\_on\_launch |`bool`|`null`| no |
@@ -251,6 +260,8 @@ In this module, we have implemented the following CIS Compliance checks for VPC:
251
260
| <aname="input_secondary_cidr_blocks"></a> [secondary\_cidr\_blocks](#input\_secondary\_cidr\_blocks)| List of the secondary CIDR blocks which can be at most 5 |`list(string)`|`[]`| no |
252
261
| <aname="input_secondry_cidr_enabled"></a> [secondry\_cidr\_enabled](#input\_secondry\_cidr\_enabled)| Whether enable secondary CIDR with VPC |`bool`|`false`| no |
253
262
| <aname="input_vpc_cidr"></a> [vpc\_cidr](#input\_vpc\_cidr)| The CIDR block of the VPC |`string`|`"10.0.0.0/16"`| no |
263
+
| <aname="input_vpc_ecr_endpoint_enabled"></a> [vpc\_ecr\_endpoint\_enabled](#input\_vpc\_ecr\_endpoint\_enabled)| Set to true if you want to enable vpc ecr endpoints |`bool`|`false`| no |
264
+
| <aname="input_vpc_s3_endpoint_enabled"></a> [vpc\_s3\_endpoint\_enabled](#input\_vpc\_s3\_endpoint\_enabled)| Set to true if you want to enable vpc S3 endpoints |`bool`|`false`| no |
254
265
| <aname="input_vpn_key_pair_name"></a> [vpn\_key\_pair\_name](#input\_vpn\_key\_pair\_name)| Specify the name of AWS Keypair to be used for VPN Server |`string`|`""`| no |
255
266
| <aname="input_vpn_server_enabled"></a> [vpn\_server\_enabled](#input\_vpn\_server\_enabled)| Set to true if you want to deploy VPN Gateway resource and attach it to the VPC |`bool`|`false`| no |
256
267
| <aname="input_vpn_server_instance_type"></a> [vpn\_server\_instance\_type](#input\_vpn\_server\_instance\_type)| EC2 instance Type for VPN Server, Only amd64 based instance type are supported eg. t2.medium, t3.micro, c5a.large etc. |`string`|`"t3a.small"`| no |
description=" Set to true if you do not wish the log group (and any logs it may contain) to be deleted at destroy time, and instead just remove the log group from the Terraform state"
269
+
type=bool
270
+
default=false
271
+
}
272
+
273
+
variable"vpc_s3_endpoint_enabled" {
274
+
description="Set to true if you want to enable vpc S3 endpoints"
275
+
type=bool
276
+
default=false
277
+
}
278
+
279
+
variable"vpc_ecr_endpoint_enabled" {
280
+
description="Set to true if you want to enable vpc ecr endpoints"
0 commit comments