# Filebeat 7.6.0 oss can't work with AWS Elasticsearch Service because it tries to access xpack
**URL:** https://discuss.elastic.co/t/filebeat-7-6-0-oss-cant-work-with-aws-elasticsearch-service-because-it-tries-to-access-xpack/221189
**Category:** Beats
**Created:** [February 27, 2020, 9:21am UTC](https://discuss.elastic.co/t/filebeat-7-6-0-oss-cant-work-with-aws-elasticsearch-service-because-it-tries-to-access-xpack/221189 "2020-02-27T09:21:36Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Vlad\_Lukyanov](https://discuss.elastic.co/u/Vlad_Lukyanov)
#### Post date: [February 27, 2020, 9:21am UTC](https://discuss.elastic.co/t/filebeat-7-6-0-oss-cant-work-with-aws-elasticsearch-service-because-it-tries-to-access-xpack/221189/1 "2020-02-27T09:21:36Z")
Have
- AWS ES instance open to world
- AWS EC2 instance for testing
- FileBeat OSS 7.6.0 installed from OSS-7.x Debian repo
on 'filebeat setup -e --template'
Got
2020-02-27T09:06:00.826Z INFO elasticsearch/client.go:757 Attempting to connect to Elasticsearch version 7.1.1
Overwriting ILM policy is disabled. Set `setup.ilm.overwrite:true` for enabling.
2020-02-27T09:06:00.829Z ERROR instance/beat.go:933 Exiting: request checking for ILM availability failed: 401 Unauthorized: {"Message":"Your request: '/\_xpack' is not allowed."}
Expected that filebeat will check '"build\_flavor" : "oss"' and not try to access /\_xpack endpoint
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 26, 2020, 11:21am UTC](https://discuss.elastic.co/t/filebeat-7-6-0-oss-cant-work-with-aws-elasticsearch-service-because-it-tries-to-access-xpack/221189/2 "2020-03-26T11:21:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.