Firefly Documentation Portal
  • Welcome to the Documentation Portal
  • Contacting Firefly support
  • User Guides
    • QuickStart Guide
      • Onboarding
      • Dashboard
      • FAQ
      • Glossary
        • IaC status
    • Exploring the Inventory
    • Compose: Generating new configuration
    • Navigating the IaC Explorer
    • Workflows
      • Guardrails
    • Integrations
      • Integrate your providers and tools
        • Integrate your data sources
          • Integrate PagerDuty
          • Integrate MongoDB Atlas
          • Integrate AWS
            • Integrate AWS using Terraform
            • Integrate AWS using CloudFormation
            • Upgrading AWS integration to event-driven
            • AWS Discovery Status
          • Integrate Google Cloud
            • Integrate Google Cloud using a service account key
            • Integrate Google Cloud using Terraform
            • Google Cloud Discovery Status
          • Integrate Kubernetes
          • Integrate Datadog
          • Integrate New Relic
          • Integrate Okta
          • Integrate GitHub service
          • Integrate Cloudflare
          • Integrate NS1
          • Integrate Microsoft Azure
            • Integrate Microsoft Azure using Terraform
            • Azure Discovery Status
          • Integrate HashiCorp Vault
        • Integrate your IaC remote states
          • Integrate Terraform Cloud
          • Integrate Terraform Enterprise
          • Integrate HashiCorp Consul
          • Integrate remote stacks in Google Cloud Storage
          • Integrate env0
        • Integrate your version control system
          • Integrate GitHub
          • Integrate GitLab
          • Integrate Bitbucket
            • Integrate Bitbucket Data Center
            • Integrate Bitbucket Cloud
          • Integrate AWS CodeCommit
          • Integrate Azure DevOps
        • Send Firefly notifications to your messaging tools
          • Send Firefly notifications to Slack
            • Send notifications to Slack using the Slack App
            • Sending notifications to Slack using a webhook
          • Send Firefly notifications to Microsoft Teams
          • Send Firefly notifications to Torq
          • Send Firefly notifications to webhooks
          • Send Firefly notifications to Opsgenie
          • Send Firefly notifications to PagerDuty
            • Integration Key
            • General Access REST API Key
          • Send Firefly notifications to Google Chat
        • Integrate project management tools
          • Integrate Jira
    • Governance
    • Event-Center
    • How-to Guides
      • Manage assets
        • Codify assets
          • Codify assets to Config Connector
          • Codify assets to Manifest
          • Codify assets to Helm
          • Codify assets to CDK8S
          • Codify assets to Terraform
          • Codify assets to Pulumi
          • Codify assets to CloudFormation
          • Codify assets to CDK
          • Codify assets to Crossplane
          • Codify assets to Ansible
        • Delete unmanaged assets
        • Fix drifts
        • Remove asset Terraform code
        • Excluded drifts
        • IaC-Ignored assets
      • Monitor events
      • Manage notifications
      • Manage user roles
    • Deep Dive articles
      • Disaster recovery
      • Drifts
      • Codification
      • Notifications
      • Governance
      • Event-driven
      • IaC-Ignored assets
  • Appendix
    • Migrating CloudFormation resources to Terraform
    • Terraform Cloud Run Tasks
    • Creating a key pair
    • SSO Configuration
    • Firefly API Documentation
    • Support Matrix
    • Data privacy and AI usage
  • Firefly MCP
  • Firefly Backstage Plugin
Powered by GitBook
On this page
  • Event-driven integration
  • Event-driven backends in the IaC Explorer

Was this helpful?

  1. User Guides
  2. Deep Dive articles

Event-driven

The advantages of using event-driven architecture for AWS and GCP integrations.

PreviousGovernanceNextIaC-Ignored assets

Last updated 9 months ago

Was this helpful?

The term event-driven refers to a software architecture in which an application or system responds to specific events or actions generated by a user, another application, or a system. In an event-driven architecture, the application or system does not perform a task until it receives an event or action that triggers it to do so.

Event-driven applications are designed to respond to events in real-time, making them highly responsive to changes in the environment. In this architecture, events are the primary communication mechanism between the various components of the system.

When an event is triggered, the application or system can take immediate action, such as sending a notification, updating a database, or invoking a function. By using event-driven architectures, developers can build applications that are more user-friendly, responsive, and scalable.

Event-driven integration

Using event-driven integration allows Firefly to fetch your assets in near real-time continuously. Firefly integrates with CloudTrail for AWS and uses audit logs from Google Cloud to refresh the assets in the Inventory as soon as they change. Without it, the Inventory takes up to eight hours to update.

To use the event-driven service, you must enable CloudTrail in your AWS account, which is available with Terraform and CloudFormation. For Google Cloud, enable logging API.

S3 Event Notifications of TF State Files

When you enable S3 event notifications for Terraform state files, Firefly can monitor updates to your IaC stacks stored in S3 buckets and optimize the IaC status in the system. This will provide near real-time updates from your TF state files.

Event-driven backends in the IaC Explorer

The in Firefly employs event-driven backends. Once Firefly scans your IaC stacks, it finds as soon as any updates are made to your cloud infrastructure, significantly reducing the time required to view changes in your IaC status.

IaC Explorer
Event-driven backends