# ElasticSearch Elastic Cloud serveless deployments serverely out of date **URL:** \ **Category:** Elastic Search\ **Created:** [February 5, 2025, 10:25am UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117 "2025-02-05T10:25:16Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Stanislav\_Modrak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stanislav_modrak/32/141169_2.png) [@Stanislav\_Modrak](https://discuss.elastic.co/u/Stanislav_Modrak)\ **Post date:** [February 5, 2025, 10:25am UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/1 "2025-02-05T10:25:16Z")
Today I had a huge surprise when trying to migrate some of our existing infrastructure to a new Elasticsearch service **serveless deployment** hosted on **Elastic Cloud** and my code has stopped working with `ResponseError: This API is unavailable in the version of Elasticsearch you are using`. Upon closer inspection, I found out that the newly created serveless deployments are on version `8.11.0` of Elasticsearch, which is severely out of date (latest version should be `8.17.1`). This makes this completely unusable for us as we rely on up to date APIs and unfortunately will have to abandon this offering right away, which is a huge shame because it seemed greatly attractive. Have I missed anything or can nothing be done about this? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [February 5, 2025, 2:30pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/2 "2025-02-05T14:30:50Z")
Hi @Stanislav_Modrak Welcome to the community and thanks for trying Elastic Serverless? Sorry for the confusion If you run `GET /` to get the version number, the 8.11.0 shown is for internal reasons... that does not represent the feature version number. Serverless is essentially version-less; your serverless deployment is / will be the latest. Serverless technically does not expose a version number by design, as it always stays on the latest / up-to-date... in this case right now it will have the serverless equivalent on 8.17.1 but will not report that. So, lets focus on what API is failing. Exactly what API is failing, it is possible that that API is not supported or works differently. What Elastic version is it currently working with today? ---
**Author:** ![Stanislav\_Modrak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stanislav_modrak/32/141169_2.png) [@Stanislav\_Modrak](https://discuss.elastic.co/u/Stanislav_Modrak)\ **Post date:** [February 5, 2025, 3:18pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/3 "2025-02-05T15:18:29Z")
Hi Stephen. Ah, I see. That is what probably confused me as well. I have now also realised there's a separate client package to use specifically for serverless deployments, so I am looking into that one. This has now stopped throwing `ResponseError: This API is unavailable in the version of Elasticsearch you are using` for me. Thanks for your help! 🙂 ---
**Author:** ![Stanislav\_Modrak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stanislav_modrak/32/141169_2.png) [@Stanislav\_Modrak](https://discuss.elastic.co/u/Stanislav_Modrak)\ **Post date:** [February 5, 2025, 3:21pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/4 "2025-02-05T15:21:13Z")
> [@stephenb](#): > > it always stays on the latest / up-to-date... How do you make sure serverless always stays on the latest version? How do you deal with breaking changes? Especially such that affect some of the user data indices. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [February 5, 2025, 4:21pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/5 "2025-02-05T16:21:40Z")
> [@Stanislav\_Modrak](#): > > How do you make sure serverless always stays on the latest version? How do you deal with breaking changes? Especially such that affect some of the user data indices. Serverless ...is a different mindset .... This is a big topic.... internally... The API Version is a fixed version at this time... and is not expected to change for a long time. There is a change log > **[Elastic Cloud Serverless changelog | Elastic Installation and Upgrade Guide...](https://www.elastic.co/guide/en/elastic-stack/9.0/serverless-changelog.html)** Can you give an example of a breaking change you are concerned about? ---
**Author:** ![Stanislav\_Modrak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stanislav_modrak/32/141169_2.png) [@Stanislav\_Modrak](https://discuss.elastic.co/u/Stanislav_Modrak)\ **Post date:** [February 5, 2025, 4:42pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/6 "2025-02-05T16:42:26Z")
> [@stephenb](#): > > This is a big topic.... internally... I can certainly imagine. > [@stephenb](#): > > Can you give an example of a breaking change you are concerned about? None at this moment actually, I was just thinking ahead. 🙂 > [@stephenb](#): > > API Version is a fixed version at this time... and is not expected to change for a long time This was a second concern of ours actually. And that is that if that's the case, our serverless deployment might start to lag behind the latest Elasticsearch version and we would miss out on new features and capabilities. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [February 5, 2025, 4:50pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/7 "2025-02-05T16:50:33Z")
There is a lot of documenation emerging on Serverless... there is a new API Hub All the APIs across products > **[Elastic APIs](https://www.elastic.co/docs/api/)** > > Welcome to the Elastic APIs This is the Elasticsearch Serverless API example > **[Elasticsearch Serverless API documentation](https://www.elastic.co/docs/api/doc/elasticsearch-serverless)** > > Documentation source and versions > This documentation is derived from the main branch of the elasticsearch-specification repository. It is provided under lice... ---
**Author:** ![Kathleen\_DeRusso](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kathleen_derusso/32/132039_2.png) [@Kathleen\_DeRusso](https://discuss.elastic.co/u/Kathleen_DeRusso)\ **Post date:** [February 5, 2025, 5:55pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/8 "2025-02-05T17:55:16Z")
> [@Stanislav\_Modrak](#): > > This was a second concern of ours actually. And that is that if that's the case, our serverless deployment might start to lag behind the latest Elasticsearch version and we would miss out on new features and capabilities. The opposite is true, new features are available on Serverless well before they're available on stack releases! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 5, 2025, 5:56pm UTC](https://discuss.elastic.co/t/elasticsearch-elastic-cloud-serveless-deployments-serverely-out-of-date/374117/9 "2025-03-05T17:56:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.