chore(apigateway): add TLS 1.3 security policies for domain names #36303
+82
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add four new TLS 1.3 security policy options to SecurityPolicy enum: * TLS13_1_3_2025_09 for regional/private APIs * TLS13_1_2_PQ_2025_09 with post-quantum cryptography support * TLS13_2025_EDGE for edge-optimized endpoints * TLS13_1_3_FIPS_2025_09 for FIPS compliance - Update multi-level base path validation to accept TLS 1.2 or higher instead of only TLS 1.2 - Add comprehensive documentation examples showing TLS 1.3 usage for both regional and edge-optimized APIs - Add test cases to verify TLS 1.3 policies are accepted and work with multi-level base paths - Update error message to reflect that TLS 1.2 or higher is required for multi-level base paths
github-actions
bot
added
effort/small
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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)
Closes #36280.
Reason for this change
AWS now recommends using enhanced TLS 1.3 security policies for API Gateway custom domain names, but the CDK
SecurityPolicyenum only includes legacyTLS_1_0andTLS_1_2options. Users cannot specify AWS-recommended security policies likeSecurityPolicy_TLS13_1_3_2025_09because the enum is restrictive.Description of changes
Expanded the
SecurityPolicyenum in@aws-cdk/aws-apigatewayto include four TLS 1.3 security policy options:TLS13_1_3_2025_09- Pure TLS 1.3 (AWS recommended)TLS13_1_2_PQ_2025_09- TLS 1.3 + 1.2 with post-quantum cryptographyTLS13_2025_EDGE- TLS 1.3 for edge-optimized endpointsTLS13_1_3_FIPS_2025_09- FIPS-compliant TLS 1.3Updated validation logic to allow TLS 1.2+ security policies for multi-level base path mappings (previously only allowed the legacy
TLS_1_2enum value).Added documentation examples showing how to use TLS 1.3 security policies for both regional and edge-optimized APIs.
Breaking Changes: None - this is a purely additive change. All existing code continues to work unchanged.
Describe any new or updated permissions being added
N/A - No IAM permissions or resource access changes.
Description of how you validated changes
accepts TLS 1.3 security policies- verifies CloudFormation template generationallows TLS 1.3 for multi-level base paths- verifies validation logic accepts TLS 1.3Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license