Deploy and Manage: Elastic Cloud Enterprise Deploy #499
Conversation
deploy-manage/deploy/cloud-enterprise/deploy-an-orchestrator.md
Outdated
Show resolved
Hide resolved
| Try one of the [getting started guides](https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/getting-started-guides.html) to discover the core concepts of the Elastic Stack and understand how Elastic can help you. | ||
| :::: | ||
|
|
||
| ### What is ECE? |
There was a problem hiding this comment.
I think this heading, along with "Why ECE," can be removed, and their content can simply be part of the introduction. For example:
ECE has evolved from Elastic's hosted Cloud SaaS offering into a standalone product. You can deploy ECE on public or private clouds, virtual machines, or on-premises.
With Elastic Cloud Enterprise, you can:
- Host regulated or sensitive data on your internal network.
- Reuse your existing investment in on-premises infrastructure and reduce costs.
- Maximize hardware utilization across multiple clusters.
- Centralize the management of Elastic deployments across teams and geographies.
(or something similar)
There was a problem hiding this comment.
yeah, those sections don't look very natural. It was part of the original content. I'll review it, thanks!!
Co-authored-by: kosabogi <[email protected]>
Co-authored-by: kosabogi <[email protected]>
Co-authored-by: kosabogi <[email protected]>
| * [Deploy ECE](./cloud-enterprise/deploy-an-orchestrator.md) |
There was a problem hiding this comment.
might want to specify that this is the orchestrator / installation - this always confused me in the original doc
| Other sections of the documentation also include important tasks related to ECE: | ||
|
|
||
| * [Secure your ECE installation](../security/secure-your-elastic-cloud-enterprise-installation.md) |
There was a problem hiding this comment.
technically, the rest of the security section might be relevant as well (e.g. securing settings, saved objects?)
could call out the ece section specifically though
There was a problem hiding this comment.
Secure your ECE installation was a page in the original content with a lot of security related topics for ECE as chid docs. I hope to have something similar in the security section there.
It's true that I expect that to be focused on the orchestrator security and not on deployments security.
I'll add a link to the "secure your deployments" area which was https://www.elastic.co/guide/en/cloud-enterprise/current/ece-securing-clusters.html in the original docs. Thanks!
What I wouldn't do linking in the main page of ECE to something as specific as kibana saved objects, but if you share other examples that I might be missing please share!
For secure settings I expect them to be part of the security content mentioned previously.
|
|
||
| % Use migrated content from existing pages that map to this page: | ||
| % should we use a L2 heading here or just continue? |
|
|
||
| % What needs to be done: Refine | ||
| {{ece}} (ECE) is an Elastic self-managed solution for deploying, orchestrating, and managing {{es}} clusters at scale. It provides a centralized platform that allows organizations to run {{es}}, {{kib}}, and other {{stack}} components across multiple machines. |
There was a problem hiding this comment.
this page is missing the key info from the ECE overview below (the "why ECE")
| - https://www.elastic.co/guide/en/cloud-enterprise/current/Elastic-Cloud-Enterprise-overview.html | ||
| --- | ||
|
|
||
| # Elastic Cloud Enterprise overview [Elastic-Cloud-Enterprise-overview] |
There was a problem hiding this comment.
IMO I'd just pull this up a level because there's not that much stuff
I'd also just merge the service-oriented arch page and the services as docker containers page because they are overlapping
There was a problem hiding this comment.
this can wait for later though for time reasons
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
This is the first PR as part of the effort to refine all ECE content, per https://github.com/elastic/docs-projects/issues/339
Changes:
prepare your environmentmoved inside Deploy and Orchestrator.Pages to review:
ECE landing page.
ECE overview (with childs, almost untouched). This is a new page, we could include all this content in the landing page but i think it won't be better.
Deploy an orchestrator
Configure ECE: I have only brought here the content from the mapped documents. This will need refinement, let's get some feedback about this but the focus on this content will be in the next PR.
Note that the links that appear in Additional topics are duplicated in the Deployan orgrestrator and the main landing page. I'd like to get feedback about if this is ok or if we shouldn' link to those external sections in both places (security, snapshots, license, maintenance, user and roles)
cc: @shainaraskas