Skip to content
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

Support IAM roles for service accounts in AWS EKS #1241

Closed
adamjohnson01 opened this issue Nov 8, 2019 · 1 comment · Fixed by #1340
Closed

Support IAM roles for service accounts in AWS EKS #1241

adamjohnson01 opened this issue Nov 8, 2019 · 1 comment · Fixed by #1340

Comments

@adamjohnson01
Copy link
Contributor

Issue #1019 and #1182 did not include all of the requirements to support IAM roles for service accounts in AWS EKS. This is due to coretex using session.New instead of session.NewSession. I have opened an issue in the coretex project. A workaround is to add the following env var to the Loki pod

AWS_SDK_LOAD_CONFIG=1

To Reproduce

  1. Deploy Loki in EKS using IAM roles for service accounts using DynamoDB and S3 storage

Expected behavior
Loki can connect to S3 and DynamoDB.

Environment:

  • Infrastructure: EKS
  • Deployment tool: helm/argo-cd

The following errors show up in the logs.

level=info ts=2019-11-08T10:23:10.089802001Z caller=table_manager.go:220 msg="synching tables" expected_tables=1
level=error ts=2019-11-08T10:23:10.09039794Z caller=table_manager.go:179 msg="error syncing tables" err="NoCredentialProviders: no valid providers
in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors"

@adamjohnson01
Copy link
Contributor Author

The PR in cortex was merged, I have opened a PR to pull the cortex changes into loki.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant