The best way to create an isolated set of credentials for use with Shippable Pipelines is to create a Kubernetes Service Account, and set up a kubeconfig file that utilizes it.

Amazon Web Services (IAM)

  1. Click on Integrations in the left sidebar menu followed by the '+' icon in the Account Integrations panel.

Add Azure DC/OS credentials

  1. Select deploy as the Integration family.
  2. Choose AWS (IAM) from the list of integration types.
  3. Integration Name: Use a distinctive name that's easy to associate to the integration and recall. Example: manishas-aws-iam
  4. Enter the ARN for the role shippable-role-to-allow-ecs-access. This will be a string with format like this arn:aws:iam::12345678912:role/shippable-role-to-allow-ecs-access. This role should be associated with a policy as defined here
  5. Click Save

Amazon ECS credentials

Amazon EC2 Container Service Using Account Keys

  1. Click on the gear icon for Account Settings in your top navigation bar and then click on the Integrations section.

Amazon ECS credentials

  1. Click on the Add Integration button.
  2. For Integration type, locate AWS from the list of integrations.
  3. For Integration Name use a distinctive name that's easy to associate to the integration and recall. Example: AWS-Integration.
  4. Enter your access and secret keys provided by AWS. See here for info on how to generate them. These keys should be associated with an account that has access to a policy with rules described here.
  5. Click on Save.

Amazon ECS credentials

Please remember that before you can use this integration to set up your Pipelines, you will need to enable the integration for the Subscription that contains your Pipelines.


The following policy document is required for Shippable to manage your deployments to ECS.

    "Version": "2012-10-17",
    "Statement": [
            "Effect": "Allow",
            "Action": [
            "Resource": "*"