You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
Error logged when running logstash (sudo systemctl start logstash):
Plugin: <LogStash::Inputs::CloudWatch_Logs access_key_id=>"**", secret_access_key=><password>, id=>"68ef61a27eed2bd3e2a969415fd27263924ca794001390c75f15c212eab", log_group=>["fluteui-Prod", "
logstash[30989]: Error: The security token included in the request is invalid.
Exception: Aws::CloudWatchLogs::Errors::UnrecognizedClientException
The access key is passed correctly, but the secret_key is a somehow just password. During setup, the secret key and the access key are added to the cloudwatch_logs_cloud.conf file:
sudo sed -i "s/access_here/$(sed 's:/:\\/:g' /home/access_key_id.txt)/" /etc/logstash/conf.d/cloudwatch_logs_cloud.conf
sudo sed -i "s/secret_here/$(sed 's:/:\\/:g' /home/secret_access_key.txt)/" /etc/logstash/conf.d/cloudwatch_logs_cloud.conf
I have looked at both .txt files and the cloudwatch.conf file and the keys are there, but somehow the secret key is being passed incorrectly. Has anyone encountered a problem like this before?
Here is the cloudwatch.conf file. You can see I tried using an aws_credentials.yaml file as well, and I got another invalid token error:
Logstash version: 7.17.9
Error logged when running logstash (sudo systemctl start logstash):
The access key is passed correctly, but the secret_key is a somehow just password. During setup, the secret key and the access key are added to the cloudwatch_logs_cloud.conf file:
I have looked at both .txt files and the cloudwatch.conf file and the keys are there, but somehow the secret key is being passed incorrectly. Has anyone encountered a problem like this before?
Here is the cloudwatch.conf file. You can see I tried using an aws_credentials.yaml file as well, and I got another invalid token error:
The text was updated successfully, but these errors were encountered: