LogoLogo
  • Welcome to Heeler!
    • Overview
    • Terminology
  • Getting Started
    • Code Setup
      • GitHub
      • GitLab
      • Azure DevOps
      • Bitbucket
      • Artifactory
      • GitHub Container Registry
      • On-Premises Broker
    • Cloud Setup
      • Amazon Web Services
        • AWS Supported Services
        • AWS Event Collection
      • Google Cloud Platform
        • GCP Supported Services
        • GCP Event Collection
    • Environment Boundaries
      • Implementing an Organizational Unit or Account Strategy
      • Implementing a Tag Strategy
      • Implementing a Resource Strategy
    • Integration Setup
      • Jira
      • Slack
      • Microsoft Teams
      • Shortcut
    • User Management
      • SAML / Single Sign-On
  • Product Walk-Through
    • Dashboard
    • Catalog
    • Security
Powered by GitBook
On this page

Was this helpful?

  1. Getting Started
  2. Environment Boundaries

Implementing an Organizational Unit or Account Strategy

There is little to do to implement a strategy for Organizational Units/Folders (AWS/GCP) or for Accounts/Project (AWS/GCP). It is managed in the Heeler Environments page. It will dynamically assign Environment Tags to resources based upon their membership.

If there are overlapping assignments, e.g., a resource is in an account tagged Environent: Disaster Recovery, but in an OU tagged Environment: Production, the more narrowly scoped account tag will take precedence.

PreviousEnvironment BoundariesNextImplementing a Tag Strategy

Last updated 8 months ago

Was this helpful?