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
Title: Add Support for Customer-managed Prefix Lists in the VPC Terraform Module
Feature Request: Customer-managed Prefix Lists
Summary
A managed prefix list is a collection of one or more CIDR blocks that simplifies the configuration and maintenance of security groups and route tables. It allows users to create a prefix list from frequently used IP addresses and reference them as a set in security group rules and routes, rather than individually. This streamlines the process of consolidating security group rules with varying CIDR blocks, but the same port and protocol, into a single rule that utilizes a prefix list. When it becomes necessary to allow traffic from an additional CIDR block, updating the relevant prefix list automatically updates all associated security groups.
There are two types of prefix lists:
Customer-managed prefix lists — User-defined and managed sets of IP address ranges. These can be shared with other AWS accounts, enabling them to reference the prefix list in their resources.
AWS-managed prefix lists — IP address ranges sets for AWS services, which cannot be created, modified, shared, or deleted by the user.
I propose adding support for customer-managed prefix lists in the VPC Terraform module. The AWS provider already includes a resource for handling this, which can be found in the Terraform AWS Provider documentation.
Rationale
After searching for alternative solutions, I have found none that provide the same level of convenience and flexibility as customer-managed prefix lists. Given the benefits of this feature and the availability of a corresponding resource in the AWS provider, I believe it would be a valuable addition to the VPC Terraform module.
Appreciation
I would like to express my gratitude for the exceptional work you have done in maintaining this project. Your dedication and contributions to the community have made a significant impact, and I sincerely appreciate your efforts. Thank you for considering my feature request and for your ongoing commitment to improving the VPC Terraform module.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Title: Add Support for Customer-managed Prefix Lists in the VPC Terraform Module
Feature Request: Customer-managed Prefix Lists
Summary
A managed prefix list is a collection of one or more CIDR blocks that simplifies the configuration and maintenance of security groups and route tables. It allows users to create a prefix list from frequently used IP addresses and reference them as a set in security group rules and routes, rather than individually. This streamlines the process of consolidating security group rules with varying CIDR blocks, but the same port and protocol, into a single rule that utilizes a prefix list. When it becomes necessary to allow traffic from an additional CIDR block, updating the relevant prefix list automatically updates all associated security groups.
There are two types of prefix lists:
More information on prefix lists can be found in the official AWS documentation.
Proposal
I propose adding support for customer-managed prefix lists in the VPC Terraform module. The AWS provider already includes a resource for handling this, which can be found in the Terraform AWS Provider documentation.
Rationale
After searching for alternative solutions, I have found none that provide the same level of convenience and flexibility as customer-managed prefix lists. Given the benefits of this feature and the availability of a corresponding resource in the AWS provider, I believe it would be a valuable addition to the VPC Terraform module.
Appreciation
I would like to express my gratitude for the exceptional work you have done in maintaining this project. Your dedication and contributions to the community have made a significant impact, and I sincerely appreciate your efforts. Thank you for considering my feature request and for your ongoing commitment to improving the VPC Terraform module.
The text was updated successfully, but these errors were encountered: