AWS Setup#

You can use the coiled setup aws CLI tool to connect Coiled to your AWS account, which relies on your local AWS credentials:

coiled setup aws


No local AWS credentials?

If you use AWS as part of a larger organization or company, you may need to contact your admin for access.

For individuals, you can use AWS CloudShell, which already has the AWS CLI installed and configured with your AWS credentials. You can use the --cloudshell-link parameter to print instructions specific to your Coiled account:

coiled setup aws --cloudshell-link

With your permission, this command will create the IAM policies and infrastructure Coiled needs so you can create clusters in your AWS account. You will be prompted with an explanation at each step, so you can choose to say “yes” (or “no”) at any point (see Configuring AWS for more details).

Here’s a demonstration of the process:


Especially if you are using a new AWS account, you may encounter a LimitExceeded error (e.g. VcpuLimitExceeded). You can view and adjust quota limits using the coiled setup aws --quotas (see Quotas).

coiled setup aws#

coiled setup aws [OPTIONS]


--iam-user <iam_user>#

IAM User to create in your AWS account

--setup-policy <setup_policy>#

Non-default name for the setup IAM Policy, default {iam-user}-setup

--ongoing-policy <ongoing_policy>#

Non-default name for the ongoing IAM Policy, default {iam-user}-ongoing

--profile <profile>#

AWS profile to use from your local AWS credentials file


Only update existing IAM Policies


Update instance policy (not for regular use)

Don’t do setup, give instructions for setup using CloudShell

--region <region>#

AWS region to use when setting up your VPC/subnets


Don’t automatically send credentials to Coiled, finish setup manually in the web UI


Check and potentially request AWS quota increases for common instance types

-y, --yes#

Don’t prompt for confirmation, just do it!

Environment variables


Provide a default for --profile