cloudformation-coverage-roadmap
cloudformation-coverage-roadmap copied to clipboard
aws-cloudformation
AWS::EC2::Route support for DestinationPrefixListId
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.
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.
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.
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.
I don't understand how something like this can take 1 year or more to be addressed.
Definitely need this feature. My template to deploy transit gateway, including all the routing, is made unnecessarily complex because I can't route to a prefix list.
So disappointed that there is yet another feature without full support in CloudFormation before being launched. Complete lack of shock that it's still not implemented over a year after it being pointed out that it's missing.
If you're not using CDK this could also apply but you'd have to bake your own CustomResource provider lambda to suit..
Otherwise those of us who use the unstoppable, incredible and amazing AWS CDK: 👌🏼😎🚀🙏🙌
The workaround right now that allows one to keep the infrastructure orchestration and resource building within the stack management and not need an external post script or similar is to use the AWSCustomResource and call the JS SDK CreateRoute with the minimum required params (RouteTableId, DestinantionPrefixListId plus whatever the target is: gateway, endpoint, interface etc)
This is actually what the definition of the what the CustomResource exists for; to fulfil any resource provisioning etc that isn't available natively in CFN constructs.
This is what we use and it's really very cool and effective 🔥🚀
And p.s. I wholeheartedly agree with all of you above that this should be naturally supported as an accepted value to cidrIp or as a standalone param to support PLs. However, for reasons beyond comprehension this is not the case yet, and thus we are forced to innovate, evolve and adapt 👌🏼😎🙏🚀 #spacexFTW
Similarly, this ought to be supported by AWS::EC2::TransitGatewayRoute which also support creating routes to prefix lists via console and CLI.
This issue is yet to be resolved and is a very frustrating experience.
Bumping. It doesn't make sense that we can create a PrefixList resource in CF but not use it in routes. This is a gap that should have already been resolved.
Any progress on this? Seems like low hanging fruit, easy to implement and a huge benefit.
Let's be honest, CloudFormation is for 🦖 🦕 's..
It's time to drop that pseudo-IaC rubbish and move to a real IaC framework..
For example: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/route.html#destination_prefix_list_id
And you can use it with https://developer.hashicorp.com/terraform/cdktf , so it's a WIN WIN! marriage of two superpowers! 😍 🚀
