Fastly
Visualize Fastly data, map Fastly users to employees, and monitor changes through queries and alerts.
- Installation guide
- Fastly data model
Installation
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.
Configuration in Fastly
Configuration 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
tag.AccountName
when theAccountName
toggle 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
DISABLED
and manually execute the integration.Your Fastly Customer ID and API Token.
Click Create once all values are provided to finalize the integration.
Next steps
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.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
API Token | fastly_api_token | AccessKey |
Account | fastly_account | Account |
Service | fastly_service | Service |
Service Backend | fastly_service_backend | ApplicationEndpoint |
User | fastly_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
fastly_account | HAS | fastly_api_token |
fastly_account | HAS | fastly_service |
fastly_account | HAS | fastly_user |
fastly_service | HAS | fastly_service_backend |
fastly_user | HAS | fastly_api_token |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
fastly_service | CONNECTS | *DomainRecord* | FORWARD |
fastly_service_backend | CONNECTS | *Host or Gateway* | FORWARD |