-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[DOCS] Add serverless details in Elasticsearch security privileges #109718
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Documentation preview: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ++ on documenting privilege availability here.
Left a comment around the behavioral
privileges (I can address it in a follow up PR). There are a couple more cluster privileges missing:
delegate_pki
manage_user_profile
monitor_data_frame_transform
<- this is deprecated anyhow. fine to leave outnone
- read/write connector/fleet secrets
I'll take an action item to add the ones that are worth adding in a follow up. Let me know if you had more changes planned here, otherwise I can give it one more review (this basically looks ready to merge from my perspective).
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-security (Team:Security) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Just a short note on a display glitch we gotta address, all good to merge without re-review though.
Relates to elastic/elasticsearch-specification#2491
This PR updates https://www.elastic.co/guide/en/elasticsearch/reference/current/security-privileges.html to call out the specific privileges that are not available in serverless projects.