Deprecating Redshift Bucket Credentials

In November 2014, we were really happy to announce a new cool feature -- Read-only bucket credentials to your Redshift backend. Time has passed and we have decided to deprecate this feature.

Though accessing data in a bucket is very useful, with the current scenario it can lead to an assumption how data is stored and how it'll be stored in future. The latter is much worse, because any change in our backend can lead to breakage of the system, which was programmed to access the data in a bucket.

Thus, we recommend you to access your data in a more robust way:

  1. Create a new Redshift Writer
  2. Choose a database provided by Keboola or your own Redshift database
  3. Configure which tables you need to synchronize
  4. Run the newly configured writer
  5. Copy the credentials created in step 2 to the software which needs to access your data

The existing Bucket credentials continue to work until April 18, 2018. However, we strongly recommend to migrate to the Redshift Writer as soon as possible.

The creation of new credentials and credentials listing will be disabled in the Storage section with the publication of this post.

Also, the Bucket credentials have been marked as deprecated in our Storage API.