Projects on the Seven Bridges Platform: some differences for AWS and Google Cloud users

Back to Blog

Projects on the Seven Bridges Platform: some differences for AWS and Google Cloud users

Projects on AWS and Google Cloud Platform

We recently deployed the Seven Bridges Platform on Google’s cloud infrastructure. This means that we can offer new Seven Bridges users a choice of underlying platform service provider: either Amazon Web Services (AWS), who have powered our Platform to date, or Google Cloud. Researchers who already store their data with one of these cloud services will be able to access and process it using the Seven Bridges Platform, without any time-consuming data transfer.

Independently of which cloud provider you choose, you will be able to access all the features of the Seven Bridges Platform. However, there are currently some temporary differences between the two deploys.

Since Seven Bridges made a fresh install of the Platform on Google Cloud, we decided to not include some of the Platform’s older features that we’re actively phasing out. Specifically, as you may have noticed, there are two kinds of project on the AWS deploy of the Seven Bridges Platform. We introduced developer projects alongside our regular project type last year, as a special kind of project in which you can install your own tools. We are now merging the two types, so that every project will have the functionality of a developer project. (Don’t worry though — no projects will be lost in the process!).

We decided to just get straight to this point with our Google Cloud deploy. For that reason, every project on the Google Cloud deploy of the Seven Bridges Platform is a ‘developer project’ by default.

We anticipate that the two project types on the AWS deploy will be fully merged in the next few months. After that point, the Seven Bridges Platform will look, feel and run identically on both environments.

The current difference between our two deploys means that, in places, the documentation is a little different for users of the AWS deploy and the Google Cloud deploy. Wherever this is the case, we’ll clearly signpost the difference.