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

sigv4proxy NoCredentialProviders #3520

Open
eahangari-8x8 opened this issue Jun 27, 2024 · 2 comments
Open

sigv4proxy NoCredentialProviders #3520

eahangari-8x8 opened this issue Jun 27, 2024 · 2 comments

Comments

@eahangari-8x8
Copy link

Hello everyone I have installed the kubecost using helm chart and argocd but I get the following error in the sigv4proxy container.
here is the log:

 time="2024-06-27T20:31:22Z" level=error msg="unable to proxy request" error="NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors"

here is my values.yaml

global:
  grafana:
    enabled: false
    proxy: false

  prometheus:
    enabled: true

  amp:
    enabled: true
    prometheusServerEndpoint: http://localhost:8005/workspaces/<redacted>
    remoteWriteService: https://aps-workspaces.us-east-1.amazonaws.com/workspaces/<redacted>/api/v1/remote_write
    sigv4:
      region: us-east-1

  platforms:
    cicd:
      enabled: true
      skipSanityChecks: true

sigV4Proxy:
  region: us-east-1
  host: aps-workspaces.us-east-1.amazonaws.com

I really appreciate it if you can give me any help or advice on how to resolve it.
Thanks

@eahangari-8x8
Copy link
Author

update: Im not using IRSA ( Iam role for service account ) I prefer to use eks pod identity but it seems that it is only defined for (https://docs.kubecost.com/install-and-configure/install/cloud-integration/aws-cloud-integrations/aws-cloud-integration-using-irsa).
can I have the confirmation on this please. So I have to use the IRSA for the sigv4

@eahangari-8x8
Copy link
Author

update2:
awslabs/aws-sigv4-proxy#191
the pr has already been opened to update the GO sdk version

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

No branches or pull requests

1 participant