sls deploy command deploys your entire service via CloudFormation. Run this command when you have made infrastructure changes (i.e., you edited
serverless deploy function -f myFunction when you have made code changes and you want to quickly upload your updated code to AWS Lambda or just change function configuration.
-cName of your configuration file, if other than
-sThe stage in your service that you want to deploy to.
-rThe region in that stage that you want to deploy to.
-ppath to a pre-packaged directory and skip packaging step.
--verboseShows all stack events during deployment, and display any Stack Output.
--forceForces a deployment to take place.
deploy function(see above). Convenience shortcut - cannot be used with
--concealHides secrets from the output (e.g. API Gateway key values).
--aws-s3-accelerateEnables S3 Transfer Acceleration making uploading artifacts much faster. You can read more about it here. It requires additional
s3:PutAccelerateConfigurationpermissions. Note: When using Transfer Acceleration, additional data transfer charges may apply.
--no-aws-s3-accelerateExplicitly disables S3 Transfer Acceleration. It also requires additional
serverless deploy command runs, the framework runs
serverless package in the background first then deploys the generated package.
This is the simplest deployment usage possible. With this command Serverless will deploy your service to the defined
provider in the default stage (
dev) to the default region (
serverless deploy --stage production --region eu-central-1
With this example we've defined that we want our service to be deployed to the
production stage in the region
serverless deploy --package /path/to/package/directory
With this example, the packaging step will be skipped and the framework will start deploying the package from the
SLS_AWS_MONITORING_FREQUENCYallows the adjustment of the deployment monitoring frequency time in ms, default is
SLS_AWS_MONITORING_FREQUENCY=10000 serverless deploy