-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathserverless.yml.example
More file actions
55 lines (46 loc) · 1.71 KB
/
Copy pathserverless.yml.example
File metadata and controls
55 lines (46 loc) · 1.71 KB
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
# Minimal serverless.yml template for a service running under LSS.
# Complete, runnable versions live under examples/ — e.g.
# examples/localstack-ultimate/serverless.yml (single service) or any
# examples/localstack-free/*-service/serverless.yml (multi-service).
service: example-service
frameworkVersion: '3'
provider:
name: aws
runtime: nodejs20.x
region: us-east-1
functions:
hello:
handler: src/handlers/hello.handler
events:
- http:
path: hello
method: get
plugins:
- serverless-lss # auto-registers this service with the LSS orchestrator
- serverless-offline # optional: only if you also run functions via offline
custom:
# serverless-lss plugin — where the orchestrator is listening.
# Must match `serverPort` in lss.config.json (default 3100).
orchestrator:
enabled: true
orchestratorUrl: http://localhost:3100
# Ports LSS uses for this service. `custom.lss` wins; if you already have a
# serverless-offline block, its httpPort/lambdaPort are picked up as a
# drop-in fallback (httpPort → apiPort, lambdaPort → invokePort).
lss:
apiPort: 3000 # HTTP API (API Gateway emulation)
invokePort: 3001 # direct Lambda invocations
# Infrastructure resources are provisioned on registration. Supported types:
# DynamoDB tables, SQS queues, SNS topics, S3 buckets (incl. notifications),
# EventBridge buses/rules, Lambda event source mappings and OpenSearch
# Serverless collections. Example:
#
# resources:
# Resources:
# SearchCollection:
# Type: AWS::OpenSearchServerless::Collection
# Properties:
# Name: example-search # served at <engine>/_aoss/example-search
# Type: SEARCH
package:
individually: false