Akamai
Overview
Firefly integrates with Akamai to pull in information like configurations, properties, and edge hostnames as "assets". This means in your Firefly Inventory, you'll see Akamai resources listed (with their configurations) just like cloud assets. You can then enforce IaC or policies on them as well (for example, ensuring all Akamai properties follow a naming convention).
Prerequisites
An Akamai API client with appropriate credentials (Client token, Client secret, Access token)
Ensure the API client has read permissions on Akamai resources
Access to Akamai Control Center to create API clients
Setup Procedure
In Firefly, select Add New > Akamai
In Akamai Control Center, create a new API client with read permissions
Copy the credentials into Firefly's integration form
Select your Akamai region, and select Next
Creating API Credentials
Navigate to Akamai Control Center
Go to Identity & Access Management section
Create a new API client with read-only permissions
Save the client token, client secret, and access token
Configuration Details
Firefly scans every 8 hours by default for SaaS data
Your Akamai configurations list will stay updated automatically
You can enforce IaC or policies on your Akamai assets
Supports monitoring of Akamai properties, configurations, and edge hostnames
Best Practices
Use dedicated API clients for Firefly integration
Regularly rotate API credentials for security
Monitor API client usage in Akamai
Keep track of which Akamai assets are being monitored
Review and update policies as needed
Troubleshooting
For API credential issues:
Verify API client permissions
Check if the credentials have expired
Ensure the client has the correct access level
For asset discovery issues:
Verify the integration is active in Firefly
Check if the API client has access to the required resources
Review Firefly integration logs
For policy enforcement issues:
Verify the asset types are supported
Check policy configuration
Review Firefly policy logs
Last updated
Was this helpful?