Visualize Fastly data, map Fastly users to employees, and monitor changes through queries and alerts.
- Installation guide
- Fastly data model
You will need to create an API Token key on Fastly for this integration. See their documentation for more information.
The API token should be generated by a superuser so it is associated with the organization, not the user, with global read permissions.
Finalize in JupiterOne
To install the Fastly integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Fastly. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Fastly account in JupiterOne. Ingested entities will have this value stored in
AccountNametoggle is enabled.
Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration.
Your Fastly Customer ID and API Token.
Click Create once all values are provided to finalize the integration.
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
The following entities are created:
|Resources||Entity ||Entity |
The following relationships are created:
|Source Entity ||Relationship ||Target Entity |