feat: document aux file upload for SSL/TLS certificates in NGINXaaS Console - #2207
Merged
Conversation
…onsole Allow passing certificates and keys via aux files.wq Includes a warning that this is not recommended for sensitive data and should only be used when other approaches are not suitable.
github-actions
Bot
added
the
documentation
JTorreG
reviewed
Aug 13, 2026
JTorreG
approved these changes
Aug 13, 2026
…cates-console.md Co-authored-by: Jon Torre <78599298+JTorreG@users.noreply.github.com>
travisamartin
approved these changes
Aug 13, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Proposed changes
Adds a new "Add certificates via aux files" section to the NGINXaaS Console SSL/TLS certificates page. Covers using Add File > Upload Auxiliary / other file in the configuration editor to upload certificate and key files, with a warning that this is not recommended for sensitive data and should only be used when the other certificate management approaches are not suitable.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩