# Cannot connect my Kibana instance to AWS Elastic Search service {Kibana server is not ready yet}
**URL:** https://discuss.elastic.co/t/cannot-connect-my-kibana-instance-to-aws-elastic-search-service-kibana-server-is-not-ready-yet/199475
**Category:** Kibana
**Created:** [September 13, 2019, 7:59pm UTC](https://discuss.elastic.co/t/cannot-connect-my-kibana-instance-to-aws-elastic-search-service-kibana-server-is-not-ready-yet/199475 "2019-09-13T19:59:45Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@sshrivastava](https://discuss.elastic.co/u/sshrivastava)
#### Post date: [September 13, 2019, 7:59pm UTC](https://discuss.elastic.co/t/cannot-connect-my-kibana-instance-to-aws-elastic-search-service-kibana-server-is-not-ready-yet/199475/1 "2019-09-13T19:59:45Z")
Hi all,
I'm trying to setup wazuh cluster in aws with AWS ES instead of regular elastic search service.
The problem i'm facing is after making changes in /etc/kibana/kibana.yml:
kibana.index: ".kibana"
elasticsearch.hosts: ["https://my\_VPC\_es\_endpoint:443"]
They're both in same subnet group.
Below are the logs generated from : journalctl -u kibana.service
[https://textuploader.com/10msp](https://textuploader.com/10msp)
I keep getting kibana server is not ready yet
and something like this :
```
Sep 13 18:48:54 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:3] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
Sep 13 18:48:54 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:4] Unknown lvalue 'StartLimitBurst' in section 'Unit'
Sep 13 19:03:13 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:3] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
Sep 13 19:03:13 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:4] Unknown lvalue 'StartLimitBurst' in section 'Unit'
Sep 13 19:24:46 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:3] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
Sep 13 19:24:46 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:4] Unknown lvalue 'StartLimitBurst' in section 'Unit'
Sep 13 19:51:41 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:3] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
Sep 13 19:51:41 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:4] Unknown lvalue 'StartLimitBurst' in section 'Unit'
Sep 13 19:52:09 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:3] Unknown lvalue 'StartLimitIntervalSec' in section 'Unit'
Sep 13 19:52:09 ip-172-16-13-237.ec2.internal systemd[1]: [/etc/systemd/system/kibana.service:4] Unknown lvalue 'StartLimitBurst' in section 'Unit'
```
---
### Author:  [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)
#### Post date: [September 13, 2019, 8:04pm UTC](https://discuss.elastic.co/t/cannot-connect-my-kibana-instance-to-aws-elastic-search-service-kibana-server-is-not-ready-yet/199475/2 "2019-09-13T20:04:18Z")
Hello,
AWS ES forums will be a better place to ask about issues with it. We will help with self-hosted Elasticsearch, but for third-party services we really have no access to what settings and/or setup they do so we do not have enough information to help.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 11, 2019, 8:04pm UTC](https://discuss.elastic.co/t/cannot-connect-my-kibana-instance-to-aws-elastic-search-service-kibana-server-is-not-ready-yet/199475/3 "2019-10-11T20:04:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.