-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathserverless.yml
209 lines (197 loc) · 5.58 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
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
# 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: stealth-project # NOTE: update this with your service name
plugins:
- serverless-webpack
- serverless-domain-manager
custom:
webpack:
webpackConfig: 'webpack.config.js' # Name of webpack configuration file
includeModules: true # Node modules configuration for packaging
packager: 'npm' # Packager that will be used to package your external modules
customDomain:
domainName: 'vmchanger.abashina.org'
basePath: ''
stage: ${self:provider.stage}
createRoute53Record: true
# 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: nodejs8.10
memorySize: 128
timeout: 60 # The default is 6
# 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: # Gives permission to our DynamoDB table.
- dynamodb:DeleteItem
- dynamodb:GetItem
- dynamodb:PutItem
- dynamodb:Query
- dynamodb:Scan
- dynamodb:UpdateItem
Resource:
- "arn:aws:dynamodb:*:*:table/voiceMailChangerTable"
- "arn:aws:dynamodb:*:*:table/voicemailChangerUsers"
- Effect: Allow
Action: # Gives permission to generate audio.
- polly:SynthesizeSpeech
Resource: "*"
- Effect: Allow
Action: # Gives access to our s3 bucket.
- s3:GetObject
- s3:PutObject
- s3:PutObjectAcl
Resource:
- "arn:aws:s3:::voicemail-changer-bucket-mp3"
- "arn:aws:s3:::voicemail-changer-bucket-mp3/*"
- Effect: Allow
Action: # Gives permission to publish messages.
- SNS:Publish
Resource: "*"
# you can define service wide environment variables here
# environment:
# variable1: value1
# you can add packaging information here
#package:
# include:
# - include-me.js
# - include-me-dir/**
# exclude:
# - exclude-me.js
# - exclude-me-dir/**
functions:
call:
handler: src/handlers/call.call
events:
- http:
path: call
method: post
integration: lambda
response:
headers:
Content-Type: "'application/xml'"
template: $input.path("$.body.message")
changer:
handler: src/handlers/changer.changer
events:
- http:
path: changer
method: post
integration: lambda
response:
headers:
Content-Type: "'application/xml'"
template: $input.path("$.body.message")
submit:
handler: src/handlers/submit.submit
events:
- http:
path: submit
method: post
signup:
handler: src/handlers/signup.signup
events:
- http:
path: signup
method: post
login:
handler: src/handlers/login.login
events:
- http:
path: login
method: post
info:
handler: src/handlers/info.info
events:
- http:
path: info
method: post
generate:
handler: src/handlers/generate.generate
events:
- stream:
type: dynamodb
batchSize: 1
enabled: true
arn:
Fn::GetAtt:
- voiceMailChangerTable
- StreamArn
# 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: users/create
# method: get
# - 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
# - alexaSkill
# - iot:
# sql: "SELECT * FROM 'some_topic'"
# - cloudwatchEvent:
# event:
# source:
# - "aws.ec2"
# detail-type:
# - "EC2 Instance State-change Notification"
# detail:
# state:
# - pending
# - cloudwatchLog: '/aws/lambda/hello'
# Define function environment variables here
# environment:
# variable2: value2
# you can add CloudFormation resource templates here
resources:
Resources:
voiceMailChangerTable:
Type: AWS::DynamoDB::Table
Properties:
TableName: voiceMailChangerTable
AttributeDefinitions:
- AttributeName: id
AttributeType: S
KeySchema:
- AttributeName: id
KeyType: HASH
ProvisionedThroughput:
ReadCapacityUnits: 1
WriteCapacityUnits: 1
StreamSpecification:
StreamViewType: NEW_IMAGE
voicemailChangerUsers:
Type: AWS::DynamoDB::Table
Properties:
TableName: voicemailChangerUsers
AttributeDefinitions:
- AttributeName: phone
AttributeType: S
KeySchema:
- AttributeName: phone
KeyType: HASH
ProvisionedThroughput:
ReadCapacityUnits: 1
WriteCapacityUnits: 1
S3BucketMP3:
Type: AWS::S3::Bucket
Properties:
BucketName: voicemail-changer-bucket-mp3