Skip to content
This repository has been archived by the owner on Sep 8, 2023. It is now read-only.

Komiser Local: Missing config.toml step in AWS #75

Open
ShubhamPalriwala opened this issue Apr 15, 2023 · 0 comments
Open

Komiser Local: Missing config.toml step in AWS #75

ShubhamPalriwala opened this issue Apr 15, 2023 · 0 comments

Comments

@ShubhamPalriwala
Copy link
Collaborator

I followed the documentation to connect my AWS account as per the below:
https://docs.komiser.io/docs/cloud-providers/aws#local-komiser-cli

And I was confused that:

  1. Do I need to add an AWS section in my config.toml
  2. In what format should I?
  3. The docs said in a different section on the same page in the form of:
[[aws]]
name="sandbox"
source="CREDENTIALS_FILE"
path=./path/to/credentials/file
profile="default

I tried the same and kept on getting the following error:

WARN[2023-04-15T12:09:19+05:30] [shubham-test][AWS] operation error Lambda: ListFunctions, failed to sign request: failed to retrieve credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, request canceled, context deadline exceeded

Which on further debugging and hit and trials, I managed to get it working by setting the following in my config.toml:

[[aws]]
name="shubham-test"
source="CREDENTIALS_FILE"

Since it's in the default path ie the path suggested in the docs, we do not need to pass the path parameter (this is also mentioned in the docs in the configuring credentials section: https://docs.komiser.io/docs/cloud-providers/aws#configuring-credentials).

My suggestion is that most users won't read the documentation so thoroughly hence adding a step of config.toml won't harm in any way and will improve the UX

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

No branches or pull requests

1 participant