Resolvers
Configuration options
| Option | Required | Type | Default | Description |
|---|---|---|---|---|
accessKeyId | No | String | AWS Access Key ID | |
secretAccessKey | No | String | AWS Secret Access Key | |
sessionToken | No | String | AWS Session Token | |
region | No | String | us-east-1 | AWS region |
profile | No | String | AWS profile name | |
dashboard | No | Boolean | true | Whether Serverless Dashboard AWS Provider credentials should be used |
Example
stages:
default:
resolvers:
aws-account-1:
type: aws
profile: account1-profile-name
region: us-west-2
accessKeyId: ${env:ACCOUNT1_AWS_ACCESS_KEY_ID}
secretAccessKey: ${env:ACCOUNT1_AWS_SECRET_ACCESS_KEY}
dashboard: false
Provider-specific variables
You can reference AWS-specific values as the source of your variables. Those values are exposed via the Serverless Variables system through:
{providerName:}variable prefix which should be the name of the resolver provider specified in theresolversblock (aws-account-1in the example above).{aws:}variable prefix which uses the deployment credentials.
The following variables are available:
accountId
Account ID of you AWS Account, based on the AWS Credentials that you have configured.
service: new-service
provider:
name: aws
functions:
func1:
name: function-1
handler: handler.func1
environment:
ACCOUNT_ID: ${aws:accountId}
region
The region used by the Serverless CLI. The ${aws:region} variable is a shortcut for ${opt:region, self:provider.region, "us-east-1"}.