Providers¶
AWS¶
AWS Account/Credentials¶
You’ll need AWS security credentials set anywhere on your system, either as env
vars or under ~/.aws/credentials
. See:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-files.html
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html
For details on how to set those up.
cedana-cli
will need an EC2 ssh key pair set up too, which you can set up using the following guide:
Or by running cedana-cli bootstrap
, which will guide you through the process and create one for you.
Launch Templates¶
You will also need an empty launch template for each region you’d like Cedana to work in - as a placeholder (since the AWS API requires a launch template name to be specified). You can follow the instructions here to create one or let cedana-cli bootstrap
do it for you (and associate a key + security group for you as well).
The most important configuration here is to specify the ssh key pair that you created in the previous step, as it allows cedana-cli
(and you) SSH access to the instance.
Everything that Cedana needs to get up and running will be installed onto the instance at instantiation time.
Necessary IAM Permissions¶
For reference (and for IT/Security teams), Cedana requires the following IAM permissions:
ec2:RequestSpotInstances
ec2:CreateTags
ec2:DescribeInstanceTypes
ec2:DescribeSpotInstanceRequests
ec2:DescribeInstances
ec2:TerminateInstances
ec2:CancelSpotInstanceRequests
You can use these to carve out IAM scopes for the system.
Paperspace¶
To get started with using your Paperspace account with Cedana, you’ll need to set up an API key and hook up a public ssh key. You can find instructions for both below:
https://docs.paperspace.com/account-management/account/security/api-keys/
https://docs.paperspace.com/account-management/account/security/ssh-keys
And that’s it!
If there’s a provider you’d like added to the marketplace, reach out to founders@cedana.ai.