document how aws-sdk uses the shared credentials file

from https://docs.aws.amazon.com/sdk-for-go/api/aws/credentials/\#SharedCredentialsProvider
pull/4612/head
Matthew Hooker 9 years ago
parent 9de8545875
commit 6b95de73c4
No known key found for this signature in database
GPG Key ID: 7B5F933D9CE8C6A1

@ -27,7 +27,7 @@ Packer supports the following builders at the moment:
that device. This is an **advanced builder and should not be used by
newcomers**. However, it is also the fastest way to build an EBS-backed AMI
since no new EC2 instance needs to be launched.
- [amazon-ebssurrogate](/docs/builders/amazone-ebssurrogate.html) - Create EBS
-backed AMIs from scratch. Works similarly to the `chroot` builder but does
not require running in AWS. This is an **advanced builder and should not be
@ -78,8 +78,11 @@ following steps:
2. Look for [local AWS configuration
files](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html#cli-config-files)
- First `~/.aws/credentials`
- Next based on `AWS_PROFILE`
- Looks for the credentials file in the `AWS_SHARED_CREDENTIALS_FILE`
environment variable, and if that's empty, use the default credentials
file (`.aws/credentials`) in the user's home directory.
- Uses the profile set in the `AWS_PROFILE` environment variable. If the
environment variable is not set, uses "default" as the profile.
3. Lookup an IAM role for the current EC2 instance (if you're running in EC2)

Loading…
Cancel
Save