Hi Cody,
How are you supplying the AWS credentials?
The AWS client that Vault uses, takes credentials from multiple
sources: static credentials, environment variables, shared file
credentials, IAM role credentials. In windows environment, I don't
know if shared file credentials and IAM role credentials would work or
not, but the other two ideally should.
The easiest way is to set the static credentials using the
`aws/config/root` endpoint.
Regards,
Vishal
On Thu, Dec 7, 2017 at 8:14 AM, Cody Hussey <
cody.r...@gmail.com> wrote:
> New to vault.
>
> This is running on a Windows test box, do I need to install any AWS
> dependencies for this to work properly?
>
> Full error:
> C:\hashicorp\vault>vault write aws/roles/deploy policy=@policy.json
> Success! Data written to: aws/roles/deploy
>
> C:\hashicorp\vault>vault read aws/creds/deploy
> Error reading aws/creds/deploy: Error making API request.
>
> URL: GET
http://127.0.0.1:8200/v1/aws/creds/deploy
> Code: 400. Errors:
>
> * Error creating IAM user: NoCredentialProviders: no valid providers in
> chain. Deprecated.
> For verbose messaging see aws.Config.CredentialsChainVerboseErrors
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
>
https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues:
https://github.com/hashicorp/vault/issues
> IRC: #vault-tool on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vault" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
vault-tool+...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/vault-tool/5a37c945-7892-4357-85ca-8d58ddc9c5cc%40googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
--
vn