Amazon Web Services on Spinnaker

Amazon EC2

Mon, 01 Jan 0001 00:00:00 +0000

An older doc is available that has some information around installing spinnaker but is no longer recommended nor supported AWS tutorial: Continuous Delivery using Spinnaker on Amazon EKS .

The AWS EC2 Provider allows you to deploy AWS EC2 resources with Spinnaker. The most common use case is the creation of AMIs and deploying the AMI’s to new autoscaling groups and then deleting the previous autoscaling groups.

Refer to the AWS Cloud Provider Overview to understand how AWS IAM must be set up with the Spinnaker AWS EC2 provider. It’s recommended to use node/pod roles to access AWS services and resources securely.

Amazon ECS

Mon, 01 Jan 0001 00:00:00 +0000

In the Amazon ECS cloud provider, an Account maps to a Spinnaker AWS account, which itself is able to authenticate against a given AWS account .

Prerequisites

Amazon ECS cluster

You need to create an Amazon ECS cluster . If using the ‘EC2’ launch type, this cluster must have enough EC2 instance capacity in it to deploy your containers. If using the ‘Fargate’ launch type, you don’t need to add any capacity to this cluster.

Amazon Web Services Concepts

Mon, 01 Jan 0001 00:00:00 +0000

Concepts

There are two types of Accounts in the Spinnaker AWS provider:

AWS Managing account
AWS Managed account(s).

Note The AWS IAM structure must be set up prior to adding the accounts to spinnaker.

From the AWS perspective, AWS Managing account assumes control of the AWS Managed account(s) through the use of AWS IAM Roles. By assuming a role across AWS Accounts, Spinnaker can control AWS resources from multiple AWS Managed accounts.