#refarch - April 2025

I am starting on a new project and contemplating using:

name_pattern: "{tenant}-{stage}-{environment}"

instead of the more common:

name_pattern: "{tenant}-{environment}-{stage}"

This "feels" better as folder-structure goes {tentant}/{stage}/{environment}.yaml and typically we think of the aws accounts as {tenant}-{stage}.
Any reason for me to not do this and stick with the default?

Hi Folks @Cristian Marquez Russo and I are just getting started creating our base setup here. Alas we are stuck on Deploy Accounts

atmos workflow deploy/organization -f accounts

Error:

│ Error: creating Organizations Organization: operation error Organizations: CreateOrganization, https response error StatusCode: 400, RequestID: c19fa06d-bfd3-4098-8a05-3e5a3ca707ac, AlreadyInOrganizationException: The AWS account is already a member of an organization.
│ 
│   with aws_organizations_organization.this[0],
│   on main.tf line 107, in resource "aws_organizations_organization" "this":
│  107: resource "aws_organizations_organization" "this" {

We are certain the errors is we already have a management account set up in an organization. The challenge is we already set up SSO sync with google as our IDP. We would love to be able to use the existing organization as our root organization. Is there any easy way to bypass this .. or are we stuck having to remove the mgmt account from the org and maybe starting over with SSO?

Hi guys,
Just a quick question regarding deploying AWS-SSOSYNC.
I have enabled the vendor and I can see that the component (ssosync) was downloaded after atmos vendor pull.
I also put my ssoconfig under stacks/catalog. However, atmos doesnt see it.
How do I deploy this component?

How come the atlantis atmos config workflow doesnt use atmos to do the plan and instead uses raw terraform commands in the docs ?

This message was deleted.

we are on atmos workflow vendor -f network

Looks like we need to add all of these vendor files to vendor.yaml?

Question:
Should we pull components with multiversion approach? or just single version?

I.e.

MULTIVERSION

    - component: "tgw/hub"
      source: "<http://github.com/cloudposse/terraform-aws-components.git//modules/tgw/hub?ref={{.Version}}|github.com/cloudposse/terraform-aws-components.git//modules/tgw/hub?ref={{.Version}}>"
      version: "1.536.0"
      targets:
        - "components/terraform/{{.Component}}/{{.Version}}"

SINGLEVERSION

I.e.
    - component: "tgw/hub"
      source: "<http://github.com/cloudposse/terraform-aws-components.git//modules/tgw/hub?ref={{.Version}}|github.com/cloudposse/terraform-aws-components.git//modules/tgw/hub?ref={{.Version}}>"
      version: "1.536.0"
      targets:
        - "components/terraform/{{.Component}}"