Skip to content
Slipwaydocs

AWS

Deploy to ECS, Lambda and EKS; read CloudWatch; federate with STS.

At a glance

Section titled “At a glance”
Category Cloud & Kubernetes
Authentication IAM role assumed with the job OIDC token (AssumeRoleWithWebIdentity)
Provider id aws

What it does

Section titled “What it does”
  • ECS service deployments (rolling, blue/green)
  • Lambda function and alias deployments
  • EKS via Kubernetes integration
  • CloudWatch metrics for verification

Set up

Section titled “Set up”
  1. Create the IAM OIDC identity provider for your Slipway issuer (see OIDC with AWS).
  2. Create a role whose trust policy matches the claims you want to allow (project, environment, ref).
  3. Add the AWS integration and enter the role ARN and region.
  4. Create an ECS or Lambda infrastructure on the environment and run Test infrastructure.

Configuration

Section titled “Configuration”

Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.

provider: aws
config:
  region: eu-west-1
  role_arn: arn:aws:iam::123456789012:role/slipway-deploy
  # no access keys: the runner exchanges its job token for STS credentials
Section titled “Related”