By default, Coiled will run on AWS inside our own AWS account. This makes it easy for you to get started quickly, without needing to set up any additional infrastructure. However, you can run Coiled on different cloud provider backends depending on your needs.
Configure Backend Options
You can configure which cloud provider (i.e., “backend”) that you want Coiled to use for provisioning Dask clusters by visiting the “Account” page of your Coiled account at https://cloud.coiled.io/<account-name>/account. More information about the currently supported providers is available below.
As mentioned above, Coiled will default to using AWS as a cloud provider, using Coiled’s own AWS account. This makes it easy for you to get started quickly.
If you prefer to run Coiled-managed computations within your own AWS infrastructure for security or billing purposes, you need to do two main things: (1) configure an IAMs user account with the correct permissions, and secure credentials for that user account (2) Provide those credentials to Coiled via the UI using the 'edit' option under 'Cloud Backend Options' on the UI Account page.
Please refer to our docs for detailed instructions.
If you prefer to use Google Cloud Platform (GCP), you can run Coiled on GCP to run your computations. Coiled can be configured to run on Coiled’s GCP account or your own GCP account.
As above, you can choose to launch in Coiled's GCP account via the UI's Account page and the 'Cloud Backend Options' dialog, or you can use your own credentials as for AWS, above. Here, the overall steps are: (1) Securing credentials for a service account (2) Creating a suitable custom role and connecting it ot the service account (3) enabling a Google Artifact Registry for that account.
As above, please refer to our docs for detailed instructions.