dragondrop docs
dragondrop.cloud
  • Welcome
  • Getting Started
    • How dragondrop Works
    • 🔒Security
    • Self-Hosted Runners
    • Cloud Perch - Cloud Footprint Visualizations
    • Jobs
      • What is a Job?
      • How Many Jobs Should We Use?
      • Creating a Job
      • Running a Job
      • Managed Drift Only Mode
      • Job Output
    • Setting Up CI/CD
    • Supported Tech Stack
    • Signing Up
    • Schedule a Demo
  • Deploying To Your Cloud
    • Infrastructure Requirements
      • Requirements
      • AWS
      • Azure
      • GCP
    • Environment Variables
    • Updating HTTPS Job Endpoints
    • FAQs
  • Setting Up CI/CD
    • GitHub Action
  • Pricing & Plans
    • Plans
    • FAQs
  • Trouble Shooting
    • Resource Coverage
      • AWS
      • Azure
      • GCP
    • Contact Support
Powered by GitBook
On this page
  • Recommended Job Segmentations
  • Hard Restrictions
  • No Restrictions
Edit on GitHub
  1. Getting Started
  2. Jobs

How Many Jobs Should We Use?

Best practices for using managed Jobs to cover your cloud

PreviousWhat is a Job?NextCreating a Job

Last updated 1 year ago

Recommended Job Segmentations

We recommend creating one Job per logical grouping of infrastructure. This allows recommendations for different infrastructure groupings to be assigned to relevant engineers with expertise in that particular grouping, and keeps recommendations relevant and focused for those reviewing them.

Some examples of infrastructure groupings for assigning cloud-concierge jobs:

  • Infrastructure segmented by application.

  • Infrastructure segmented by managing team.

  • Infrastructure segmented by Cloud Provider

  • Infrastructure segmented by development environment (dev, prod, staging)

Hard Restrictions

The only hard restriction is that a single cloud-concierge container can only output recommendations and results to a single repository in your version control system.

No Restrictions

  • A Job can be run an unlimited number of times each month.

cloud-concierge