Closed dkebler closed 5 months ago
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!
Anyone had issues with your addon/docker and route53 credentials?
Unless it's something I have done I'm guess your addon is not passing credentials on to route53 plugin correctly.
I have many other installs of route53 with caddy (including my own caddy docker) that work fine with the same aws credentials I am using here
operation error Route 53: ListHostedZonesByName, https response error StatusCode: 403, RequestID: 278d1598-46eb-46a7-a47d-87c209f26733, api error InvalidClientTokenId: The security token included in the request is invalid.
`log looks good until that line. loads custom caddy binary loads credentials correctly
it uses this caddy plugin.
https://github.com/caddy-dns/route53