# Spring boot data Elastic Cloud integration

**URL:** <https://discuss.elastic.co/t/spring-boot-data-elastic-cloud-integration/176383>\
**Category:** Elasticsearch\
**Created:** [April 11, 2019, 10:49am UTC](https://discuss.elastic.co/t/spring-boot-data-elastic-cloud-integration/176383 "2019-04-11T10:49:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Bill\_Bensing](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bill_bensing/32/45679_2.png) [@Bill\_Bensing](https://discuss.elastic.co/u/Bill_Bensing)\
**Post date:** [May 8, 2019, 4:13pm UTC](https://discuss.elastic.co/t/spring-boot-data-elastic-cloud-integration/176383/2 "2019-05-08T16:13:24Z")

</div>

I found a solution-ish, at the least I progressed to the next error. I updated to the latest version for transport ( 6.7.2 - for this given time) : [https://mvnrepository.com/artifact/org.elasticsearch.client/transport](https://mvnrepository.com/artifact/org.elasticsearch.client/transport)

Here is a link to a helpful post: [Java transport client do not work after upgrade to 6.5.3](https://discuss.elastic.co/t/java-transport-client-do-not-work-after-upgrade-to-6-5-3/161726/3)

-- Previous Comments --

I have come across this same issue this morning. Where you able to find a solution?

I'm wandering if Spring Data is automatically configuring the NamedWriteable bean. I tried the following with no success:

`@SpringBootApplication(exclude = {ElasticsearchAutoConfiguration.class, ElasticsearchDataAutoConfiguration.class})`

```
spring:
  autoconfigure:
    exclude:
      - org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchAutoConfiguration
      - org.springframework.boot.autoconfigure.data.elasticsearch.ElasticsearchDataAutoConfiguration
```

---

_[View the full topic](https://discuss.elastic.co/t/spring-boot-data-elastic-cloud-integration/176383)._