Package Exports
- cdk-scheduler
- cdk-scheduler/build/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (cdk-scheduler) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
cdk-scheduler
A CDK construct to schedule events precisely ⏱
This construct enables to trigger an event at a given time on a serverless architecture.
You should use cdk-scheduler if you need to trigger an event at a precise time (down to the second) on your AWS application.
Install
To install with npm:
npm install cdk-schedulerTo install with yarn:
yarn add cdk-schedulerUsage
Understand how the Scheduler works
cdk-scheduler is powered by SQS feature to delay events up to 15 minutes.
A lambda is scheduled to query a DynamoDB Table every 15 minutes, it pushes every events scheduled in the next 15 minutes to SQS with a delay corresponding the desired publication date.
Import and initialize Scheduler
Import the scheduler with :
import { Scheduler } from 'cdk-scheduler';Then instantiate the scheduler :
const myScheduler = new Scheduler(app, id);app: Your CDK app (aConstruct)id: The id/name of the scheduler (astring)
Write messages to the scheduler
Grant access to write a new message to the scheduler to the service(s) that will write to it. For example an API Integration or a lambda function :
myScheduler.schedulerTable.grantWriteData(newMessageLambda);Messages can be posted to the scheduler by inserting a new row into the myScheduler.schedulerTable dynamoDB table. Parameters needed are:
- The name of the table to insert to :
myScheduler.schedulerTable.tableName - The partition key to use in this table :
myScheduler.partitionKeyValue - The sort key to use must be like "
[timestamp]#[id]"- For example : "
1653052252606#some-random-id" to schedule the event the2022-05-20at13:10 UTC)
- For example : "
- The payload must be a mapping with any content
An example to create a new message from a lambda (with the appropriate values passed in the environment of the lambda) :
const dynamo = new DynamoDB({
region: process.env.SCHEDULER_REGION,
});
dynamo.putItem({
TableName: process.env.SCHEDULER_TABLE_NAME,
Item: foo, //See last part for the payload format
});Consume messages from the scheduler
The events can be consumed from the SQS Queue accessible at myScheduler.schedulingQueue.
An example to trigger some lambda integration from the SQS :
const eventSource = new SqsEventSource(myScheduler.schedulingQueue);
triggeredEventHandler.addEventSource(eventSource);Overview of the architecture

Payload format
For the scheduler to function properly the elements added to DynamoDB must have the following attributes:
| Attribute | Type | Description |
|---|---|---|
pk |
string | The primary key is always the same. Its value is the attribute partitionKey available in the construct instance |
sk |
string | The secondary key should start with the timestamp at which you wish to publish the event. You can concatenate with a unique id to be sure you do not have duplicates if you separate them with a #. For instance: ✅ 1649434680000#d66727f2-9df7-41b7-b2f8-211eb5581640 is a correct secondary key. ❌ 20220422-16:47:00:00Z00#66727f2-9df7-41b7-b2f8-211eb5581640 will never be read. |
payload |
map | This is an object, without format contraints. This payload will be sent in the event once it's published. Use this to detail the action you want to execute a the scheduled time |