| mapped_pages | ||||
|---|---|---|---|---|
| applies_to |
|
|||
| products |
|
{{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.
{{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.
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.
:::{note} There are differences between {{es-serverless}} and {{ech}}. Learn more in Compare {{ech}} and {{es-serverless}}. :::
Elastic provides three serverless solutions available on {{ecloud}}. Follow these guides to get started with your serverless project:
- {{es-serverless}}: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries.
- {{obs-serverless}}: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data.
- {{sec-serverless}}: Detect, investigate, and respond to threats with SIEM, endpoint protection, and AI-powered analytics capabilities.
Afterwards, you can:
- Learn about the cloud organization that is the umbrella for all of your {{ecloud}} resources, users, and account settings.
- Learn about how {{es-serverless}} is billed.
- Learn how to create an API key. This key provides access to the API that enables you to manage your deployments.
- Learn how manage users and roles in your {{es-serverless}} deployment.
- Learn more about {{serverless-full}} in our blog.
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.
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. Some project-level limits apply to ensure performance and stability, including a limit on the number of indices per project that can be adjusted by request.
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 that you can configure for each project.
Dedicated experiences: All serverless solutions are built on the Elastic Search Platform and include the core capabilities of the {{stack}}. They also each offer a distinct experience and specific capabilities that help you focus on your data, goals, and use cases.
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.
:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md :::
Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.
To learn more about serverless status, see Service status.
Frequently asked questions (FAQ) about {{serverless-full}} projects [general-what-is-serverless-elastic-answers-to-common-serverless-questions]
The following FAQ addresses common questions about using {{serverless-full}} projects.
For information about upcoming features, refer to our roadmap.
Q: Where can I learn about pricing for {{serverless-short}}?
A: See pricing information for {{es-serverless}}, {{observability}}, and {{sec-serverless}}.
Q: What Cloud regions does {{serverless-full}} support?
A: {{serverless-full}} is available in select AWS, GCP, and Azure regions, with plans to expand to more regions. For more information, refer to .
Q: How can I move data to or from {{serverless-short}} projects?
A: We are working on data migration tools. In the interim, use Logstash with {{es}} input and output plugins to move data to and from {{serverless-short}} projects.
Q: Can I request backups or restores for my serverless projects?
A: Request for project backups or restores is currently unsupported, and we are working on data migration tools to better support this.
Q: How can I create {{serverless-full}} service accounts?
A: Create API keys for service accounts in your {{serverless-short}} projects. Options to automate the creation of API keys with tools such as Terraform will be available in the future.
Q: Can I configure {{es}} authentication realms (for example, native realm) in {{serverless-short}} projects?
A: No. {{serverless-short}} uses a different authentication model and does not support {{es}} authentication realms. Project-level access is handled through Serverless project API keys, and user authentication is managed at the {{ecloud}} organization level (including SAML SSO).
Q: What compliance and privacy standards does {{serverless-full}} adhere to?
A: Alongside the entire Elastic platform, {{serverless-full}} is independently audited and certified to meet industry-leading compliance and privacy standards. Refer to the Elastic Trust Center for more information. Further details about specific standards are available on our roadmap.
Q: What domains do I need to allow for browser access to {{kib}} in {{serverless-short}} projects?
A: In addition to the standard {{ecloud}} endpoints, ensure users can access kibana.estccdn.com, which is required to load {{kib}}. If this domain is blocked, {{kib}} might appear as a blank page. Refer to Browser access requirements for more information.
Q: How does {{serverless-full}} ensure compatibility between software versions?
A: Connections and configurations are unaffected by upgrades. To ensure compatibility between software versions, quality testing and API versioning are used.
Q: Can I convert a {{serverless-full}} project into an {{ech}} deployment, or a hosted deployment into a {{serverless-short}} project?
A: Projects and deployments are based on different architectures, so you are unable to convert.
Q: Can I convert a {{serverless-short}} project into a project of a different type?
A: 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.
Q: How do I raise a support case for {{serverless-full}}?
A: Raise a case for your subscription as you do today. In the body of the case, mention you are working with a {{serverless-short}} project to ensure appropriate support.
Q: Why does the GET / root API return a version number that differs from the current Elasticsearch release?
:::{include} /deploy-manage/deploy/_snippets/serverless-version-reporting.md :::