AuthThe Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.AvailabilityExperimental since 9.5This functionality is experimental and is not ready for production usage. Experimental features may change or be removed at any time. Elastic will work to fix any issues, but experimental features are not subject to the support SLA of official GA features. Specific Support terms apply.Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Destroy the current project encryption key (PEK) and generate a new one.
This is the recovery path for when the on-disk encrypted PEK becomes permanently
inaccessible, for example because the key encryption material protecting it was lost.
All data that was encrypted under the destroyed key becomes permanently unrecoverable.
Each feature that stores encrypted data decides how to handle its own data during the
reset: some features drop the encrypted values entirely, while others preserve the rest
of the affected data and only clear the values that can no longer be decrypted.
Because this operation causes permanent data loss, it requires the accept_data_loss
query parameter to be set to true.
Acknowledge that resetting the project encryption key permanently destroys all data
that was encrypted under the current key.
The request fails if this is not set to true.
master_timeoutstring · default: 30s
The period to wait for a connection to the master node.
If no response is received before the timeout expires, the request fails and returns an error.
timeoutstring · default: 30s
The period to wait for a response.
If no response is received before the timeout expires, the request fails and returns an error.