-
Notifications
You must be signed in to change notification settings - Fork 241
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
Exporter for AMP Credential error #520
Comments
Are you using the collector as a container or running the binary directly on your host (mac or ec2 vm etc.)? If you are running it on your host, can you try some simple command from aws cli like |
hi @pingleig |
I didn't find anything strange in the code https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/10790bb5affa048a61cf13ca20bae19b1eca39e8/exporter/awsprometheusremotewriteexporter/auth.go#L106-L121 The only suspicious part is Shared Config Fields Did you config your credentials in |
I have tried with both ways still the same error log. is there a way to rebuild collector with hard coded credentials as a workaround? |
@hiranthaPeiris can you share your collector configuration? I wouldn't recommend attempting to hard code credentials in the collector. Let's see what we can do to figure out where the disconnect is happening. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Marking as resolved. |
Hi,
I am trying to configure AMP exporter but get NoCredentialProviders on logs of the collector as following.
WARN batchprocessor/batch_processor.go:209 Sender failed {"kind": "processor", "name": "batch/metrics", "error": "Permanent error: Post \"https://aps-workspaces.us-east-1.<workspace>/api/v1/remote_write\": NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors"}
I have set aws access key according to default AWS credentials chain and also AWS go SDK as the documentation. what I could be missing here?
Thanks
The text was updated successfully, but these errors were encountered: