#atmos - June 2026

Hello, is there any way I can use variable in atlantis integration template? I don't want to add concept of tenant or stage to our terraform when we have slightly different variables. Something like this:

    project_templates:
      project-1:
        name: "{{var.name}}-{{var.custom_name}}"

I tried workarounds with passing things like this but it didn't work

vars:
  custom_name: <value>
  stage: {{ .vars.custom_name }}

Hey!
I have open a new issue for ECR loging multiple times:
https://github.com/cloudposse/atmos/issues/2562

Upvote! https://www.reddit.com/r/Terraform/comments/1tr1hun/comment/oosbzmi/

(not sure who posted this, but thanks!)

Hey Guys,
I would like to know if support for aws secrets manager or encrypted params in param store is comming?
https://atmos.tools/stacks/sharing-state/stores

With the recent shift toward native CI, and the deprecation of the GHAs (🥳 ) what's the current guidance for drift detection w/ native CI?

Hey guys
I have a question, Is there a way to filter out some global variables? for example I have configure region as a vars on the _defaults for the org but there is just 1 component where I will like to not pass that region to, is there a way to do this?

I'd like to give a massive shout out to @shirkevich for working closely with us to implement parallel/concurrent execution in Atmos. In the upcoming release, you can control concurrency of --all and --affected for plan and apply operations.

e.g.

atmos terraform plan --all -s prod --max-concurrency=4

https://atmos.tools/changelog/terraform-dag-concurrency