I am trying to use bucket explorer this morning to update some of my buckets and I'm getting failed to authenticate errors...

I was having no problem using the system a couple weeks ago. Any chance there was a change to AWS that has somehow caused this problem?

My buckets on S3 seem to be working fine otherwise.

HELP!

Ok, I just noticed this:

I'm seeing a message in the bottom of bucket explorer that says

"The difference between the request time and the current time is too large"

Is it possible that this is a daylight savings bug?

I can't be the first person to attempt to use this since this weekend can I?

Please help... thanks!

So, on a hunch, I decided to set my local clock back 1 hour to reverse the effects of daily savings time...

And now I CAN log in...

Not sure if this is an S3 bug or a Bucket Explorer bug...

Brad wrote:So, on a hunch, I decided to set my local clock back 1 hour to reverse the effects of daily savings time...

And now I CAN log in...

Not sure if this is an S3 bug or a Bucket Explorer bug...

The time zone on your machine has to match with the time set on the machine. Also if there is a DST patch from your machine's OS vendor (Windows?), you need that patch installed. Basically Bucket Explorer takes the current time on your machine, matches it with the time zone, calculates the time in GMT and then sends that to Amazon. If that time is not correct GMT time, Amazon does not allow Authentication.

We will be releasing a new version of Bucket Explorer shortly, which should try to fix the time zone problems in most cases automatically.

i'm confused. by "system time" do we mean the time running under Windows or the motherboard clock in MDOS when one starts the computer?
And what time does Amazon use so everyone knows what to calibrate to?

ok. whatever the problem was, looking through dozens of posts online, i finally found Bucket Explorer automatically calibrates your computer time with amazon s3. the other way was too complicated.