Metricbeat to use EC2 role permissions to access AWS ELK stack

Elastic Stack Beats
,
1

I installed Metricbeat on a EC2 server to monitor docker containers and configured to send the logs to AWS ELK stack. Metricbeat is not utilizing the role that have permission to access ELK stack. How can i configure Metricbeat to use the role that has permissions to access AWS ELK stack? Is there anyway we can configure Metricbeat to access AWS ELK stack?

[root@ip-10-172-210-30 ~]# metricbeat test output
elasticsearch: https://elasticservach-sample.us-east-1.es.amazonaws.com:443...
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: 10.173.11.109, 10.173.13.99, 10.173.200.245
dial up... OK
TLS...
security: server's certificate chain verification is enabled
handshake... OK
TLS version: TLSv1.2
dial up... OK
talk to server... ERROR 403 Forbidden: {"message":"Authorization header requires 'Credential' parameter. Authorization header requires 'Signature' parameter. Authorization header requires 'SignedHeaders' parameter. Authorization header requires existence of either a 'X-Amz-Date' or a 'Date' header. Authorization=Basic ZWRwLWRldjpJcnZpbmdAMTIwMw=="}

2

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