# Kibana on AWS EC2 instance to talk to Managed AWS ES
**URL:** https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508
**Category:** Kibana
**Created:** [September 6, 2017, 3:43am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508 "2017-09-06T03:43:20Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Nikhilpawar1985](https://discuss.elastic.co/u/Nikhilpawar1985)
#### Post date: [September 6, 2017, 3:43am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/1 "2017-09-06T03:43:20Z")
Hi ,
I have installed kibana on EC2 instance as we need custom plugins on kibana and trying to configure to connect to managed AWS ES . Can someone provide a guideline to do this . I tried few things but it seems to be not working
Thanks,
Nikhil
---
### Author:  [@mujtabahussain](https://discuss.elastic.co/u/mujtabahussain)
#### Post date: [September 6, 2017, 4:22am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/2 "2017-09-06T04:22:50Z")
Check what ports you have open on the managed AWS ES instance and whether they are accessible from where you have set up your custom Kibana instance.
Ensure that in the `kibana.yml` file, you are pointing to it correct and that the plugins don't override that.
If none of that helps at all, definitely ask in [AWS Discussion Forums](https://forums.aws.amazon.com/forum.jspa?forumID=200) as well.
---
### Author:  [@Nikhilpawar1985](https://discuss.elastic.co/u/Nikhilpawar1985)
#### Post date: [September 6, 2017, 1:49pm UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/3 "2017-09-06T13:49:50Z")
AWS Managed ES doesnot provide any ports specification , just give the ES https url to connect to . I have allowed my EC2 instance ip to communicate with ES .
Some reason it cannot connect to AWS ES
---
### Author:  [@Nikhilpawar1985](https://discuss.elastic.co/u/Nikhilpawar1985)
#### Post date: [September 7, 2017, 12:46am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/4 "2017-09-07T00:46:11Z")
I have figured out the solution
---
### Author:  [@mujtabahussain](https://discuss.elastic.co/u/mujtabahussain)
#### Post date: [September 7, 2017, 1:27am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/5 "2017-09-07T01:27:27Z")
Which was?
---
### Author:  [@Nikhilpawar1985](https://discuss.elastic.co/u/Nikhilpawar1985)
#### Post date: [September 7, 2017, 1:56am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/6 "2017-09-07T01:56:28Z")
I replaced localhost with 0.0.0.0
and added a specific port with AWS ES endpoint also added new kibana index replacing the default .kibana
That fixed it
Thanks .
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 5, 2017, 1:57am UTC](https://discuss.elastic.co/t/kibana-on-aws-ec2-instance-to-talk-to-managed-aws-es/99508/7 "2017-10-05T01:57:14Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.