# Unable to enable security on elk instance using puppet
**URL:** https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179
**Category:** Kibana
**Created:** [May 5, 2020, 3:12pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179 "2020-05-05T15:12:26Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Thaylin](https://discuss.elastic.co/u/Thaylin)
#### Post date: [May 5, 2020, 3:12pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179/1 "2020-05-05T15:12:26Z")
I currently have a puppet configuration of the elasticsearch and kibana, however I cannot get security to enable so I can setup users and then enable the logstash. When I enable the securty it still allows me into the UI without prompting and does not restrict any data.. Under management I do not even see a security option to manage users and roles.
> class { 'elastic\_stack::repo':
> version =\> 7,
>
> }
> class { 'elasticsearch':
> config =\> {
> 'xpack.security.enabled' =\> true,
> }
> }
> elasticsearch::instance { 'elk-prod01': }
>
> #`
> class { 'kibana':
> oss =\> true,
> config =\> {
> 'server.port' =\> '8443',
> 'server.host' =\> "$hostname",
> 'server.ssl.certificate' =\> "/opt/ssl\_certs\_public/data/$hostname.lib.crt",
> 'server.ssl.key' =\> "/opt/ssl\_certs\_public/data/$hostname.lib.key",
> 'server.ssl.enabled' =\> true,
> 'logging.dest' =\> '/var/log/kibana/kibana.log',
> 'elasticsearch.username' =\> "kibana",
> 'elasticsearch.password' =\> "\*\*\*\*\*\*\*\*\*",
> },
> ensure =\> latest,
> }
---
### Author:  [@Thaylin](https://discuss.elastic.co/u/Thaylin)
#### Post date: [May 5, 2020, 3:45pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179/2 "2020-05-05T15:45:49Z")
been doing some digging and it seems elastic search's xpack is disabled still for some reason even though the yaml says to enable it.
---
### Author:  [@Thaylin](https://discuss.elastic.co/u/Thaylin)
#### Post date: [May 5, 2020, 4:09pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179/3 "2020-05-05T16:09:13Z")
I figured out the cause the elastic/elasticsearch puppet module is not placing the elasticserarch.yml file in /etc/elsaticsearch, but in the subdirectory . The service does not appear to be using the proper instance file.
---
### Author:  [@Thaylin](https://discuss.elastic.co/u/Thaylin)
#### Post date: [May 5, 2020, 5:25pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179/4 "2020-05-05T17:25:08Z")
To finish this up I had to add
```
security_plugin => 'x-pack',
```
to the elasticsearch class. Sorry for the post.
---
### Author:  [@Larry\_Gregory](https://discuss.elastic.co/u/Larry_Gregory)
#### Post date: [May 5, 2020, 6:05pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179/5 "2020-05-05T18:05:36Z")
Hey @Thaylin, welcome to the discussion boards.
Thanks for following up with your solution! This will help others in the future who might come across this.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 2, 2020, 6:05pm UTC](https://discuss.elastic.co/t/unable-to-enable-security-on-elk-instance-using-puppet/231179/6 "2020-06-02T18:05:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.