Render
Overview
Section titled “Overview”The Render integration connects a Render workspace to Oneleet, syncing workspace members as user account assets and your services, Postgres instances, Key Value instances, and workspace as assets. This lets Oneleet monitor who has access to your workspace and how its services and datastores are configured.
What does Oneleet monitor?
Section titled “What does Oneleet monitor?”- Render workspace members (user accounts), including each member’s role and whether they have multi-factor authentication enabled
- Postgres instances, including whether they’re publicly accessible, highly available, backed up, and running a supported version
- Key Value instances, including whether they’re publicly accessible
- Services, including whether auto-deploy is turned on
- Your workspace, including whether audit logs are available and a log stream is configured
To set up the Render integration, navigate to Integrations > Add integration > Render.
Oneleet connects with a Render scoped API key, which can only reach the workspace you create it for. Use a user who has the Admin role in that workspace, because Render only lets you grant a key the permissions your own role has.
- In the Render Dashboard, open your Account Settings page and click Create API key.
- Enter a descriptive name and select the workspace you want to monitor.
- Set each of the required permissions to Read, and leave every other permission off.
- Click Generate API key and copy the key. Render shows it only once.
- In Oneleet, paste the key into the API Key field, enter the ID of the same workspace (it starts with
tea-) in the Workspace ID field, and click Connect.
When the key is deleted in Render, Oneleet disconnects until you update the key in Oneleet.
Required permissions
Section titled “Required permissions”Render groups a key’s permissions into sections. Oneleet only reads from Render, so it needs one permission in each of these sections, set to Read.
| Section | Permission | Access | What Oneleet reads |
|---|---|---|---|
| Services | Web and private services, static sites, background workers, and cron jobs | Read | Services and their auto-deploy setting |
| Postgres | Postgres instances | Read | Postgres instances, their configuration, and their recovery status |
| Key Value | Key Value instances | Read | Key Value instances and their configuration |
| Workspaces | Members, notifications, webhooks, and log and metric streams | Read | The workspace’s name, members, and log stream settings |
| Audit Logs | Read workspace audit logs | Read | Whether audit logs are available for the workspace |
When the key is missing one of these permissions, Oneleet can’t read that resource and its sync fails, so the monitors that depend on it stop updating. To fix it, edit the key’s permissions in Render.
Classic API keys
Section titled “Classic API keys”Render is still rolling out scoped API keys. If you can’t choose permissions when you create a key, create a classic key and use it the same way.
A classic key has the same permissions as the user who created it, in every workspace that user belongs to. Connections that already use a classic key keep working. To switch one to a scoped key, create the scoped key in Render and update the key in Oneleet.