-
Notifications
You must be signed in to change notification settings - Fork 108
Add deploy-manage security landing page #703
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
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.
sounds like a nice start
deploy-manage/security.md
Outdated
| **Security feature** | Serverless | Elastic Cloud | ECE | ECK | Self-managed | | ||
|------------------|------------|--------------|-----|-----|--------------| | ||
| **Kibana Sessions** | ✓ Managed | ✓ Configurable | ✓ Configurable | ✓ Configurable | ✓ Configurable | |
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.
What's the diff between:
- Managed
- Available
- Manual
- Configurable
(Especially the last 3)
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.
Yeah I've tightened this up, thanks for pointing out:
Removed "Available" and "Manual", settled on:
- Fully managed by Elastic (Managed)
- Available but need setup (Configurable)
- Must be implemented by user (Self-managed)
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.
Does that make more sense?
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.
Configurable/self-managed practically mean the same thing, we could do simple and keep only configurable
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.
tried to clarify further in 8c136c9
Co-authored-by: florent-leborgne <[email protected]>
Co-authored-by: florent-leborgne <[email protected]>
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.
👍 for merge and iteration
## What is this? - Second cut at landing page for elastic/docs-projects#346, because the first draft started to disgust me almost immediately. - (first cut: #703) ## Summary - Intro rewrite - Replaced generic intro with specific bullet points explaining exactly what's on the page - Restructured security features section - Changed from vertical comparison tables to tab-based organization by deployment type - Security topics simplified - Cleaned up redundant descriptions in the four main security topic areas - Added "Next steps" section - New conclusion with clear paths to deployment-specific documentation - Removed "Using this documentation" section - Integrated essential guidance into a brief note under Security topics Consolidated ECE/ECK information - Combined identical deployment types to reduce redundancy --------- Co-authored-by: florent-leborgne <[email protected]>
Landing page for https://github.com/elastic/docs-projects/issues/346 --------- Co-authored-by: florent-leborgne <[email protected]>
## What is this? - Second cut at landing page for https://github.com/elastic/docs-projects/issues/346, because the first draft started to disgust me almost immediately. - (first cut: #703) ## Summary - Intro rewrite - Replaced generic intro with specific bullet points explaining exactly what's on the page - Restructured security features section - Changed from vertical comparison tables to tab-based organization by deployment type - Security topics simplified - Cleaned up redundant descriptions in the four main security topic areas - Added "Next steps" section - New conclusion with clear paths to deployment-specific documentation - Removed "Using this documentation" section - Integrated essential guidance into a brief note under Security topics Consolidated ECE/ECK information - Combined identical deployment types to reduce redundancy --------- Co-authored-by: florent-leborgne <[email protected]>
Landing page for https://github.com/elastic/docs-projects/issues/346