Atmos Pro Logo

Atmos Pro

ProductPricingDocsBlogChangelog
⌘K
Create Workspace
Atmos Pro Logo

Atmos Pro

ProductPricingDocsBlogChangelog
What is Atmos Pro?
Installation
How it Works
Workspaces
Authentication
Ordered Deployments
Deployment Approvals
Deployment Locking
Drift Detection
Event Triggers
Workflow Dispatches
Repository Permissions
Audit Log
Troubleshooting
Workspaces
Atmos Stacks
Atmos CI
Atmos Toolchain
Cloud Authentication
GitHub Repository
GitHub Workflows
GitHub Environments
Deployment Locking
Drift Detection
Webhooks
AWS
Reference
Atmos Docs
Example Repository
What is Atmos Pro?
Installation
How it Works
Workspaces
Authentication
Ordered Deployments
Deployment Approvals
Deployment Locking
Drift Detection
Event Triggers
Workflow Dispatches
Repository Permissions
Audit Log
Troubleshooting
Workspaces
Atmos Stacks
Atmos CI
Atmos Toolchain
Cloud Authentication
GitHub Repository
GitHub Workflows
GitHub Environments
Deployment Locking
Drift Detection
Webhooks
AWS
Reference
Atmos Docs
Example Repository

Atmos CI

Configure Atmos native CI integration to automatically update commit statuses, create job summaries, and export plan results inside GitHub Actions.


Atmos has native CI integration that allows it to automatically operate inside GitHub Actions — updating commit statuses, creating job summaries, and exporting plan results. Configure the ci block in your atmos.yaml to enable these features.
atmos.yaml
ci:
  enabled: true
  output:
    enabled: true
  summary:
    enabled: true
  checks:
    enabled: true
    context_prefix: ""
    statuses:
      component: true
      add: true
      change: true
      destroy: true
Each sub-feature controls a specific CI integration:
  • output — When enabled, exports variables to $GITHUB_OUTPUT so downstream steps in your workflow can reference plan results (e.g., whether changes were detected).
  • summary — When enabled, writes a formatted plan summary to $GITHUB_STEP_SUMMARY, which GitHub renders directly on the workflow run page.
  • checks — When enabled, posts commit status checks to the pull request. The context_prefix lets you namespace the check names, and the statuses map controls which check types are reported: component for per-component status, and add, change, destroy for resource-level operation statuses.

Next: Configure GitHub Workflows

Create the GitHub Actions workflows that Atmos Pro dispatches to plan, apply, and detect drift on your infrastructure.

Configure WorkflowsConfigure Atmos Stacks

Atmos StacksAtmos Toolchain
Atmos Pro Logo

Atmos Pro

The fastest way to deploy your apps on AWS with Terraform and GitHub Actions.

GitHubTwitterLinkedInYouTubeSlack

For Developers

  • Quick Start
  • Example Workflows
  • Atmos Documentation

Community

  • Register for Office Hours
  • Join the Slack Community
  • Try our Newsletter

Company

  • About Cloud Posse
  • Security
  • Pricing
  • Blog
  • Media Kit

Legal

  • SaaS Agreement
  • Terms of Use
  • Privacy Policy
  • Disclaimer
  • Cookie Policy

© 2026 Cloud Posse, LLC. All rights reserved.

Checking status...