Skip to content

docs: Small doc changes for KTLS#5521

Merged
maddeleine merged 5 commits intoaws:mainfrom
maddeleine:ktls_doc_updates
Sep 24, 2025
Merged

docs: Small doc changes for KTLS#5521
maddeleine merged 5 commits intoaws:mainfrom
maddeleine:ktls_doc_updates

Conversation

@maddeleine
Copy link
Copy Markdown
Contributor

Release Summary:

Resolved issues:

Description of changes:

We now support key updates with our ktls feature(after this is merged), so the docs should reflect that.

Call-outs:

Ended up being a smaller change than I expected, but I'm not sure more edits are needed.

Testing:

doc change.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

* Additionally, an application must not use kTLS to attempt to send more than 35GB
* of data and must not call s2n_send more than 23 million times. If either of these
* limits is exceeded, it will report an S2N_ERR_KTLS_KEY_LIMIT S2N_ERR_T_PROTO error.
* @note Calling this API will force a limit of 388 GB per s2n_send/sendfile call.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe mention that exceeding this limit will cause an INVALID_ARGUMENT error?

I'm also curious how the 388 GB is calculated 🤔 Could you add a note in the PR description?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh we might also want to mention that the limit isn't permanent / unavoidable. Like, if a customer reaches out, we could get rid of the limit. Maybe create a tracking issue and link that?

Copy link
Copy Markdown
Contributor Author

@maddeleine maddeleine Sep 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the calculation isn't something that users need to know about, so I didn't put it in our public docs. But yes, I amended an internal code comment to describe where this limit comes from.

Also yeah I created a tracking issue. If someone wants this, they can complain there.

Co-authored-by: Lindsay Stewart <stewart.r.lindsay@gmail.com>
@maddeleine maddeleine added this pull request to the merge queue Sep 24, 2025
Merged via the queue into aws:main with commit 29d0784 Sep 24, 2025
50 checks passed
@maddeleine maddeleine deleted the ktls_doc_updates branch September 24, 2025 23:52
dougch pushed a commit to dougch/s2n-tls that referenced this pull request Sep 26, 2025
Co-authored-by: Lindsay Stewart <stewart.r.lindsay@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants