Connecting Additional Integrations

After onboarding, you can add or manage integrations at any time via Settings > Integrations in the Firefly platform. To add a new integration, go to the Integrations page, click "Add New", and select the type of tool or service you wish to connect from the categorized options.

Firefly supports several categories of integrations, allowing you to expand its capabilities and tailor it to your specific operational needs.

Types of Integrations You Can Add

You can connect various tools and services to Firefly to enhance its functionality. These fall into the following categories:

Data Sources (Cloud Providers & SaaS)

• Purpose: To allow Firefly to scan and inventory your assets from cloud environments (like AWS, Azure, GCP, Kubernetes) and other SaaS services (e.g., Datadog, Okta). This enables comprehensive visibility into your cloud footprint.

• General Process: Involves granting Firefly read-only access via secure mechanisms like IAM roles, service accounts, or API keys, following guided setup wizards within Firefly.

• Learn more: See the Data Source Integrations section for detailed guides.

Workflows (CI/CD Pipelines)

• Purpose: To integrate Firefly into your existing CI/CD pipelines (e.g., Jenkins, GitLab CI, GitHub Actions). This allows Firefly to scan Infrastructure-as-Code (IaC) deployments (like Terraform, OpenTofu) and enforce predefined guardrails before changes are applied.

• General Process: Involves adding Firefly analysis steps to your pipeline definitions.

• Learn more: Refer to the Workflows Integration documentation.

Version Control Systems (VCS)

• Purpose: To link your Git repositories (e.g., GitHub, GitLab, Bitbucket) with Firefly. This enables Firefly to map cloud resources back to their IaC definitions, understand code context, and potentially open pull requests for automated IaC generation or remediation.

• General Process: Requires authorizing Firefly to access your repositories, via dedicated application or personal access tokens with appropriate permissions.

• Learn more: Find details in the VCS Integrations section.

Notification Channels (ChatOps)

• Purpose: To send real-time alerts and notifications about important events detected by Firefly (such as configuration drift, policy violations, or new unmanaged resources) directly to your team's communication platforms.

• General Process: Involves configuring connections to services like Slack, Microsoft Teams, PagerDuty, or email. This includes setting up webhooks or authorizing Firefly applications within your chosen chat or alerting tools.

• Learn more: Consult the ChatOps Integrations guide.

Project Management Tools

• Purpose: To integrate Firefly with your project management tools (e.g., Jira). This allows you to on-demand create tickets for cloud issues.

• General Process: Requires creating a token and configuring the integration in Firefly.

• Learn more: Refer to the Project Management Tools Integration documentation.

IaC Remote Backends

• Purpose: To integrate Firefly with your IaC remote backends (e.g., Terraform Cloud, Terraform Enterprise). This allows Firefly to scan your IaC state files.

• General Process: Requires creating a token and configuring the integration in Firefly.

• Learn more: Refer to the IaC Remote Backends Integration documentation.

General Steps to Add an Integration

Regardless of the integration type, the process generally follows these steps within the Firefly UI:

1. Navigate to Settings > Integrations.

2. Click the "Add New" button. This will present a list or categorized view of available integrations.

3. Select the specific cloud provider, service, or tool you wish to integrate.

4. Follow the on-screen instructions and guided procedures provided by Firefly. Each integration will have a specific set of steps, which may involve providing credentials, authorizing access, or configuring endpoints. Firefly's documentation provides detailed walkthroughs for each supported integration.

Once an integration is successfully configured, Firefly will begin to utilize it according to its purpose. For example:

• Data Sources: Firefly will start scanning for assets and ingesting metadata.

• Workflows: Firefly will be ready to analyze pipeline runs.

• VCS: Firefly will link code to resources and enable IaC-related features.

• Notification Channels: Firefly will be able to send alerts to the configured channels.

• Project Management Tools: Firefly will be able to create tickets for cloud issues.

• IaC Remote Backends: Firefly will be able to scan your IaC state files.

You can manage (edit, disable, or delete) existing integrations from the same Settings > Integrations page.