Deploy

Once you are ready to deploy your app to lambda, it’s one command to do so:

jets deploy

After deployment, you can test the Lambda functions with the AWS Lambda console or the CLI.

Lambda Functions:

Minimal Deploy IAM Policy

The IAM user you are using to run the jets deploy command needs a minimal set of IAM policies in order to deploy a Jets application. For more info, refer to the Minimal Deploy IAM Policy docs.

Deploy to Different AWS Accounts

To deploy to different AWS accounts, use different AWS profiles. To set up the different AWS profiles refer to the AWS docs: Multiple AWS Profiles. Here’s an example for your convenience:

~/.aws/credentials:

[default]
aws_access_key_id=AKIAIOSFODNN7EXAMPLE
aws_secret_access_key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

[account2]
aws_access_key_id=AKIAI44QH8DHBEXAMPLE
aws_secret_access_key=je7MtGbClwBF/2Zp9Utk/h3yCo8nvbEXAMPLEKEY

~/.aws/config:

[default]
region=us-west-2
output=json

[profile account2]
region=us-east-1
output=json

To deploy to different accounts:

jets deploy
AWS_PROFILE=account2 jets deploy

Pro tip: Use the <- and -> arrow keys to move back and forward.

Edit this page

See a typo or an error? You can improve this page. This website is available on GitHub and contributions are encouraged and welcomed. We love pull requests from you!