SEDA
A Python toolkit to build Serverless Event-Driven Applications on AWS.
Documentation: https://seda.domake.io (pending)
Examples: /templates
What
- Allows to schedule periodic and one-time tasks on EventBridge Scheduler.
- Simplifies creating, executing, and managing asynchronous task using SNS messages and Lambda events.
- Includes
@decoratorsin addition to@app.decoratorsfor reusable apps. - Works well with any framework, interface, toolkit... see /templates.
- Provides Serverless framework support via plugin.
- Other event sources, e.g. CloudWatch, Kinesis, Dynamodb, SQS, S3...
- Easy to read documentation and tests.
- SAM templates and CDK support.
Installation
pip install seda
Example
main.py:
from datetime import datetime
from seda import Seda
seda = Seda()
@seda.schedule("cron(* * * * ? *)", args=("minutes",))
async def myschedule(timespec: str = "auto") -> None:
seda.log.info(f"myschedule: {datetime.now().isoformat(timespec=timespec)}")
@seda.task
async def mytask(timespec: str = "auto") -> None:
seda.log.info(f"mytask: {datetime.now().isoformat(timespec=timespec)}")
main.seda is an AWS Lambda handler in charge of managing the creation and execution of our tasks.
@schedule: creates a new periodic "schedule" on EventBridge at deployment time.@task: creates one-time asynchronous tasks at runtime:- SNS messages: default
- Lambda events:
@task(service="lambda") - EventBridge one-time schedules:
mytask.at("...")
For reusable apps use @task and @schedule decorators that always points to the currently active Seda instance:
tasks.py:
from datetime import datetime
from seda import task
@task
async def mytask(timespec: str = "auto") -> str:
return datetime.now().isoformat(timespec=timespec)
Tasks
await mytask()
- SNS: This task is executed asynchronously by sending a message to a previously subscribed SNS topic.
- λ: A second option is to directly invoke the Lambda function
InvocationType=Eventby adding the "service" option to the task decorator@task(service="lambda"). - test: For local and test environments the task is executed synchronously by default.
One-time schedules
from datetime import datetime, timedelta
mytask.at(datetime.now() + timedelta(minutes=5))
The .at(datetime) method is equivalent to @schedule("at(datetime)").
These one-time schedules are created under a second EventBridge Schedule Group (group 1 - N schedules) so after a new deployment we can clean the group of periodic schedules but keeping our one-time schedules.
@schedule
| SEDA / AWS | TYPE | EXAMPLE |
|---|---|---|
| expression ScheduleExpression |
str |
- "rate(5 minutes)"- "cron(*/5 * * * ? *)"- "at(2025-10-26T12:00:00)" |
| args - |
Optional[Sequence] |
("a", "b") |
| kwargs - |
Optional[Dict] |
{"a": "b"} |
| timezone ScheduleExpressionTimezone |
Optional[str] |
"Asia/Saigon" |
| time_window FlexibleTimeWindow |
Optional[ScheduleTimeWindow] |
{"Mode": "FLEXIBLE", "MaximumWindowInMinutes": 15} |
| retry_policy RetryPolicy |
Optional[ScheduleRetryPolicy] |
{"MaximumEventAgeInSeconds": 60, "MaximumRetryAttempts": 10} |
| start_date StartDate |
Optional[datetime] |
datetime.now() + timedelta(minutes=5) |
| end_date EndDate |
Optional[datetime] |
datetime.now() + timedelta(days=5) |
| dead_letter_arn DeadLetterConfig.Arn |
Optional[str] |
"arn:aws:sqs:..." |
| kms_key KmsKeyArn |
Optional[str] |
"arn:aws:kms:..." |
CLI
SEDA CLI provides a list of commands to deploy, remove and debug SEDA resources on an existing Lambda function:
seda deploy --app main.seda -f myfunction
Deploy @schedule, @task:
- Creates the Schedule Groups for periodic and one-time tasks
- Creates N periodic schedules
- Creates SNS topic and a Lambda subscription to this topic
- Adds related IAM roles and policies
A second deployment removes the periodic task Schedule Group and creates a new one adding the new schedules.
We can also remove the deployed stack:
seda remove --app main.seda -f myfunction
Remote Function Invocation
Invoke Python interpreter:
seda python 'import sys;print(sys.version)' -f myfunction
Run shell commands:
seda shell env -f myfunction
Serverless Framework
The plugin serverless-seda adds all SEDA CLI commands to Serverless framework CLI:
sls seda deploy
ASGI
SEDA seamlessly integrates with ASGI applications by adding Mangum handler to seda[asgi].
pip install seda[asgi]
main.py:
from fastapi import FastAPI
from seda import Seda
app = FastAPI()
seda = Seda(app)
Default handler
Add any callable as a handler to process any non-SEDA events:
def myhandler(event, context):
pass
seda = Seda(default_handler=myhandler)
Metadata
Release files for seda 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| seda-0.0.6.tar.gz | 17.4 kB | Without provenance | Details for seda-0.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seda-0.0.6-py3-none-any.whl | Python 3 | none | any | Details for seda-0.0.6-py3-none-any.whl |
Total release size: 40.6 kB
Release files / seda-0.0.6.tar.gz
| Download URL | seda-0.0.6.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5046d4145491f8f677b6368864beb914e28cd1bb18ce9dfe3f70a1c2d32509d0
|
|
BLAKE2b-256 checksum How to use checksums |
d989fb9453942300b91dd167999a86d2b808205c32e015805c04c0a5c062a8a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.23.1
|
Release files / seda-0.0.6-py3-none-any.whl
| Download URL | seda-0.0.6-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b3799f151dd2dc5e7419fca6491160bbd6db04779cc3a7df704a597b99b00c3
|
|
BLAKE2b-256 checksum How to use checksums |
50dae45b09cc912defdded713b097d31c131a249024781d37c13d15324fbdc21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.23.1
|
Security for seda 0.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.