docs: Add back suggested FIPS + TLS1.3 policy #4605
Merged
Conversation
This file contains 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
jmayclin
approved these changes
Jun 14, 2024
lrstewart
requested review from
goatgoose and
maddeleine
and removed request for
maddeleine
goatgoose
approved these changes
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolved issues:
Related to #4594
Description of changes:
#4598 is fairly tricky, so splitting this into a separate PR so we can update the documentation ASAP.
Before I updated the default policies, "20230317" was called out as a solid default with both TLS1.3 and FIPS support in our documentation. When I updated the defaults, I removed that documentation thinking that customers could now use the official defaults. However, we're still missing the FIPS + TLS1.3 use case because we ended up delaying TLS1.3 support.
Testing:
Just a doc change.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.