iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add the error you might see

This commit is contained in:
Matthew Hooker 2016-10-03 17:36:54 -07:00
parent 7a1b84cec1
commit 24c4ba3bb5
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/builders/amazon.html.md
View File

@ -161,7 +161,11 @@ work, but specifics will depend on your use-case.
Amazon uses the current time as part of the [request signing Amazon uses the current time as part of the [request signing
process](http://docs.aws.amazon.com/general/latest/gr/sigv4_signing.html). If process](http://docs.aws.amazon.com/general/latest/gr/sigv4_signing.html). If
your system clock is too skewed from the current time, your requests might your system clock is too skewed from the current time, your requests might
fail. If you suspect your system's date is wrong, you can compare it against fail. If that's the case, you might see an error like this:
==> amazon-ebs: Error querying AMI: AuthFailure: AWS was not able to validate the provided access credentials
If you suspect your system's date is wrong, you can compare it against
http://www.time.gov/. On Linux/OS X, you can run the `date` command to get the http://www.time.gov/. On Linux/OS X, you can run the `date` command to get the
current time. If you're on Linux, you can try setting the time with ntp by running current time. If you're on Linux, you can try setting the time with ntp by
`sudo ntpd -q`. running `sudo ntpd -q`.