Do I need to enable logging within S3Stat if it's already done at Amazon S3?
I keep getting the error We were unable to access this bucket to modify logging.
This sometimes happens with recently created IAM User accounts. If you've just signed up for S3stat and immediately ran into this error, chances are that's what happened.
The only solution might be to go grab a cup of coffee and come back in an hour to try again. Hopefully by then your new IAM User's permissions will have trickled down to this bucket and we'll be able to set it up for you.
Sorry for the inconvenience.But I suspect that since it's already turned on at S3 end, its not required?? Or is it required?Thanks
foundersgyan
Monday, July 18, 2016
If you have logging in place for your endpoints, we'll leave it alone and use the settings that we detect. The error message you pasted is what we show if we can't access your account using the credentials you provided. So if you're seeing it, chances are you went off script with your permissions and left us unable to read the things we need.
Jason Kester
Tuesday, July 19, 2016
Looks like this was an issue at our end. We didn't detect that your
bucket was in the "ap-south-1" Region, so our attempts to connect to
it failed.Amazon added this new Region somewhat out of the blue this week, and the first we learned of its existence was when new endpoints started breaking.We've fixed the immediate issue and added checking to detect new Regions as they come online, so with luck this won't happen again.
Jason Kester
Wednesday, August 3, 2016
[ reply to this topic ]
[ return to topic list ]
|