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_single_nat_gateway"></a> [single\_nat\_gateway](#input\_single\_nat\_gateway)| Should be true if you want to provision a single shared NAT Gateway across all of your private networks |`bool`|`false`| no |
582
585
| <aname="input_tags"></a> [tags](#input\_tags)| A map of tags to add to all resources |`map(string)`|`{}`| no |
583
586
| <aname="input_use_ipam_pool"></a> [use\_ipam\_pool](#input\_use\_ipam\_pool)| Determines whether IPAM pool is used for CIDR allocation |`bool`|`false`| no |
587
+
| <aname="input_vpc_block_public_access_exclusions"></a> [vpc\_block\_public\_access\_exclusions](#input\_vpc\_block\_public\_access\_exclusions)| A map of VPC block public access exclusions |`map(any)`|`{}`| no |
588
+
| <aname="input_vpc_block_public_access_options"></a> [vpc\_block\_public\_access\_options](#input\_vpc\_block\_public\_access\_options)| A map of VPC block public access options |`map(string)`|`{}`| no |
584
589
| <aname="input_vpc_flow_log_iam_policy_name"></a> [vpc\_flow\_log\_iam\_policy\_name](#input\_vpc\_flow\_log\_iam\_policy\_name)| Name of the IAM policy |`string`|`"vpc-flow-log-to-cloudwatch"`| no |
585
590
| <aname="input_vpc_flow_log_iam_policy_use_name_prefix"></a> [vpc\_flow\_log\_iam\_policy\_use\_name\_prefix](#input\_vpc\_flow\_log\_iam\_policy\_use\_name\_prefix)| Determines whether the name of the IAM policy (`vpc_flow_log_iam_policy_name`) is used as a prefix |`bool`|`true`| no |
586
591
| <aname="input_vpc_flow_log_iam_role_name"></a> [vpc\_flow\_log\_iam\_role\_name](#input\_vpc\_flow\_log\_iam\_role\_name)| Name to use on the VPC Flow Log IAM role created |`string`|`"vpc-flow-log-role"`| no |
@@ -699,6 +704,7 @@ No modules.
699
704
| <aname="output_vgw_arn"></a> [vgw\_arn](#output\_vgw\_arn)| The ARN of the VPN Gateway |
700
705
| <aname="output_vgw_id"></a> [vgw\_id](#output\_vgw\_id)| The ID of the VPN Gateway |
701
706
| <aname="output_vpc_arn"></a> [vpc\_arn](#output\_vpc\_arn)| The ARN of the VPC |
707
+
| <aname="output_vpc_block_public_access_exclusions"></a> [vpc\_block\_public\_access\_exclusions](#output\_vpc\_block\_public\_access\_exclusions)| A map of VPC block public access exclusions |
702
708
| <aname="output_vpc_cidr_block"></a> [vpc\_cidr\_block](#output\_vpc\_cidr\_block)| The CIDR block of the VPC |
703
709
| <aname="output_vpc_enable_dns_hostnames"></a> [vpc\_enable\_dns\_hostnames](#output\_vpc\_enable\_dns\_hostnames)| Whether or not the VPC has DNS hostname support |
704
710
| <aname="output_vpc_enable_dns_support"></a> [vpc\_enable\_dns\_support](#output\_vpc\_enable\_dns\_support)| Whether or not the VPC has DNS support |
Copy file name to clipboardExpand all lines: UPGRADE-3.0.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ If you find a bug, please open an issue with supporting configuration to reprodu
10
10
11
11
Previously, VPC endpoints were configured as standalone resources with their own set of variables and attributes. Now, this functionality is provided via a module which loops over a map of maps using `for_each` to generate the desired VPC endpoints. Therefore, to maintain the existing set of functionality while upgrading, you will need to perform the following changes:
12
12
13
-
1. Move the endpoint resource from the main module to the sub-module. The example state move below is valid for all endpoints you might have configured (reference [`complete-vpc`](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/complete-vpc) example for reference), where `ssmmessages` should be updated for and state move performed for each endpoint configured:
13
+
1. Move the endpoint resource from the main module to the sub-module. The example state move below is valid for all endpoints you might have configured (reference [`complete-vpc`](https://github.com/terraform-aws-modules/terraform-aws-vpc/tree/master/examples/complete) example for reference), where `ssmmessages` should be updated for and state move performed for each endpoint configured:
14
14
15
15
```
16
16
terraform state mv 'module.vpc.aws_vpc_endpoint.ssm[0]' 'module.vpc_endpoints.aws_vpc_endpoint.this["ssm"]'
0 commit comments