Skip to main content

Getting Started

Welcome to KredSLA — the automated cloud SLA credit recovery platform. This guide will walk you through setting up your account, connecting your cloud environments, and recovering your first SLA credits.

What Is KredSLA?​

KredSLA monitors your cloud infrastructure across AWS, Azure, GCP, and OCI for Service Level Agreement (SLA) violations and automatically recovers the credits you're owed. No manual monitoring, no spreadsheet tracking, no missed filing deadlines.

How it works:

  1. Connect your cloud accounts with read-only credentials
  2. KredSLA continuously monitors for SLA breaches
  3. Evidence is automatically assembled and claims are filed
  4. Credits are recovered and tracked in your dashboard

Step 1: Create Your Account​

KredSLA supports enterprise single sign-on through:

  • Google Workspace — Click "Continue with Google Workspace"
  • Microsoft Entra ID (Azure AD) — Click "Continue with Microsoft 365"
  • Okta — OIDC or SAML
  • JumpCloud — OIDC or SAML

SSO is the fastest path — your organization is created automatically from your identity provider.

Sign Up with Email​

  1. Click Create Account on the login page
  2. Enter your email, organization name, and a password
    • Password must be at least 12 characters with mixed case, numbers, and special characters
  3. A two-factor authentication code will be sent to your email
  4. Enter the code to complete registration

Step 2: Connect Your First Cloud Account​

After logging in, you'll be guided through the cloud onboarding wizard.

AWS​

  1. Select AWS as your cloud provider
  2. You'll be provided with a CloudFormation template that creates a read-only cross-account IAM role
  3. Deploy the template in your AWS account
  4. Paste the resulting Role ARN back into KredSLA
  5. KredSLA validates the credentials and begins resource discovery

Required permissions: Read-only access to CloudWatch, AWS Health, and AWS Support APIs.

Azure​

  1. Select Azure as your provider
  2. Create a Service Principal using the provided CLI commands or Azure Portal instructions
  3. Grant it Monitoring Reader and Support Request Contributor roles
  4. Enter the Application ID, Client Secret, and Tenant ID
  5. KredSLA validates and begins scanning

GCP​

  1. Select GCP as your provider
  2. Create a Service Account with the provided role assignments
  3. Download the JSON key file
  4. Upload the key file to KredSLA
  5. Discovery begins automatically

OCI (Oracle Cloud)​

  1. Select OCI as your provider
  2. Provide your Tenancy OCID, User OCID, API Key Fingerprint, and PEM key file
  3. Ensure inspect permissions are granted on target compartments
  4. KredSLA validates and starts scanning
info

All cloud credentials are stored in OpenBao (an open-source Vault fork) — never in the application database. Credentials are fetched only at task execution time and never cached.

Step 3: Connect Observability (Optional)​

KredSLA can pull availability metrics from your existing observability stack for richer SLA breach detection:

PlatformIntegration Method
CloudWatchAuto-detected via AWS account
Azure MonitorAuto-detected via Azure account
GCP MonitoringAuto-detected via GCP account
OCI MonitoringAuto-detected via OCI account

All cloud-native monitoring is auto-discovered during cloud onboarding — no extra configuration needed.

To connect your observability stack:

  1. Navigate to the Observability Bridge section
  2. Select your platform
  3. Enter the required API credentials
  4. Map the integration to one or more of your connected cloud accounts
  5. KredSLA validates access and begins pulling metrics

Step 4: Automatic Discovery & Monitoring​

Once your cloud accounts are connected, KredSLA automatically:

  1. Discovers SLA-eligible resources — EC2, RDS, S3, Lambda, Virtual Machines, Cloud SQL, Autonomous Database, and dozens more across all four providers
  2. Maps service dependencies — builds a dependency graph to trace outages to their root managed-service failure
  3. Begins continuous monitoring — checks for SLA breaches every 30 minutes

You'll see your discovered resources and their SLA coverage in the dashboard immediately after the scan completes.

Step 5: Your First SLA Credit Recovery​

When KredSLA detects an SLA violation, the automated pipeline handles everything:

Breach Detected → Evidence Bundled → Claim Filed → Credit Recovered
  1. Detection — Availability drops below the provider's SLA threshold
  2. Verification — Cross-referenced against the provider's official health feed to confirm a provider-side incident
  3. Evidence bundling — Metrics, incident records, dependency paths, and SLA references are assembled automatically
  4. Filing — A support case is submitted to the cloud provider via their API
  5. Tracking — The claim is monitored until approved or rejected
  6. Recovery — Approved credits appear in your savings dashboard

You can track every claim in the Claims Tracker — with full visibility into status, evidence, and financial impact.

What's Next?​

  • User Manual — Detailed guide to every feature in the platform
  • Blog — Product updates and cloud cost management insights
  • FAQ — Common questions about KredSLA
  • Enterprise Solutions — Multi-cloud management at scale

Need Help?​