https://github.com/nullstone-modules/aws-ecs-cron-trigger
Nullstone capability to trigger an ECS/Fargate app using a cron schedule.
https://github.com/nullstone-modules/aws-ecs-cron-trigger
Last synced: 25 days ago
JSON representation
Nullstone capability to trigger an ECS/Fargate app using a cron schedule.
- Host: GitHub
- URL: https://github.com/nullstone-modules/aws-ecs-cron-trigger
- Owner: nullstone-modules
- License: mit
- Created: 2023-06-20T19:15:23.000Z (about 3 years ago)
- Default Branch: master
- Last Pushed: 2026-06-10T19:09:53.000Z (about 1 month ago)
- Last Synced: 2026-06-10T21:06:57.158Z (about 1 month ago)
- Language: HCL
- Size: 8.79 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
README
# Scheduled Trigger for ECS/Fargate
Nullstone capability to trigger an ECS/Fargate app or job on a cron schedule.
## Telling cron runs apart from manual runs
Every scheduled run starts the ECS task with two environment variables your app can read:
| Variable | Value |
|--------------------------|--------------------------------------------------------------------------------|
| `NULLSTONE_TRIGGER` | `cron` — the run was started by this schedule (not a manual `nullstone run`) |
| `NULLSTONE_TRIGGER_NAME` | the name of this cron capability — identifies *which* schedule fired the run |
These are applied as **container overrides** on the scheduled `RunTask`. A manual `nullstone run` instead sets
`NULLSTONE_TRIGGER=manual`, so your app can positively tell the two apart by the value of `NULLSTONE_TRIGGER`, and
`NULLSTONE_TRIGGER_NAME` lets you distinguish multiple schedules attached to the same app.
Example (Node.js):
```js
if (process.env.NULLSTONE_TRIGGER === "cron") {
console.log(`Started by cron schedule: ${process.env.NULLSTONE_TRIGGER_NAME}`);
} else {
console.log("Started manually");
}
```