-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<Assume_role_credentials> throw MissingCredentialsError #246
Comments
Does anyone have an idea for this error? |
I am also the same mistake, only AK+SK can use. |
Was a solution ever found for this? Experiencing the same issue when trying to use instance profile credentials. |
We need help from AWS expert to investigate deeply. |
Solved my issue today. Did not have enough permissions for the plugin to access the bucket. Minimum requirements seem to be list bucket and put. |
For that case, the error should be AccessDenied. Did you get MissingCredentialsError instead of AccessDenied with lack of permission? |
After giving ListBucket and putobject permission also , we are facing same issue. |
Did anyone figure out the issue? I see the same error trying to push logs to cloudwatch. I am running fluentd as a sidecar in fargate pod. |
Workaround I used:
My pods had enough permissions. I had kube2iam(ref/more ref) installed and the pod had the right annotation. Problem I was facing:
This suggests that it might not be a permission issue but some SDK usage related issue. Hope it helps someone. |
In my case I have found out I need to disable |
Did anyone found the solution? Im facing the same problem but while writing into AWS Elastic search. |
I am facing also this error:
After added assume role configuration:
But pod have already IAM role assigned and I can able to copy data to my bucket via aws s3 cp file s3://bucket --region us-east-1 Conf:
|
I suppose even without any credential given, the plugin should not crash the fluentd. |
Do we have any solutions for this issue? Use of roles is more secure than access keys. |
I am running fluentd in a Kubernetes cluster. When configuring the
s3_out
plugin, instead of providing theaccess_key
and thesecret_key
, I used the<assume_role_credentials>
. My s3 configuration looks like this -However, I get the following error
I should be able to access AWS without providing the
access key and secret key
.Can anybody provide more details about it?
The text was updated successfully, but these errors were encountered: