I'm trying to set an optional parameter in my CloudFormation template but facing issues. Specifically, I'm attempting to use an `AWS::EC2::SecurityGroup::Id` parameter with a default value of an empty string. However, CloudFormation throws an error when I try to deploy it. I can bypass the problem by using `Type: String`, but it feels like a design flaw. Is it really intended that AWS-specific types can't be optional while basic types can? Plus, I'm confused about why all parameter values are treated as strings behind the scenes, using an empty string instead of `null` for omitted values. Does anyone know the reasoning behind this choice? I'm also using conditions based on the parameter, which works fine with the string type, but causes a validation error when I attempt to use `AWS::EC2::SecurityGroup::Id` without passing a value.
1 Answer
It sounds like you’re hitting a limitation that's pretty common with AWS CloudFormation. Unfortunately, I also haven't found a way to set optional parameters with AWS-specific types without defaulting to String. It's frustrating because it feels like they could have supported it better. I'm curious to see if anyone has come up with a clever workaround for this!
I've always ended up using String types too. I agree, it's a bummer that we can't have the flexibility with AWS-specific types. I hope someone figures it out soon!