This is a deprecated feature of the dashboard. Please look at our documentaion for Providers and Parameters which replaces the use of deployment profiles for setting up AWS connections and parameters.
Prior to the January 11th, 2021 release, deployment profiles supported setting AWS Access Role ARNs and managing parameters. Support for using AWS Access Roles for deployments has moved from deployment profiles to Providers. Support for managing Parameters has moved from deployment profiles to services and instances.
Deployment profiles will be deprecated on February 28th, 2021. Migration from deployment profiles to providers and parameters will be automatic; however, there are two required action items to use the new features.
Parameters and Providers were migrated automatically from deployment profiles on January 31st, 2021.
The automatic migration replaced deployment profiles with providers by performing the following:
app1links to the
devdeployment profile, then the
devprovider will be added to
service1. This is repeated for all services in all apps.
app1has a stage
prodlinked to the
proddeployment profile, then the
prodprovider will be added to the
service1instances deployed to the
Deployment profiles are managed in the Serverless Framework Dashboard. When you run
serverless deploy, the CLI obtains the Safeguard policies, Parameters, and the generated AWS Credentials.
Create a new deployment profile by navigating to profiles in the Serverless Framework Dashboard and click add.
This is a user-readable name for the deployment profile. Most often it has a name that maps to a stage (e.g. “dev”, “prod”), or in larger organizations the line of business or environment (e.g. “apac-banking-prod”). This name will uniquely identify the deployment profile when associating it with a stage in an application.
The description helps provide additional context when listing the deployment profiles.
Access Roles, Parameters and Safeguards have individual configuration guides:
Create a new stage by navigating to applications in the Serverless Framework Dashboard.
You can also set the default deployment profile field in the application. You can use this to set the deployment profile on all services in that application. When deploying to a stage which hasn't be defined in the dashboard, then the default deployment profile will be used.
When you run
serverless deploy Serverless Framework will obtain the AWS Access Key, Parameter and Safeguards associated with the deployment profile configured for that application and stage based on the values for
stage in your
The Serverless Framework will first try to match the current stage from
serverless.yml with a stage configured on that application in the dashboard. If they match, it will use the deployment profile associated with that stage. If the stages do not match, then the default deployment profile from that application will be used.