AWS error when trying to run non-stable versions of Komiser
jakepage91 opened this issue · 0 comments
jakepage91 commented
Is your feature request related to a problem? Please describe.
When I build Komiser binary from contributor submitted forks. Authenticating Komiser to AWS through the credentials file throws a STS error. I don't get these error when running the latest stable version of Komiser
Describe the solution you'd like
To have the same behavior running a stable or non stable version of Komiser, AWS auth should't fail for all services when running ./komiser start on a non-stable binary
Example output:
WARN[2023-12-15T14:52:22Z] [Admin][AWS] operation error CloudWatch Logs: DescribeLogGroups, https response error StatusCode: 400, RequestID: c03eca0f-720a-4fbd-b3f4-8b94870c9328, api error UnrecognizedClientException: The security token included in the request is invalid.
WARN[2023-12-15T14:52:22Z] [Admin][AWS] operation error OpenSearch: ListDomainNames, https response error StatusCode: 403, RequestID: cba62785-0e91-4838-afa2-6cdd08b5f948, api error UnrecognizedClientException: The security token included in the request is invalid.
WARN[2023-12-15T14:52:22Z] [Admin][AWS] operation error ElastiCache: DescribeCacheClusters, https response error StatusCode: 403, RequestID: 03d80670-a6e2-4064-8434-ce82ef1b2145, api error InvalidClientTokenId: The security token included in the request is invalid.
WARN[2023-12-15T14:52:22Z] [Admin][AWS] operation error STS: GetCallerIdentity, https response error StatusCode: 403, RequestID: 721551dc-0a79-454d-ad3f-67c5b3d2f94e, api error InvalidClientTokenId: The security token included in the request is invalid.