Skip to main content

Heroku

Visualizes Heroku teams, users, applications, and services, map Heroku users to employees, and monitors changes through queries and alerts.

Installation​

To use this integration, JupiterOne requires an API key configured for read access in your Heroku account. The integration requires a Heroku Enterprise account and the read token scope. Optionally, use the global token scope to also fetch members of each Heroku team.

The Heroku account that generates the API key determines which permissions are available. For full access to all data (including application add-ons), the account must have the admin role. An account with the member role can retrieve most data, but add-on information is only accessible to admins.

info

For additional information on creating an API key on Heroku, refer to the Heroku authentication documentation.

Configuration in JupiterOne​

To install the Heroku integration in JupiterOne, navigate to the Integrations tab and select Heroku. Click New Instance to begin configuring your integration, providing the following:

  • Account Name — A label used to identify this integration instance in JupiterOne. Ingested entities will have this value stored in tag.AccountName when the AccountName toggle is enabled.

  • Description — An optional description to help distinguish this instance from others.

  • Polling Interval — How often JupiterOne should collect data from Heroku. You may leave this as DISABLED and trigger the integration manually.

  • API Key — Your Heroku API key, configured for the appropriate token scope (read for basic access; global if team member data is needed).

Click Create Configuration after all values are provided.

Next steps​

Once your integration instance is configured, it will begin running on the polling interval you selected. Continue on to our instance management guide to learn more about working with and editing integration instances.