fix(elasticache): security group for ServerlessCache
does not use default endpoint port
#35738
+331
−32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue # (if applicable)
N/A
Reason for this change
A security group ingress for the new
ServerlessCache
construct does not use an endpoint port.The following CDK code generates an INVALID CFn template with
null
forFromPort
andToPort
:An expected template:
FYI: The method
cache.connections.defaultPort?.toRuleJson()
outputs{"Value":{"ipProtocol":"tcp","fromPort":null,"toPort":null}}
. But we expect{"Value":{"ipProtocol":"tcp","fromPort":{"Fn::GetAtt":["Cache18F6EE16","Endpoint.Port"]},"toPort":{"Fn::GetAtt":["Cache18F6EE16","Endpoint.Port"]}}}
.Description of changes
Use
Token.asNumber
for thedefaultPort
ofConnections
inServerlessCache
:Describe any new or updated permissions being added
Description of how you validated changes
Both an unit test and an integ test.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license