Amazon EventBridge Scheduler

Connect

Activate your license key and start the emulator with the Vera launcher, as in Activate Pro, then run this in a terminal of its own, from an empty scratch directory. It gives the official AWS CLI dummy credentials and a config file of its own, so no AWS account is needed and your own AWS profile isn't touched.

export VERA_ENDPOINT="http://localhost:5003"
export AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test
export AWS_REGION=us-east-1 AWS_DEFAULT_REGION=us-east-1
export AWS_SHARED_CREDENTIALS_FILE=/dev/null
export AWS_EC2_METADATA_DISABLED=true
export AWS_PAGER="" AWS_CLI_AUTO_PROMPT=off
unset AWS_PROFILE AWS_DEFAULT_PROFILE
unset AWS_SESSION_TOKEN AWS_SECURITY_TOKEN
unset AWS_WEB_IDENTITY_TOKEN_FILE AWS_ROLE_ARN AWS_ROLE_SESSION_NAME
unset AWS_CONTAINER_CREDENTIALS_FULL_URI
unset AWS_CONTAINER_CREDENTIALS_RELATIVE_URI
cat > vera-aws-config <<'EOF'
[default]
region = us-east-1
output = json
cli_binary_format = base64
s3 =
    addressing_style = path
EOF
export AWS_CONFIG_FILE="$PWD/vera-aws-config"

When you've finished every example in this terminal, close it and delete vera-aws-config, not before.

Use the AWS CLI’s scheduler commands. The emulator serves the 2021-06-30 API over the REST JSON protocol.

A schedule needs a target and the ARN of an existing IAM role, and a role that doesn’t exist is rejected. In Vera 1.2.2, schedule metadata worked with a freshly created role, but delivery to a target wasn’t observed (see Limitations). The example below works with a schedule group, which needs no role or target.

Example

Create a schedule group and read it back. create-schedule-group returns the group’s ScheduleGroupArn.

aws --endpoint-url "$VERA_ENDPOINT" scheduler create-schedule-group --name vera-docs-group
aws --endpoint-url "$VERA_ENDPOINT" scheduler get-schedule-group --name vera-docs-group

get-schedule-group returns the group, ACTIVE, with its creation and modification times, which differ on every run. These are selected fields:

Output (selected fields)

{
    "Arn": "arn:aws:scheduler:us-east-1:123456789012:schedule-group/vera-docs-group",
    "Name": "vera-docs-group",
    "State": "ACTIVE"
}

A schedule group is a container for schedules: this example invokes no target. To clean up, delete the group. It prints nothing, and leaves no schedule or group behind.

aws --endpoint-url "$VERA_ENDPOINT" scheduler delete-schedule-group --name vera-docs-group

Supported features

• Schedule groups, created, read back and deleted.
• Schedule records. In Vera 1.2.2, schedule metadata worked with a freshly created IAM role. In a diagnostic run on Vera 1.2.0 preview, where a role record already existed, a schedule with an at(...) expression and a local SQS target was created, read back and deleted. A record isn’t proof that the schedule fires: see Limitations.
• Role checks: a schedule naming a role that doesn’t exist was rejected with ValidationException. That’s a check that the role exists, not a check of what the role allows.
• Also served, not checked in Vera 1.2.0 preview or Vera 1.2.0-rc.3: updating and listing schedules, listing schedule groups, and tags.

Limitations

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

• No scheduled delivery was observed. Delivery still wasn’t observed in Vera 1.2.2. In Vera 1.2.0 preview, a diagnostic one-time schedule was set five seconds ahead, but no target message was received after twelve seconds. Scheduling accuracy and background firing have not been established.
• Not yet verified: cron expressions, time zones, flexible time windows, retries, dead-letter queues and deleting a schedule after it completes.

API coverage

Every operation in AWS's published 2021-06-30 API (SDK model, botocore 1.43.105), and whether the emulator implements it. Availability combines the earlier implementation inventory with the dated observations below; checking a page's example does not verify every operation. Each note names its evidence first; an observation given without a build or date comes from earlier testing, on 3 November 2026. What the statuses mean

Operation	Status	Notes
CreateSchedule	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — schedule metadata worked with a freshly created IAM role; delivery to a target wasn't observed. Local observation: Vera 1.2.0 preview, 5 November 2026 — In a diagnostic run that reused an existing role record, created a schedule with an at(...) expression and a local SQS target. A role that doesn't exist was rejected with ValidationException. Creating a schedule isn't proof it fires: a one-time schedule set five seconds ahead delivered no message within twelve seconds.
CreateScheduleGroup	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — Created the example's group and returned its ScheduleGroupArn.
DeleteSchedule	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — Deleted the diagnostic schedule, which reused an existing role record.
DeleteScheduleGroup	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — Deleted the example's group, printing nothing.
GetSchedule	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — Read back the diagnostic schedule, which reused an existing role record.
GetScheduleGroup	Implemented	Local observation: Vera 1.2.0 preview, 5 November 2026 — Returned the group's ARN, name, ACTIVE state and timestamps.
ListScheduleGroups	Implemented
ListSchedules	Implemented
ListTagsForResource	Implemented
TagResource	Implemented
UntagResource	Implemented
UpdateSchedule	Implemented