Netflix Spinnaker: multi-cloud continuous integration tool

With the release of the open source Netflix Spinnaker delivery platform, the cloud-savvy video on demand company signals that the cloud is bigger than AWS

Video on demand provider Netflix has been successfully running much of their operation in the AWS cloud for six years now, and the relationship has been mutually beneficial. If people are talking about AWS, then the odds are that you’ll hear something about Netflix: whether it’s how they migrated their huge workload to AWS, their Simian Army resilience testing tool, or how well Netflix manages AWS outages. Now you can add Netflix Spinnaker to the conversation.

In a blog post a few months ago, Netflix first mentioned Spinnaker, an open source, multi-cloud deployment tool that was then under development. The post mentioned how the company was planning to move to Spinnaker from its own Asgard. The Netflix Spinnaker code is now publicly available.

What is Netflix Spinnaker?

According to Netflix:

Netflix Spinnaker is an open source multi-cloud Continuous Delivery platform for releasing software changes with high velocity and confidence. Spinnaker is designed with pluggability in mind; the platform aims to make it easy to extend and enhance cloud deployment models. To create a truly extensible multi-cloud platform, the Spinnaker team partnered with Google, Microsoft and Pivotal to deliver out-of-the-box cluster management and deployment. As of today, Spinnaker can deploy to and manage clusters simultaneously across both AWS and Google Cloud Platform with full feature compatibility across both cloud providers. Spinnaker also features deploys to Cloud Foundry; support for its newest addition, Microsoft Azure, is actively underway.

It’s very interesting that Netflix, which has always relied on AWS for its infrastructure, has now built a tool to migrate or deploy on AWS or Google Cloud Platform and Pivotal. Are they trying to reduce their dependency on a sole vendor?

Netflix Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes. It provides both Cluster and Deployment management.

Cluster Management

Cluster Management deals with cloud resources like:

  • Server Groups. Collections of cloud-based virtual machines (VMs) built from AMIs or images. A server group can also be associated with a load balancer, Security Group, user information, region and availability zones.
  • Load Balancers. Protocols for managing traffic loads associated with a server group.
  • Security Groups. Rules defining network traffic access and firewall rules according to IP range (CIDR), communication protocol (e.g., TCP) and port range.
  • Clusters. User-defined, logical groupings of Server Groups within Spinnaker.

Deployment Management

Netflix Spinnaker deployment management provides for continuous integration and workflow. It facilitates the creation of pipelines that represent a delivery process that can begin with the creation of some deployable asset (such as a machine image, JAR file, or Docker image) and end with a deployment.

  • Pipeline. The key deployment management construct in Netflix Spinnaker. Pipelines are defined by a sequence of stages, triggers that kick off the pipeline, and parameters that get passed between pipeline stages and can be configured to issue notifications (via email, SMS or HipChat) as the pipeline executes. Triggers can be either automatic – like a Jenkins job, CRON schedule, or another pipeline – or manual.
  • Stage. A Stage in Spinnaker represents different phases in a pipeline’s lifecycle. Spinnaker comes pre-packaged with a number of stages, including:
    • Bake: Bakes an image within the specified region.
    • Deploy: Deploys a previously baked or found image.
    • Destroy Server Group: Destroys a server group.
    • Disable Server Group: Disables a server group.
    • Enable Server Group: Enables a server group.
    • Find Image: Finds a previously-baked image to deploy into an existing cluster.
    • Jenkins: Runs a Jenkins job.
    • Manual Judgment: Waits for user approval before continuing.
    • Modify Scaling Process: Suspend or resume server group scaling processes.
    • Pipeline: Runs a pipeline. This allows pipelines to be composed hierarchically.
    • Quick Patch Server Group: Quick patches a server group. Used for emergency patches.
    • Resize Server Group: Resizes a server group.
    • Script: Runs an arbitrary shell script.
    • Shrink Cluster: Shrinks a cluster.
    • Wait: Waits a specified period of time.

Netflix Spinnaker Components:

Spinnaker includes the following micro services:

  • Clouddriver: encapsulates all cloud operations.
  • Deck: user interface.
  • Echo: the event service that is responsible for triggering pipeline executions and forwarding pipeline events to listeners.
  • Front50: data store for pipelines, notifications and applications.
  • Gate: service gateway responsible for providing an API and UI to end users.
  • Igor: interface to Jenkins, Stash, and GitHub.
  • Orca: orchestration engine responsible for running Spinnaker pipelines and tasks.
  • Rosco: bakery responsible for creating images for deployment.
  • Rush: general purpose scripting engine.
Netflix Spinnaker

(Netflix Spinnaker components – courtesy: Netflix)

Setting Up Netflix Spinnaker

Setting up Spinnaker for development takes just a few steps. These instructions cover pulling Spinnaker from source and setting it up to run locally against Amazon Web Services and/or Google Cloud Platform accounts. We will then see how Spinnaker is configured for the AWS Cloud from a developer machine.
Before jumping in, make sure you have an AWS account. We’ll follow the steps from the Spinnaker getting started guide:

Create an EC2 role

  • Create a New Role in AWS Identity & Access Management (IAM) and set the Role Name to BaseIAMRole. EC2 instances launched with Spinnaker will be associated with this role.

Create an EC2 Key Pair

  • Create a Key Pair and name the key pair <aws_account_name>-keypair (note: this must match your account name plus “-keypair”).
  • Download the private key file <aws_account_name>-keypair.pem and change its permissions:
chmod 400 aws_account_name-keypair.pem

Create AWS credentials for Spinnaker

  • Create a new user in IAM. Create an access key for the user. Save the access key and secret key into the ~/.aws/credentials file on your workstation.
  • Click the checkbox next to PowerUserAccess in IAM, then click Attach Policy.
  • Create an inline policy with “Select for Policy Generator”.
  • From the IAM Policy Generator, select “AWS Identity and Access Management” as an AWS Service, and then “PassRole” for Actions.
  • Type * (the asterisk character) and “Apply Policy”.


The bootstrap scripts are meant to run on Ubuntu 14.04 LTS and Mac OS X 10.11. Here’s now it works on Ubuntu:

  • Clone the Spinnaker from GitHub. Make sure you have git version 2.0 and above.
git clone
  • Set the path as follows:
export SPINNAKER_HOME=/path/to/your/Spinnaker/workspace

Configure the Environment:

  • Before setting up Spinnaker, make sure your workstation meets the following dependencies.
    • JDK8
    • Redis
    • Cassandra
    • Packer
  • Run the following scripts:

Configure Spinnaker:

  • Create a directory for Spinnaker configuration overrides, copy the default configuration template there, and edit to select the appropriate cloud provider(s). Here we will have for AWS.
mkdir -p $HOME/.spinnaker spinnaker/config/default-spinnaker-local.yml
chmod 600 $HOME/.spinnaker/spinnaker-local.yml
  • If you are deployed on a supported cloud provider (e.g., AWS or Google) and you only wish to deploy on that platform, then you do not need to perform additional configuration. Otherwise, edit $HOME/.spinnaker/spinnaker-local.yml, enable the cloud provider(s) of your choice, and configure the attributes for that provider. Here we will enable only AWS.

Start the Netflix Spinnaker Service

  • To start the Spinnaker Service, execute following:
../spinnaker/dev/ [service]
  • If a service is provided, then just that one service will be started. If no service is provided, then all the services will be started.

Stop the Netflix Spinnaker Service

  • To Stop Spinnaker (except Redis and Cassandra), run following:
../spinnaker/dev/ [service]


This has been just a quick introduction to Netflix Spinnaker. With support for many cloud vendors and even containers like Docker, this looks like a very promising package. We hope to bring you more posts on Spinnaker in coming weeks to demonstrate how it can be installed on AWS and Google Cloud Platform, and how it can manage clusters and workflows.


Written by

Chandan Patra

Cloud Computing and Big Data professional with 10 years of experience in pre-sales, architecture, design, build and troubleshooting with best engineering practices.Specialities: Cloud Computing - AWS, DevOps(Chef), Hadoop Ecosystem, Storm & Kafka, ELK Stack, NoSQL, Java, Spring, Hibernate, Web Service

Related Posts

John Chell
— June 13, 2019

AWS Certified Solutions Architect Associate: A Study Guide

The AWS Solutions Architect - Associate Certification (or Sol Arch Associate for short) offers some clear benefits: Increases marketability to employers Provides solid credentials in a growing industry (with projected growth of as much as 70 percent in five years) Market anal...

Read more
  • AWS
  • AWS Certifications
Chris Gambino and Joe Niemiec
Chris Gambino and Joe Niemiec
— June 11, 2019

Moving Data to S3 with Apache NiFi

Moving data to the cloud is one of the cornerstones of any cloud migration. Apache NiFi is an open source tool that enables you to easily move and process data using a graphical user interface (GUI).  In this blog post, we will examine a simple way to move data to the cloud using NiFi c...

Read more
  • AWS
  • S3
Chandan Patra
— June 11, 2019

Amazon DynamoDB: 10 Things You Should Know

Amazon DynamoDB is a managed NoSQL service with strong consistency and predictable performance that shields users from the complexities of manual setup.Whether or not you've actually used a NoSQL data store yourself, it's probably a good idea to make sure you fully understand the key ...

Read more
  • AWS
  • DynamoDB
Andrew Larkin
— June 6, 2019

The 11 AWS Certifications: Which is Right for You and Your Team?

As companies increasingly shift workloads to the public cloud, cloud computing has moved from a nice-to-have to a core competency in the enterprise. This shift requires a new set of skills to design, deploy, and manage applications in cloud computing.As the market leader and most ma...

Read more
  • AWS
  • AWS Certifications
Sam Ghardashem
Sam Ghardashem
— May 15, 2019

Aviatrix Integration of a NextGen Firewall in AWS Transit Gateway

Learn how Aviatrix’s intelligent orchestration and control eliminates unwanted tradeoffs encountered when deploying Palo Alto Networks VM-Series Firewalls with AWS Transit Gateway.Deploying any next generation firewall in a public cloud environment is challenging, not because of the f...

Read more
  • AWS
Joe Nemer
Joe Nemer
— May 3, 2019

AWS Config Best Practices for Compliance

Use AWS Config the Right Way for Successful ComplianceIt’s well-known that AWS Config is a powerful service for monitoring all changes across your resources. As AWS Config has constantly evolved and improved over the years, it has transformed into a true powerhouse for monitoring your...

Read more
  • AWS
  • Compliance
Francesca Vigliani
— April 30, 2019

Cloud Academy is Coming to the AWS Summits in Atlanta, London, and Chicago

Cloud Academy is a proud sponsor of the 2019 AWS Summits in Atlanta, London, and Chicago. We hope you plan to attend these free events that bring the cloud computing community together to connect, collaborate, and learn about AWS. These events are all about learning. You can learn how t...

Read more
  • AWS
  • AWS Summits
Paul Hortop
Paul Hortop
— April 2, 2019

How to Monitor Your AWS Infrastructure

The AWS cloud platform has made it easier than ever to be flexible, efficient, and cost-effective. However, monitoring your AWS infrastructure is the key to getting all of these benefits. Realizing these benefits requires that you follow AWS best practices which constantly change as AWS...

Read more
  • AWS
  • Monitoring
Joe Nemer
Joe Nemer
— April 1, 2019

AWS EC2 Instance Types Explained

Amazon Web Services’ resource offerings are constantly changing, and staying on top of their evolution can be a challenge. Elastic Cloud Compute (EC2) instances are one of their core resource offerings, and they form the backbone of most cloud deployments. EC2 instances provide you with...

Read more
  • AWS
  • EC2
Nitheesh Poojary
— March 26, 2019

How DNS Works – the Domain Name System (Part One)

Before migrating domains to Amazon's Route53, we should first make sure we properly understand how DNS worksWhile we'll get to AWS's Route53 Domain Name System (DNS) service in the second part of this series, I thought it would be helpful to first make sure that we properly understand...

Read more
  • AWS
Stuart Scott
— March 14, 2019

Multiple AWS Account Management using AWS Organizations

As businesses expand their footprint on AWS and utilize more services to build and deploy their applications, it becomes apparent that multiple AWS accounts are required to manage the environment and infrastructure.  A multi-account strategy is beneficial for a number of reasons as ...

Read more
  • AWS
  • Identity Access Management
Sanket Dangi
— February 11, 2019

WaitCondition Controls the Pace of AWS CloudFormation Templates

AWS's WaitCondition can be used with CloudFormation templates to ensure required resources are running.As you may already be aware, AWS CloudFormation is used for infrastructure automation by allowing you to write JSON templates to automatically install, configure, and bootstrap your ...

Read more
  • AWS
  • CloudFormation