How can we help?
Start with the guide that matches your cloud provider or the stage where you are blocked. Flare supports GCP Cloud Audit Logs and recent regional AWS CloudTrail management event history.Workspace and GitHub early access
Use the Workspace guide for customer IDs, administrator permissions and reporting delays. Use the GitHub guide for Enterprise Cloud requirements, organization ownership, GitHub App permissions, report limits and reconnecting. GitHub uses a dedicated deterministic report; Workspace uses New Analysis. Both support manual runs only; check your account’s availability in Connectors.Connect a cloud
Connect GCP
Configure read-only OAuth, find your Project ID, reconnect an expired token, or troubleshoot missing audit logs.
Connect AWS
Create the read-only IAM role, understand trust versus permissions policies, and resolve role or Region errors.
Run and investigate
Run an analysis
Fetch live GCP or AWS activity, upload a file, choose a time window, and understand event limits.
Understand results
Read scores, severity, source evidence, first-seen values, and truncation notices.
Ask follow-up questions
Get provider-specific investigation steps and turn findings into an incident summary.
Upload a file
Prepare GCP, AWS, or custom logs in JSON, NDJSON, CSV, or plain text.
Fast checks
Never send passwords, OAuth tokens, access keys, secret keys, or session credentials to Flare Support.
Still blocked?
Visit Flare Support or email [email protected]. Include:- The provider: GCP, AWS, Google Workspace, GitHub, or file upload
- The GCP Project ID, AWS account ID and Region, Workspace customer ID or GitHub organization
- The role name or connector status, when relevant
- The exact error message and the time it occurred