# Déployer un kibana qui se connecte à elastic cloud **URL:** \ **Category:** Discussions en français\ **Created:** [November 19, 2018, 8:51am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301 "2018-11-19T08:51:55Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\ **Post date:** [November 19, 2018, 8:51am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/1 "2018-11-19T08:51:55Z")
Bonjour, j'ai une instance de déploiement elastic cloud. Je voudrais faire tourner sur mon serveur (avec mon nom de domaine) une instance kibana qui se connecte à ce cluster (cloud). Je n'ai pas trouvé de best practice pour cela. Je vois qu'on peut se connecter à l'instance facilement, mais comment fait on pour configurer x-pack? comment configurer le reporting? merci ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 19, 2018, 10:15am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/2 "2018-11-19T10:15:20Z")
Question idiote. Pourquoi tu ne veux pas utiliser l'instance Kibana provisionnée par cloud? Sinon, il faut que tu configures Kibana. - [https://www.elastic.co/guide/en/kibana/current/settings.html](https://www.elastic.co/guide/en/kibana/current/settings.html) - [https://www.elastic.co/guide/en/kibana/current/secure-settings.html](https://www.elastic.co/guide/en/kibana/current/secure-settings.html) ---
**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\ **Post date:** [November 19, 2018, 10:31am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/3 "2018-11-19T10:31:48Z")
Parce que je veux y accéder par une URL à moi: [https://monitoring.ma-boite.com](https://monitoring.ma-boite.com) ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 19, 2018, 11:03am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/4 "2018-11-19T11:03:34Z")
Je vois... Genre ici : [https://www.elastic.co/guide/en/cloud/release-ms-13/ec-faq.html](https://www.elastic.co/guide/en/cloud/release-ms-13/ec-faq.html) > **Can I get a custom DNS, a custom URL or a static IP address?** > > For the most part, we do not plan to support these items, but custom domain aliases are on the road map. For example, an endpoint URL for _mycompanyname_ .found.io. will be supported. You can also host your own server as a proxy to forward HTTP or HTTPS requests to your cluster hosted on Elastic Cloud. ---
**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\ **Post date:** [November 19, 2018, 11:08am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/5 "2018-11-19T11:08:03Z")
OK, it is on the roadmap, but do you have some visibility on it? > [@dadoonet](#): > > an endpoint URL for _mycompanyname_ .found.io. will be supported is not what I search. I do not want the [found.io](http://found.io). Therefore, the kibana has today to be hosted on my server. Currently trying, I'll post my steps ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [November 19, 2018, 11:10am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/6 "2018-11-19T11:10:45Z")
Oui oui. La partie intéressante dans ton cas est: > You can also host your own server as a proxy to forward HTTP or HTTPS requests to your cluster hosted on Elastic Cloud. En fait, je te dis ça car la gestion des montées de version est du coup beaucoup plus simple... Si tu n'y arrives pas, tu peux également demander à ton support cloud [https://www.elastic.co/cloud/as-a-service/support](https://www.elastic.co/cloud/as-a-service/support) qui est fait pour ça aussi je pense. Qu'as-tu configuré jusqu'à présent ? ---
**Author:** ![dao](https://avatars.discourse-cdn.com/v4/letter/d/a6a055/32.png) [@dao](https://discuss.elastic.co/u/dao)\ **Post date:** [November 20, 2018, 9:36am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/7 "2018-11-20T09:36:45Z")
Réponse du support cloud: `ca n'est pas dans notre scope` Bon, donc j'ai bien déployé mon kibana qui se connecte à mon elastic cloud. 1. Etonnement, il n'y a pas de user `kibana_system` dans le déploiement elastic cloud. Je me demande bien comment ils font pour le kibana qui est livré dans le cloud. Comment se connecte t il a cluster? Bon toujours est il que j'ai du le créer via l'API (`https://44ddXXXXXXXXXX.eu-west-1.aws.found.io:9243/_xpack/security/user/mon-kibana-system`) 2. je positionne les accès au cluster: 3. Je positionne le basePath (car mon kibana est accessible de `https://monitoring.ma-boite.com/bidgata/:`server.basePath: "/bigdata"` Je n'ai toujours pas accès au reporting. J'aimerais que le reporting utilise mon instance KIBANA du cloud. Pour cela, la doc me demande de positionner ces informaitons dans `kibana.yml` ```auto xpack.reporting.encryptionKey: "ZHDFEBHAIJOSXXXXXXXXO682351279" xpack.reporting.kibanaServer.port: 443 xpack.reporting.kibanaServer.protocol: https xpack.reporting.kibanaServer.hostname: 5aa5dXXXXXXbe03.eu-west-1.aws.found.io xpack.reporting.queue.timeout: 90000 ``` En ce moment ca plante encore (Unable to generate report - TimeoutError: waiting for selector ".application" failed: timeout 30000ms exceeded) mais ca a l'air dû à la 6.5. J'ai un ticket au support I'll keep you updated ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 18, 2018, 9:43am UTC](https://discuss.elastic.co/t/deployer-un-kibana-qui-se-connecte-a-elastic-cloud/157301/8 "2018-12-18T09:43:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.