Using S3 with Spinnaker instead of Cassandra Backend

Aug 22, 2016 by Ben Mappen

Cassandra is used by Spinnaker to persist pipelines configuration and cluster information. While Cassandra may suit your needs it might be overkill for POCs or early development phases where the number of configurations and continuous deployments are small. While Spinnaker can be configured to have an Amazon S3 backend, it’s not always trivial to setup.

You might find an error in the front50 log that looks like the following:

org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type [com.netflix.spinnaker.front50.model.pipeline.PipelineDAO] is defined: expected single matching bean but found 2: pipelineRepository,s3PipelineDAO

Setting an Active Spring Profile

Spinnaker heavily relies on the Spring framework. The Spring framework expects there only one object that matches the interface for a backend repository.

You can change the default options passed into spinnaker by editing the defaults file for spinnaker /etc/default/spinnaker

in there you can change the default active profile by setting the java front50 options to the following:

FRONT50_OPTS="-Dspring.profiles.active=s3"

Another common mistake is that folks forget to disable Cassandra in their front50.yml which you can find at /opt/spinnaker/config. Make the following change:

    enabled: false```
Hope these changes help!
If you haven't heard of Spinnaker, its a next generation cloud deployment tool originally built by Netflix and subsequently open-sourced.  It's best know for continuous delivery at Netflix and helping them achieve more than 4,000 deployments/day.  It's currently being contributed to by over 30 developers from Google, Pivotal, Netflix, Veritas and Microsoft.

Share this post:

Recently Published Posts

Navigating AWS Deployment Targets with Armory

Jan 20, 2023

Many organizations look to Amazon Web Services (AWS) to host and deploy their applications in the cloud. However, they’re finding that their deployment tooling, often built as an extension of their legacy continuous integration (CI), is one of the main impediments to adopting cloud services.  Custom-scripted production pipelines built with in-house tooling need to be […]

Read more

Release Roundup – January 2023

Jan 11, 2023

Get the latest product news on Continuous Deployment-as-a-Service and the most recent release for Continuous Deployment Self Hosted, 2.28.2. Welcome to 2023!  Just like every organization, Armory is looking for ways to improve our practices and deliver more value (and faster!) to you, our customers. That’s why our engineering team is working to deliver features, […]

Read more

Learn Continuous Deployment with Armory and Wilco

Jan 6, 2023

Armory is excited to announce we have launched an interactive, narrative-driven developer experience that teaches continuous deployment concepts. And now you can try it out for yourself! Wilco, also known as the “flight simulator” for software developers, allows companies to create engaging interactive developer challenges (called quests) that enable developers to acquire and practice skills […]

Read more