Skip to main content

Quickstart Guide

Get SmartSRE scanning your GCP environment in under 5 minutes.

Prerequisites​

  • A Google Cloud Platform account with at least one project
  • Owner or Editor role on the GCP project you want to connect
  • Access to Google Cloud Shell (recommended) or gcloud CLI

Step 1: Sign Up​

  1. Navigate to smartsre.smartmigrate.ai
  2. Click Get Started and sign in with your Google account
  3. Complete the tenant setup wizard

Step 2: Connect Your GCP Project​

After signup, SmartSRE guides you through connecting your first GCP project:

  1. Generate Connection Script — SmartSRE creates a customized shell script
  2. Run in Cloud Shell — Copy the script and execute it in Google Cloud Shell
  3. Verify Connection — SmartSRE confirms the service account is configured

The script performs these actions in your GCP project:

  • Enables required GCP APIs
  • Creates a dedicated service account (smartsre-agent@...)
  • Grants minimal IAM roles for scanning
  • Configures impersonation for secure, keyless access
No Keys Required

SmartSRE uses service account impersonation—no JSON keys are downloaded or stored.

Step 3: Run Your First Scan​

  1. From the Dashboard, click Run Scan
  2. Select a service (e.g., BigQuery or Cloud Run)
  3. Choose your connected project and scope
  4. Click Start Scan

The scan typically completes in 30-60 seconds, depending on resource count.

Step 4: Review Findings​

Once the scan completes:

  1. Navigate to the Run Details page
  2. Review the Findings tab for detected issues
  3. Each finding shows:
    • Severity (Info, Low, Medium, High, Critical)
    • Issue Type (e.g., high_memory_usage, public_bucket)
    • Resource affected
    • Recommended Actions

Step 5: Apply a Fix (Optional)​

If SmartSRE recommends automated fixes:

  1. Click Fix on an individual finding, or Fix All for bulk remediation
  2. Review the proposed ChangeSet (list of operations)
  3. If approval is required, an approver will be notified
  4. Once approved, SmartSRE applies the changes

All executions create rollback checkpoints for safe recovery.

What's Next?​