-
Notifications
You must be signed in to change notification settings - Fork 0
/
serverless.yml
90 lines (80 loc) · 2.57 KB
/
serverless.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
# 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-lambdaServerless-bl # NOTE: update this with your service name
# 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: nodejs4.3
profile: default
# you can overwrite defaults here
# stage: dev
# region: us-east-1
# you can add statements to the Lambda function's IAM Role here
iamRoleStatements:
- Effect: "Allow"
Action:
- "s3:*"
Resource: '*'
# you can add packaging information here
#package:
# exclude:
# - exclude-me.js
# artifact: my-service-code.zip
functions:
getComment:
handler: handler.getComment
# The following are a few example events you can configure
# NOTE: Please make sure to change your handler code to work with those events
# Check the event documentation for details
events:
- http:
path: comments/{id}
method: get
integration: lambda
request:
parameters:
querystrings:
id: true
response:
headers:
Content-Type: integration.response.header.Content-Type
Content-Disposition: integration.response.header.Content-Disposition
# - s3: ${env:BUCKET}
# - schedule: rate(10 minutes)
# - sns: greeter-topic
# - stream: arn:aws:dynamodb:region:XXXXXX:table/foo/stream/1970-01-01T00:00:00.000
commentParser:
handler: handler.commentParser
# The following are a few example events you can configure
# NOTE: Please make sure to change your handler code to work with those events
# Check the event documentation for details
events:
- s3:
bucket: aws-lambdaserverless-comment-inbox
event: s3:ObjectCreated:*
rules:
- prefix: comments-
- suffix: .json
# you can add CloudFormation resource templates here
resources:
Resources:
NewResource:
Type: AWS::S3::Bucket
Properties:
BucketName: aws-lambdaserverless-bl-created
# Outputs:
# NewOutput:
# Description: "Description for the output"
# Value: "Some output value"