#atmos - April 2026

Hey guys!
I have a question about Atmos MCP configuration that came up during
the latest office-hours meeting.

I've reviewed the docs at https://atmos.tools/cli/configuration/mcp and the
example at https://atmos.tools/gists/mcp-with-aws where ATMOS_PROFILE is set
for authentication.

Currently, I'm defining multiple MCP servers and need to set ATMOS_PROFILE and
identity for each one individually. For example:

mcp:
  servers:
    server-one:
      env:
        ATMOS_PROFILE: 'managers'
      identity: "core-root/terraform"
    server-two:
      env:
        ATMOS_PROFILE: 'managers'
      identity: "core-root/terraform"

Is there a way to configure ATMOS_PROFILE and identity globally so they apply to all MCP servers by default, rather than repeating them in each server definition?

PS: I think the links for the last office hour are missing on the channel.

Hi,

Is there any issue with cloudposse/utils? Why can't I fetch it?

Hi, I have a quick question about components under https://github.com/cloudposse-terraform-components

Why do they require the account-map component to be present? Isn't account map deprecated?

Yes, we are moving away from account map for all new engagements. For the next year, we need to straddle a world where both work, before we fully yank it out. We therefore use a providers.tf mixin that doesn't use account map.

Hey guys, I have a question about ci.comments is there a ENV to disable this?
https://atmos.tools/cli/configuration/ci/comments

I like it and want it for most of my CI/CD workflows but I'm trying to do a custom drift detection workflow where I will not like this to be trigger but I don't see a way to disable this using an ENV like ATMOS_COMMENTS_ENABLED=FALSE

We've added an example of using Atmos Native CI with GitHub Job Matrixes:
https://github.com/cloudposse-examples/atmos-native-ci-advanced

We've Updated the Atmos Native CI examples also to use containerized steps rather than run github-action-setup-atmos since it's way more performant.
https://github.com/cloudposse-examples/atmos-native-ci

❓️ Is there a way, to combine JIT and generating overrides files like this?
https://developer.hashicorp.com/terraform/language/files/override#merging-locals-blocks

Starting to dig into this feature
https://atmos.tools/stacks/generate

Hello! I'm looking for a way to switch identity depending on the component in a stack.

I have a default identity which I use store terraform state file, But the component that I'm trying to create should be on another account. I have tried using the component level identity selection, but it isn't working. it tries to create the component on the default identity no matter the config I tried.

We added a batch deployment dashboard to Atmos Pro which is useful when PRs touch a lot of components and the normal mermaid-style diagrams cannot be shown due to comment-size limitations.

Hi guys!
Is there any article/documentation on how to move from Terraform to OpenTofu? (tf 1.5.7)

Hello,
I'm asking because I didn't see about this in the Atmos documentation. Is it possible to add the Git commit and branch to the variables? This would allow us to tag resources and thus track the code that created or modified them. Do you think this is a good idea? And Then would you consider adding this feature to the Atmos core?

Just another friendly reminder: if you are waiting on a resolution to an issue you have opened, please check if there's an associated PR. If there is, it's probably held up on validation, and any help we can get to validate those pull requests will expedite merging and cutting a release.