Lambda backend allows provisioning infrastructure in Lambda Cloud while storing
artifacts in an S3 bucket.
Follow the step-by-step guide below to configure this backend in your project.
Set up storage¶
As Lambda Cloud doesn't have its own object storage,
dstack requires you to specify an S3 bucket,
along with AWS credentials, for storing state and artifacts.
Create an S3 bucket¶
First, you need to create an S3 bucket.
dstack will use this bucket to store state and artifacts.
Create an IAM user¶
The next step is to create an IAM user and grant this user permissions to perform actions on the
Logs and secrets
If you want
dstack to also store logs and secrets, you can optionally grant permissions
Create an access key¶
To create an access key,
follow this guide. Once the access key is created, make sure to download the
.csv file containing your IAM user's
Access key ID and
Secret access key.
Set up API key¶
Then, you'll need a Lambda Cloud API key. Log into your Lambda Cloud account, click
API keys in the sidebar, and then
Generate API key button to create a new API key.
Configure the backend¶
Now, log in to the UI, open the project's settings,
Edit, then click
Add backend, and select
Lambda in the
The following fields are required:
API key- (Required) The [API key] to authenticate
dstackwith Lambda Cloud
Regions- (Required) The list of regions where
dstackmay provision infrastructure. It is recommended to select as many regions as possible to maximize availability.
Storage- (Required) The storage provider that
dstackwill use to store the state and artifacts. Currently, only
Access key ID- (Required) The Access key ID to authenticate
Secret access key- (Required) The Secret access key to authenticate
Bucket- (Required) The S3 bucket to store state and artifacts