Securing Kibana and ElasticSearch without X-Pack-Security plugin

0

A customer integrated the ELK stack into their application. If they run their own ES cluster, or use the managed service provided by elastic.co, they can lock down access to Kibana and ES using the X-Pack-Security plugin.

They're aware of the approach outlined in https://aws.amazon.com/blogs/security/how-to-control-access-to-your-amazon-elasticsearch-service-domain/, but want to avoid the need to run a proxy to handle authentication between Kibana & ES.

Do we have any alternative suggestion?

質問済み 7年前468ビュー
1回答
0
承認された回答

Rather than use a proxy server that is allowed access via IP which requires you running an extra instance, you can enable IAM access and use the aws-es-kibana proxy which runs locally on the client and uses the clients IAM credentials to do the SigV4 signing. Here's another local proxy that supports IAM roles which the first one I mentioned doesn't.

AWS
エキスパート
Adam_W
回答済み 7年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ