Merge pull request #4612 from mitchellh/fix4553

document how aws-sdk uses the shared credentials file
This commit is contained in:
Matthew Hooker 2017-03-01 16:45:58 -08:00 committed by GitHub
commit f830fdd28e
1 changed files with 6 additions and 3 deletions

View File

@ -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 name set in the `AWS_PROFILE` environment variable. If
the environment variable is not set, uses "default" as the profile name.
3. Lookup an IAM role for the current EC2 instance (if you're running in EC2)