Terraform-provider-aws: InvalidClientTokenId when AWS secret contains a "/"

[hashibot]

_This issue was originally opened by @fjferrer as hashicorp/terraform#16709. It was migrated here as a result of the provider split. The original body of the issue is below._

---

Hi there,

I'm getting InvalidClientTokenId when trying to run terraform plan.

Bug found in terraform version: 0.10.8 and 0.11.0

Steps to Reproduce

1. terraform init
2. terraform plan

Important Factoids

AWS Secret key contains "/". Creating a new pair of keys without "/" in the secret key solved the issue.

References

• hashicorp/terraform#13333

[jufemaiz]

So this is still an issue yeah?

[Radik2]

Hello people,

Is this still an issue ?

[allthatilk]

I'm getting it so I think it's still happening?

[bflad]

Hi folks 👋 While this may still be a valid bug report, a lot has changed in the Terraform AWS Provider's and AWS Go SDK's authentication logic since it was filed, and the maintainers have not been able to reproduce the issue lately. To encourage fresh bug reports which might have additional information leading to a root cause, I'm going to close this for now. If you are running recent versions of the Terraform AWS Provider (version 2.69.0 is the current latest), please file a new bug report issue following the issue template and hopefully we can track this down. Thanks.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!