Week in Review -- April 4, 2016

Last week was shorter for us due to Easter, but we managed to do more things in a shorter time.

Versions Management

We introduced simple management for transformation buckets. You are now able to rollback to the previous version of your transformation. Or simply copy one version to another.

Read more about Versions Management in previous post.


We're still working on our documentation to provide you with best support. Whether for easier components configurations or diving more into Keboola Connection in general.

Check our post about Documentation Changes.


Thanks to you, our users, we can detect anomalies (or bugs) in components faster. Thus after applying patches, components will be better for all, not only for issue reporters.

  • Small fixes have been applied to Keboola Connection UI
  • Bings Ads extractor, provided by David Ešner, has been updated

Support for Multi-Factor Authentication

Keboola Connection now supports Multi-Factor Authentication (sometimes called two-step verification) using Google Authenticator app. It can be activated in Account section accessible from user menu. You will need to download the app first, version for iPhone is here and for Android here. This feature adds verification by 6-digit code generated by the app after entering of username and password and so increases safety of your account.

Activation looks like this:

And login will look like this:

New Keboola Connection

Today we have launched a brand new user interface Keboola Connection. Some of you have been already working with it and giving us feedback for a while.

Now it is available for everyone, so you can start exploring it right now. There are no big or conceptual changes so we hope everything will be familiar to you. And you'll have your work done faster.

Just a few highlights:

  • Consistent behaviour, every action provides feedback.
  • Interface doesn't lie like the old one, and pending indicators are shown for all actions so you can be sure that everything is saved when your action is complete.
  • It should be more descriptive and should guide you, we know there is still lot of work ahead of us.
  • All extractors, writers and orchestrations can be renamed
  • Faster navigation and linked relations like jobs and component configurations

Finally it is a solid base for upcoming enhancements and features. Important areas are collaboration, project overview and monitoring, better understanding and organization of data, project changelog.

We’d also love to hear your feedback, you can reach us on support@keboola.com or if you want to be closer to development on our Github project page.

In case something went wrong you can still switch to the previous version by the link trick: just change the project url https://connection.keboola.com/admin/projects/YOUR_PROJECT_ID to https://connection.keboola.com/admin/projects-new/YOUR_PROJECT_ID yes, this one is old :) 


SSL security improvement

Please review the entire post carefully to determine whether your use of the services will be affected.

As of 12:00 AM PDT April 30, 2015, we will discontinue support of RC4 cipher for securing connections to connection.keboola.com. 

These requests will fail once we disable support for RC4 cipher for the Keboola Connection. To avoid interrupted access, you must update any client software (or inform any clients to update software) making the requests that are using RC4 cipher to connect to our API services.

Security improvements

We're announcing few security improvements:

  • All our servers, facing to clients, are using EV security certificates (what is EV?
  • All our servers have encrypted disks by using Amazon AWS KMS.
  • All our Elasticsearch clusters encrypt all events.
  • Amazon Redshift backends are encrypted by default. Existing customers can request to be moved to encrypted backends.
  • Storage API employ native Amazon S3 file encryption by default
  • All our Multi-AZ RDS metadata servers have encrypted data by default.
  • New Amazon RDS servers are encrypted by default. Existing customers can request to be moved to encrypted backends.

Long story short: if you're connecting to Keboola Connection, client facing servers are covered by strong encryption SSL with displayed identity in browser's address bar + all client's data in Keboola Connection are encrypted by default.