docs: Update Boundary licensing information #5999
Open
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
3 tasks
Comment on lines
77
to
96
| { | ||
| "id": "SJkaNV09xP", | ||
| "source": "https://hashicorp.com/boundary/nixos/controller+worker", | ||
| "specversion": "1.0", | ||
| "type": "error", | ||
| "data": { | ||
| "error": "error from licensing watcher: invalid license or license is expired", | ||
| "error_fields": {}, | ||
| "id": "e_33IKa8BqB3", | ||
| "version": "v0.1", | ||
| "op": "licensing.StartWatching" | ||
| }, | ||
| "datacontentype": "text/plain", | ||
| "time": "2025-08-01T16:54:14.34408533-07:00" | ||
| } | ||
| ==> Boundary dev environment self-terminating | ||
| ==> Health is enabled, waiting 0s before shutdown | ||
| ==> Boundary dev environment graceful shutdown triggered, interrupt again to enter shutdown | ||
| ``` |
There was a problem hiding this comment.
because this is a log message and not a code snippet, I don't think we need to enable the copy button
<CodeBlockConfig hideClipboard>
```plaintext
{
"id": "SJkaNV09xP",
"source": "https://hashicorp.com/boundary/nixos/controller+worker",
"specversion": "1.0",
"type": "error",
"data": {
"error": "error from licensing watcher: invalid license or license is expired",
"error_fields": {},
"id": "e_33IKa8BqB3",
"version": "v0.1",
"op": "licensing.StartWatching"
},
"datacontentype": "text/plain",
"time": "2025-08-01T16:54:14.34408533-07:00"
}
==> Boundary dev environment self-terminating
==> Health is enabled, waiting 0s before shutdown
==> Boundary dev environment graceful shutdown triggered, interrupt again to enter shutdown
There was a problem hiding this comment.
Thank you! Updated.
stellarsquall
approved these changes
Aug 25, 2025
lucymhdavies
reviewed
Sep 4, 2025
| Ongoing sessions continue to run, but you will not be able to create any new sessions. | ||
|
|
||
| Prior to the expiration date, Boundary logs 5 warnings to the event stream at the following intervals: |
There was a problem hiding this comment.
Are you able to provide an example of what that log looks like? That would be helpful for users to configure alerting on this, just in case.
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.
Description
Per SPE-1197, a customer had some questions about what happens when the Boundary Enterprise license expires. These included:
These scenarios were documented in the Vault docs, and the customer expected to find the information in the Boundary docs too.
This PR updates the Boundary Enterprise licensing documentation with more information about what happens in the scenarios listed above.
View the preview deployment
PCI review checklist
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.