# Kibana v7.0.0 AWS Fargate Startup Issue

**URL:** <https://discuss.elastic.co/t/kibana-v7-0-0-aws-fargate-startup-issue/180618>\
**Category:** Kibana\
**Created:** [May 10, 2019, 8:28pm UTC](https://discuss.elastic.co/t/kibana-v7-0-0-aws-fargate-startup-issue/180618 "2019-05-10T20:28:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![webb74](https://avatars.discourse-cdn.com/v4/letter/w/dc4da7/32.png) [@webb74](https://discuss.elastic.co/u/webb74)\
**Post date:** [May 10, 2019, 8:28pm UTC](https://discuss.elastic.co/t/kibana-v7-0-0-aws-fargate-startup-issue/180618/1 "2019-05-10T20:28:56Z")

</div>

I have an Elasticsearch v7.0.0 cluster (non-oss) up and running. I am attempting to load the Kibana v7.0.0 (non-oss) Docker image on AWS Fargate for use with the cluster. The container fails to start and never produces Cloudwatch logs. As a test I used the Kibana v7.0.0 (oss) image and it starts, connects to the Elasticsearch cluster and responds via the UI. The only difference besides the image name in the Fargate task definition for the Kibana (non-oss) version is I set 3 additional environment variables, see below. Removal of these offer no help with the startup. Does anyone have suggestions on how to debug this issue?

Env variables:  
{  
"name": "XPACK\_MONITORING\_UI\_CONTAINER\_ELASTICSEARCH\_ENABLED",  
"value": "false"  
},  
{  
"name": "XPACK\_XPACK\_MAIN\_TELEMETRY\_ENABLED",  
"value": "false"  
},  
{  
"name": "XPACK\_SECURITY\_ENABLED",  
"value": "false"  
}

UPDATE: removal of pre-existing .kibana\* indices in Elasticsearch plus lengthening the Fargate and loadbalancer health check timeouts allowed Kibana to finish its optimization process and began to run.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [May 13, 2019, 3:56pm UTC](https://discuss.elastic.co/t/kibana-v7-0-0-aws-fargate-startup-issue/180618/2 "2019-05-13T15:56:21Z")

</div>

Glad you figured it out - I would assume it was just waiting on the optimize process since the plugins were disabled. Should have still seen log output, though.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 10, 2019, 3:56pm UTC](https://discuss.elastic.co/t/kibana-v7-0-0-aws-fargate-startup-issue/180618/3 "2019-06-10T15:56:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.