Skip to main content
All CollectionsSupport
Testing for S3 RequestTimeTooSkewed error
Testing for S3 RequestTimeTooSkewed error
Brent Sanders avatar
Written by Brent Sanders
Updated over a week ago

Set the identity of the server to check

From the salt-master

identity={server-identity}

CMD to look at S3 date (first) and local date (second) to see difference

salt "${identity}" cmd.run "curl http://s3.amazonaws.com -v 2>&1 | grep -E -i -w '< Date:' | awk '/<\sDate:\s/ { gsub(/<\sDate:\s/, \"\") }; { print }'" && salt "${identity}" cmd.run 'date -u +%a,\ %e\ %b\ %Y\ %T\ %Z'

CMD to run to see if we get a (RequestTimeTooSkewed) error

ย salt "${identity}" cmd.run 'export AWS_ACCESS_KEY_ID=AKIAJEBQ4AEFLNMPUB4A; export AWS_SECRET_ACCESS_KEY=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; export AWS_DEFAULT_REGION=us-east-1; aws s3 ls s3://ottomatik-test-us-std'

Solution

๐ŸŽ‰๐ŸŽ‰๐ŸŽ‰

We hope you find this helpful! If you need any further assistance, please contact us and we'll be more than glad to help you out.ย 

Did this answer your question?