[D&M] Clean up Deploy Elastic Cloud surface pages + Elastic Cloud Hosted

deploy-manage/deploy/elastic-cloud.md

@@ -1,44 +1,42 @@
 ---
+applies_to:
+  serverless: ga
+  deployment:
+    ess: ga
 mapped_pages:
   - https://www.elastic.co/guide/en/serverless/current/intro.html#general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud
 ---
 
 # Elastic Cloud [intro]
 
-{{serverless-full}} is a fully managed solution that allows you to deploy and use Elastic for your use cases without managing the underlying infrastructure. It represents a shift in how you interact with {{es}} - instead of managing clusters, nodes, data tiers, and scaling, you create **serverless projects** that are fully managed and automatically scaled by Elastic. This abstraction of infrastructure decisions allows you to focus solely on gaining value and insight from your data.
+{{ecloud}} allows you to centrally manage [hosted deployments](elastic-cloud/cloud-hosted.md) of the {{stack}} and [serverless projects](elastic-cloud/serverless.md) for your Observability, Security, and Search use cases. 
 
-{{serverless-full}} automatically provisions, manages, and scales your {{es}} resources based on your actual usage. Unlike traditional deployments where you need to predict and provision resources in advance, serverless adapts to your workload in real-time, ensuring optimal performance while eliminating the need for manual capacity planning.
+These hosted deployments and serverless projects are hosted on Elastic Cloud, through the cloud provider and regions of your choice, and are tied to your organization account.
 
-Serverless projects use the core components of the {{stack}}, such as {{es}} and {{kib}}, and are based on an architecture that decouples compute and storage. Search and indexing operations are separated, which offers high flexibility for scaling your workloads while ensuring a high level of performance.
+You can check the operational status of {{ecloud}} at any time from [status.elastic.co](https://status.elastic.co/).
 
-Elastic provides three serverless solutions available on {{ecloud}}:
+## Sign up
 
-* **/solutions/search.md[{{es-serverless}}]**: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries.
-% See solutions/search/serverless-elasticsearch-get-started.md
-* **/solutions/observability.md[{{obs-serverless}}]**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data.
-* **/solutions/security/elastic-security-serverless.md[{{sec-serverless}}]**: Detect, investigate, and respond to threats with SIEM, endpoint protection, and AI-powered analytics capabilities.
+You can get started by creating an {{ecloud}} organization on [cloud.elastic.co](https://cloud.elastic.co/registration).
 
-[Learn more about {{serverless-full}} in our blog](https://www.elastic.co/blog/elastic-cloud-serverless).
+For more details on the available sign up options and trial information, go to [](elastic-cloud/create-an-organization.md).
 
+## Benefits of {{ecloud}}
 
-## Benefits of serverless projects [_benefits_of_serverless_projects]
+Some of the unique benefits of {{ecloud}} include:
 
-**Management free.** Elastic manages the underlying Elastic cluster, so you can focus on your data. With serverless projects, Elastic is responsible for automatic upgrades, data backups, and business continuity.
+- Regular updates and improvements automatically deployed or made available.
+- Built-in security, including encryption at rest.
+- Central management of billing and licensing.
+- Built-in tools for monitoring and scaling your {{ecloud}} resources.
+- Central management of users, roles, and authentication, including integration with SSO providers.
 
-**Autoscaled.** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end.
+For more information, refer to [](/deploy-manage/cloud-organization.md).
 
-**Optimized data storage.** Your data is stored in cost-efficient, general storage. A cache layer is available on top of the general storage for recent and frequently queried data that provides faster search speed. The size of the cache layer and the volume of data it holds depend on [settings](elastic-cloud/project-settings.md) that you can configure for each project.
+## Differences between serverless projects and hosted deployments[general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud]
 
-**Dedicated experiences.** All serverless solutions are built on the Elastic Search Platform and include the core capabilities of the Elastic Stack. They also each offer a distinct experience and specific capabilities that help you focus on your data, goals, and use cases.
+You can have multiple hosted deployments and serverless projects in the same {{ecloud}} organization, and each deployment type has its own specificities.
 
-**Pay per usage.** Each serverless project type includes product-specific and usage-based pricing.
-
-**Data and performance control**. Control your project data and query performance against your project data. * Data. Choose the data you want to ingest and the method to ingest it. By default, data is stored indefinitely in your project, and you define the retention settings for your data streams. * Performance. For granular control over costs and query performance against your project data, serverless projects come with a set of predefined settings you can edit.
-
-
-## Differences between serverless projects and hosted deployments on {{ecloud}} [general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud]
-
-You can run [hosted deployments](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) of the {{stack}} on {{ecloud}}. These hosted deployments provide more provisioning and advanced configuration options.
 
 |     |     |     |
 | --- | --- | --- |
@@ -54,39 +52,8 @@ You can run [hosted deployments](/deploy-manage/deploy/elastic-cloud/cloud-hoste
 | **Backups** | Projects automatically backed up by Elastic. | Your responsibility with Snapshot & Restore. |
 | **Data retention** | Editable on data streams. | Index Lifecycle Management. |
 
+## APIs
 
-## Answers to common serverless questions [general-what-is-serverless-elastic-answers-to-common-serverless-questions]
-
-**Is there migration support between hosted deployments and serverless projects?**
-
-Migration paths between hosted deployments and serverless projects are currently unsupported.
-
-**How can I move data to or from serverless projects?**
-
-We are working on data migration tools! In the interim, [use Logstash](asciidocalypse://docs/logstash/docs/reference/ingestion-tools/logstash/index.md) with Elasticsearch input and output plugins to move data to and from serverless projects.
-
-**How does serverless ensure compatibility between software versions?**
-
-Connections and configurations are unaffected by upgrades. To ensure compatibility between software versions, quality testing and API versioning are used.
-
-**Can I convert a serverless project into a hosted deployment, or a hosted deployment into a serverless project?**
-
-Projects and deployments are based on different architectures, and you are unable to convert.
-
-**Can I convert a serverless project into a project of a different type?**
-
-You are unable to convert projects into different project types, but you can create as many projects as you’d like. You will be charged only for your usage.
-
-**How can I create serverless service accounts?**
-
-Create API keys for service accounts in your serverless projects. Options to automate the creation of API keys with tools such as Terraform will be available in the future.
-
-To raise a Support case with Elastic, raise a case for your subscription the same way you do today. In the body of the case, make sure to mention you are working in serverless to ensure we can provide the appropriate support.
-
-**Where can I learn about pricing for serverless?**
-
-See serverless pricing information for [Search](https://www.elastic.co/pricing/serverless-search), [Observability](https://www.elastic.co/pricing/serverless-observability), and [Security](https://www.elastic.co/pricing/serverless-security).
-
-**Can I request backups or restores for my projects?**
+{{ecloud}} offers APIs to manage your organization and its resources. Check the [{{ecloud}}](https://www.elastic.co/docs/api/doc/cloud/) and [{{ecloud}} serverless](https://www.elastic.co/docs/api/doc/elastic-cloud-serverless/) APIs.
 
-It is not currently possible to request backups or restores for projects, but we are working on data migration tools to better support this.
+More tools are available for you to make the most of your {{ecloud}} organization and {{es}}. Refer to [](/deploy-manage/deploy/elastic-cloud/tools-apis.md).

deploy-manage/deploy/elastic-cloud/access-kibana.md

@@ -1,11 +1,14 @@
 ---
+applies_to:
+  deployment:
+    ess: ga
 mapped_urls:
   - https://www.elastic.co/guide/en/cloud/current/ec-access-kibana.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-access-kibana.html
   - https://www.elastic.co/guide/en/cloud-heroku/current/ech-enable-kibana2.html
 ---
 
-# Access Kibana
+# Access Kibana [ec-access-kibana]
 
 % What needs to be done: Lift-and-shift
 
@@ -20,8 +23,29 @@ mapped_urls:
 
 $$$ec-enable-kibana2$$$
 
-**This page is a work in progress.** The documentation team is working to combine content pulled from the following pages:
 
-* [/raw-migrated-files/cloud/cloud/ec-access-kibana.md](/raw-migrated-files/cloud/cloud/ec-access-kibana.md)
-* [/raw-migrated-files/cloud/cloud-heroku/ech-access-kibana.md](/raw-migrated-files/cloud/cloud-heroku/ech-access-kibana.md)
-* [/raw-migrated-files/cloud/cloud-heroku/ech-enable-kibana2.md](/raw-migrated-files/cloud/cloud-heroku/ech-enable-kibana2.md)
+Kibana is an open source analytics and visualization platform designed to search, view, and interact with data stored in Elasticsearch indices. The use of Kibana is included with your subscription.
+
+For new Elasticsearch clusters, we automatically create a Kibana instance for you.
+
+To access Kibana:
+
+1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
+2. On the **Deployments** page, select your deployment.
+
+    On the deployments page you can narrow your deployments by name, ID, or choose from several other filters. To customize your view, use a combination of filters, or change the format from a grid to a list.
+
+3. Under **Applications**, select the Kibana **Launch** link and wait for Kibana to open.
+
+    ::::{note} 
+    Both ports 443 and 9243 can be used to access Kibana. SSO only works with 9243 on older deployments, where you will see an option in the Cloud UI to migrate the default to port 443. In addition, any version upgrade will automatically migrate the default port to 443.
+    ::::
+
+4. Log into Kibana. Single sign-on (SSO) is enabled between your Cloud account and the Kibana instance. If you’re logged in already, then Kibana opens without requiring you to log in again. However, if your token has expired, choose from one of these methods to log in:
+
+    * Select **Login with Cloud**. You’ll need to log in with your Cloud account credentials and then you’ll be redirected to Kibana.
+    * Log in with the `elastic` superuser. The password was provided when you created your cluster or [can be reset](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-users.md).
+    * Log in with any users you created in Kibana already.
+
+
+In production systems, you might need to control what Elasticsearch data users can access through Kibana, so you need create credentials that can be used to access the necessary Elasticsearch resources. This means granting read access to the necessary indexes, as well as access to update the `.kibana` index.

deploy-manage/deploy/elastic-cloud/add-plugins-extensions.md

@@ -1,6 +1,10 @@
 ---
+applies_to:
+  deployment:
+    ess: ga
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-adding-plugins.html
+  - https://www.elastic.co/guide/en/cloud-heroku/current/ech-adding-elastic-plugins.html
 ---
 
 # Add plugins and extensions [ec-adding-plugins]
@@ -13,16 +17,16 @@ Plugins extend the core functionality of {{es}}. There are many suitable plugins
 
 Plugins can come from different sources: the official ones created or at least maintained by Elastic, community-sourced plugins from other users, and plugins that you provide. Some of the official plugins are always provided with our service, and can be [enabled per deployment](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md).
 
-There are two ways to add plugins to a deployment in Elasticsearch Service:
+There are two ways to add plugins to a hosted deployment in {{ecloud}}:
 
-* [Enable one of the official plugins already available in Elasticsearch Service](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md).
+* [Enable one of the official plugins already available in {{ecloud}}](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/cloud/ec-adding-elastic-plugins.md).
 * [Upload a custom plugin and then enable it per deployment](upload-custom-plugins-bundles.md).
 
-Custom plugins can include the official {{es}} plugins not provided with Elasticsearch Service, any of the community-sourced plugins, or [plugins that you write yourself](asciidocalypse://docs/elasticsearch/docs/extend/create-elasticsearch-plugins/index.md). Uploading custom plugins is available only to Gold, Platinum, and Enterprise subscriptions. For more information, check [Upload custom plugins and bundles](upload-custom-plugins-bundles.md).
+Custom plugins can include the official {{es}} plugins not provided with {{ecloud}}, any of the community-sourced plugins, or [plugins that you write yourself](asciidocalypse://docs/elasticsearch/docs/extend/create-elasticsearch-plugins/index.md). Uploading custom plugins is available only to Gold, Platinum, and Enterprise subscriptions. For more information, check [Upload custom plugins and bundles](upload-custom-plugins-bundles.md).
 
 To learn more about the official and community-sourced plugins, refer to [{{es}} Plugins and Integrations](asciidocalypse://docs/elasticsearch/docs/reference/elasticsearch-plugins/index.md).
 
-For a detailed guide with examples of using the Elasticsearch Service API to create, get information about, update, and delete extensions and plugins, check [Managing plugins and extensions through the API](manage-plugins-extensions-through-api.md).
+For a detailed guide with examples of using the {{ecloud}} API to create, get information about, update, and delete extensions and plugins, check [Managing plugins and extensions through the API](manage-plugins-extensions-through-api.md).
 
 Plugins are not supported for {{kib}}. To learn more, check [Restrictions for {{es}} and {{kib}} plugins](restrictions-known-problems.md#ec-restrictions-plugins).
 

deploy-manage/deploy/elastic-cloud/available-stack-versions.md

@@ -1,11 +1,14 @@
 ---
+applies_to:
+  deployment:
+    ess: ga
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud/current/ec-version-policy.html
 ---
 
 # Available stack versions [ec-version-policy]
 
-This section describes our version policy for Elasticsearch Service, including:
+This section describes our version policy for {{ech}}, including:
 
 * [What Elastic Stack versions are available](#ec-version-policy-available)
 * [When we make new Elastic Stack versions available](#ec-version-policy-new)
@@ -18,7 +21,7 @@ This section describes our version policy for Elasticsearch Service, including:
 
 Elastic Stack uses a versions code that is constructed of three numbers separated by dots: the leftmost number is the number of the major release, the middle number is the number of the minor release and the rightmost number is the number of the maintenance release (e.g., 8.3.2 means major release 8, minor release 3 and maintenance release 2).
 
-You might sometimes notice additional versions listed in the user interface beyond the versions we currently support and maintain, such as [release candidate builds](#ec-release-builds) and older versions. If a version is listed in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body), it can be deployed.
+You might sometimes notice additional versions listed in the user interface beyond the versions we currently support and maintain, such as [release candidate builds](#ec-release-builds) and older versions. If a version is listed in the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body), it can be deployed.
 
 
 ## New Elastic Stack versions [ec-version-policy-new]
@@ -44,7 +47,7 @@ A forced upgrade or restart might become necessary in a situation that:
 
 ## Release candidates and cutting-edge releases [ec-release-builds]
 
-Interested in kicking the tires of Elasticsearch releases at the cutting edge? We sometimes make release candidate builds and other cutting-edge releases available in Elasticsearch Service for you to try out.
+Interested in kicking the tires of Elasticsearch releases at the cutting edge? We sometimes make release candidate builds and other cutting-edge releases available in {{ecloud}} for you to try out.
 
 ::::{warning}
 Remember that cutting-edge releases are used to test new function fully. These releases might still have issues and might be less stable than the GA version. There’s also no guaranteed upgrade path to the GA version when it becomes available.
@@ -58,4 +61,4 @@ Cutting-edge releases do not remain available forever. Once the GA version of El
 
 ## Version Policy and Product End of Life [ec-version-policy-eol]
 
-For Elasticsearch Service, we follow the [Elastic Version Maintenance and Support Policy](https://www.elastic.co/support/eol), which defines the support and maintenance policy of the Elastic Stack.
+For {{ecloud}}, we follow the [Elastic Version Maintenance and Support Policy](https://www.elastic.co/support/eol), which defines the support and maintenance policy of the Elastic Stack.