Cloudformation-coverage-roadmap: AWS::EC2::Route: support for DestinationPrefixListId

[mikeydowntown]

Looks like the CLI and SDKs supports defining a route destination as a prefix list however this is not yet implemented in CloudFormation and I see no evidence that this is planned. Is it? I see that it is implemented in the SecurityGroup resource type as property DestinationPrefixListId.

My use case is that I'm using CFN to create routes across a large number of route tables back to a common set CIDRs, targeted to new transit gateways, via multiple stacks in multiple regions and accounts. These CIDRs will eventually change so customer-managed prefix lists would be a very useful feature here but not practical for me to use if I cannot do so from my CloudFormation template, as I can do for properties such as DestinationCidrBlock.

[hugo-galindo]

We have a similar scenario ☝️ for a project. Would really appreciate DestinationPrefixListId Cloudformation support for AWS::EC2::Route. We have over 400 route tables to be updated and this would extremely beneficial to our automation process.

[terryrankine]

this

[datablitz7]

This seems like an oversight. Please implement this either as a separate property (e.g DestinationPrefixListId) or as a context sensitive one under the existing DestinationCidrBlock, similar to how it works for Security Group entries, where CidrIp can handle PrefixListId, SecurityGroupId or CIDR ranges. Either way, this is a major inconsistency that needs to be addressed.

[mfang329]

Concurred. Use Prefix lists to manage subnets are very beneficial but without the option to add it to the CFN route entry is a useless feature. I can manually add the Prefix lists manually the route entry to go around this issue, but it defeats the purpose in terms of the CFN automation.

[tmhccpeet]

bump

Anything being done about this yet?

[mquidi86]

I don't understand how something like this can take 1 year or more to be addressed.

[sbwrege2z]

I have a similar need to all those expressed here.