serverless.yml

# Welcome to Serverless!
#
# This file is the main config file for your service.
# It's very minimal at this point and uses default values.
# You can always add more config options for more control.
# We've included some commented out config examples here.
# Just uncomment any of them to get that config option.
#
# For full config options, check the docs:
#    docs.serverless.com
#
# Happy Coding!

service: aws-step-functions

# You can pin your service to only deploy with a specific Serverless version
# Check out our docs for more details
# frameworkVersion: "=X.X.X"

provider:
  name: aws
  runtime: python3.6
  memorySize: 128 # megabytes, 128 or more
  stage: dev
  region: eu-central-1
  # NOTE: You need to create this AWS profile (IAM user) with the
  # proper permissions
  # It is called `serverless-admin` in the docs.
  profile: lambda-functions-dev
  # you can define service wide environment variables here
  environment:
    DYNAMODB_SHOPS_TABLE: ${self:service}-${self:provider.stage}-shopsTable
    DYNAMODB_SALES_TABLE: ${self:service}-${self:provider.stage}-salesTable
    SQS_APPLICATION_QUEUE: ${self:service}-${self:provider.stage}-applicationQueue
  # you can add statements to the Lambda function's IAM Role here
  iamRoleStatements:
    # First, our service needs to be able to access its DynamoDB data store
    - Effect: "Allow"
      Action:
        - "dynamodb:Query"
        - "dynamodb:Scan"
        - "dynamodb:GetItem"
        - "dynamodb:PutItem"
        - "dynamodb:UpdateItem"
        - "dynamodb:DeleteItem"
      Resource:
        - arn:aws:dynamodb:${opt:region, self:provider.region}:*:table/${self:provider.environment.DYNAMODB_SHOPS_TABLE}
        - arn:aws:dynamodb:${opt:region, self:provider.region}:*:table/${self:provider.environment.DYNAMODB_SALES_TABLE}
    # We also need access to the SQS message queue
    - Effect: "Allow"
      Action:
        - "sqs:GetQueueUrl"
        - "sqs:SendMessage"
      Resource:
        - arn:aws:sqs:${opt:region, self:provider.region}:*:${self:provider.environment.SQS_APPLICATION_QUEUE}

# you can add packaging information here
package:
  exclude:
    - ./**
  include:
    - functions/**

# You need to have these plugins for Serverless installed (see package.json)
plugins:
  - serverless-step-functions
  - serverless-pseudo-parameters

#
# The individual Lambda Functions are defined here
#
functions:
  hello:
    handler: functions/hello.hello
  upload-shops:
    handler: functions/shops.upload_shops
  list-shops:
    handler: functions/shops.list_shops
  upload-sales:
    handler: functions/sales.upload_sales
  generate-weekly-sales-report:
    handler: functions/sales.generate_weekly_report
  send-message:
    handler: functions/queue.send_message

#
# The Step Functions (workflows) are defined here
#
stepFunctions:
  stateMachines:
    upload-sales-step-function:
      name: ${self:service}-${self:provider.stage}-uploadSales
      events:
        - http:
            path: sales/upload
            method: POST
      definition:
        Comment: "Upload sales data"
        StartAt: UploadSalesData
        States:
          UploadSalesData:
            Type: Task
            Resource: arn:aws:lambda:${opt:region, self:provider.region}:#{AWS::AccountId}:function:${self:service}-${self:provider.stage}-upload-sales
            Next: CheckUploadStatus
          CheckUploadStatus:
            Type: Choice
            Choices:
            - Variable: "$.data.type"
              StringEquals: "sales-uploaded"
              Next: SendSalesDataUploadedEvent
            Default: ReturnError
          SendSalesDataUploadedEvent:
            Type: Task
            Resource: arn:aws:lambda:${opt:region, self:provider.region}:#{AWS::AccountId}:function:${self:service}-${self:provider.stage}-send-message
            Next: ReturnSuccess
          ReturnSuccess:
            Type: Succeed
          ReturnError:
            Type: Fail
            Cause: "Invalid sales data."
            Error: "Error."

#
# Declare the resources that we need to provision
#
resources:     # CloudFormation template syntax
  Resources:
    shopsTable:
      Type: AWS::DynamoDB::Table
      Properties:
        TableName: ${self:provider.environment.DYNAMODB_SHOPS_TABLE}
        # Note: DynamoDB is schemaless, except for the key attributes
        # defined here:
        AttributeDefinitions:
          -
            AttributeName: "shopNumber"
            AttributeType: "N"
        KeySchema:
          -
            AttributeName: "shopNumber"
            KeyType: "HASH"
        ProvisionedThroughput:
          ReadCapacityUnits: 1
          WriteCapacityUnits: 1
    salesTable:
      Type: AWS::DynamoDB::Table
      Properties:
        TableName: ${self:provider.environment.DYNAMODB_SALES_TABLE}
        # Note: DynamoDB is schemaless, except for the key attributes
        # defined here:
        AttributeDefinitions:
          -
            AttributeName: "shopNumber"
            AttributeType: "N"
          -
            AttributeName: "date"
            AttributeType: "S"
        KeySchema:
          -
            AttributeName: "shopNumber"
            KeyType: "HASH"
          -
            AttributeName: "date"
            KeyType: "RANGE"
        ProvisionedThroughput:
          ReadCapacityUnits: 1
          WriteCapacityUnits: 1
    applicationQueue:
      Type: "AWS::SQS::Queue"
      Properties:
        QueueName: ${self:provider.environment.SQS_APPLICATION_QUEUE}