We want to emphasize that Qloudstat is engineered to allow access to your log files with dedicated access tokens that are under your control and can be revoked independently from your personal access credentials.
For AWS S3 and AWS CloudFront configurations instead of using your personal access and secret key the best option is to set up an IAM (AWS Identity and Access Management) user in the AWS console. When setting up a new configuration in Qloudstat, you can follow the step-by-step instructions recommended.
Adding a Google Cloud Storage configuration will prompt you for the x-goog-project-id and a token to authorize access for Qloudstat issued with OAuth 2.0 authentication with the permission to read log files from your account without revealing personal access credentials. The token issued is under your control and can always be revoked using your Google Account settings.
We are working together with Rackspace to offer a similar technical solution to access Cloudfiles Akamai CDN access logs. Currently this configuration requires the shared credentials for API access to Cloudfiles.