Integrations / AWS EventBridge + Lambda
AWS EventBridge + Lambda
Not yet — needs role-based access, coming with a deliberate design.
Why connect it
EventBridge schedules and Lambda invocations are the enterprise loops. Reading them needs an IAM role you grant, not a pasted token; that design is worth doing carefully rather than quickly.
What you'll see
- Planned: every rule and scheduler schedule with target, invocations, errors, and duration from CloudWatch
What the credential can and cannot do
Where to get it: —
It grants: Nothing is connected.
It cannot: —
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.