Resolvers

• AWS S3
• AWS SSM Parameter Store & Secrets Manager
• AWS CloudFormation Outputs

Configuration options

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:

1. {providerName:} variable prefix which should be the name of the resolver provider specified in the resolvers block (aws-account-1 in the example above).
2. {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"}.

partition

The AWS partition for the resolved region, derived locally with no AWS API call. This is useful for building ARNs that work across partitions such as AWS GovCloud (US) and China, where the ARN prefix is aws-us-gov or aws-cn instead of aws.

All AWS partitions are supported, including the isolated and sovereign ones: aws-iso, aws-iso-b, aws-iso-e, and aws-iso-f (US ISO regions) and aws-eusc (European Sovereign Cloud).

Unknown regions fall back to aws, matching the behavior of the CloudFormation AWS::Partition pseudo-parameter.

service: new-service
provider:
  name: aws

functions:
  func1:
    name: function-1
    handler: handler.func1
    environment:
      QUEUE_ARN: arn:${aws:partition}:sqs:${aws:region}:${aws:accountId}:my-queue