Skip to main content

Component: aws-teams

This component is responsible for provisioning all primary user and system roles into the centralized identity account. This is expected to be used alongside the aws-team-roles component to provide fine-grained role delegation across the account hierarchy.

Teams Function Like Groups and are Implemented as Roles

The "teams" created in the identity account by this module can be thought of as access control "groups": a user who is allowed access one of these teams gets access to a set of roles (and corresponding permissions) across a set of accounts. Generally, there is nothing else provisioned in the identity account, so the teams have limited access to resources in the identity account by design.

Teams are implemented as IAM Roles in each account. Access to the "teams" in the identity account is controlled by the aws-saml and aws-sso components. Access to the roles in all the other accounts is controlled by the "assume role" policies of those roles, which allow the "team" or AWS SSO Permission set to assume the role (or not).

Privileges are Defined for Each Role in Each Account by aws-team-roles

Every account besides the identity account has a set of IAM roles created by the aws-team-roles component. In that component, the account's roles are assigned privileges, and those privileges ultimately determine what a user can do in that account.

Access to the roles can be granted in a number of ways. One way is by listing "teams" created by this component as "trusted" (trusted_teams), meaning that users who have access to the team role in the identity account are allowed (trusted) to assume the role configured in the target account. Another is by listing an AWS SSO Permission Set in the account (trusted_permission_sets).

Role Access is Enabled by SAML and/or AWS SSO configuration

Users can again access to a role in the identity account through either (or both) of 2 mechanisms:

SAML Access

  • SAML access is globally configured via the aws-saml component, enabling an external SAML Identity Provider (IdP) to control access to roles in the identity account. (SAML access can be separately configured for other accounts, see the aws-saml and aws-team-roles components for more on that.)
  • Individual roles are enabled for SAML access by setting aws_saml_login_enabled: true in the role configuration.
  • Individual users are granted access to these roles by configuration in the SAML IdP.

AWS SSO Access

The aws-sso component can create AWS Permission Sets that allow users to assume specific roles in the identity account. See the aws-sso component for details.


Stack Level: Global Deployment: Must be deployed by SuperAdmin using atmos CLI

Here's an example snippet for how to use this component. The component should only be applied once, which is typically done via the identity stack (e.g. gbl-identity.yaml).

role_arn: null
# Viewer has the same permissions as Observer but only in this account. It is not allowed access to other accounts.
# Viewer also serves as the default configuration for all roles via the YAML anchor.
viewer: &user-template
# `max_session_duration` set the maximum session duration (in seconds) for the IAM roles.
# This setting can have a value from 3600 (1 hour) to 43200 (12 hours).
# For roles people log into via SAML, a long duration is convenient to prevent them
# from having to frequently re-authenticate.
# For roles assumed from some other role, the setting is practically irrelevant, because
# the AssumeRole API limits the duration to 1 hour in any case.
# References:
# -
# -
max_session_duration: 43200 # 12 hours in seconds

# role_policy_arns are the IAM Policy ARNs to attach to this policy. In addition to real ARNs,
# you can use keys in the `custom_policy_map` in `` to select policies defined in the component.
# If you are using keys from the map, plans look better if you put them after the real role ARNs.
- "arn:aws:iam::aws:policy/job-function/ViewOnlyAccess"
role_description: "Team restricted to viewing resources in the identity account"
# If `aws_saml_login_enabled: true` then the role will be available via SAML logins.
# Otherwise, it will only be accessible via `assume role`.
aws_saml_login_enabled: false

# The following attributes control access to this role via `assume role`.
# `trusted_*` grants access, `denied_*` denies access.
# If a role is both trusted and denied, it will not be able to access this role.

# Permission sets specify users operating from the given AWS SSO permission set in this account.
trusted_permission_sets: []
denied_permission_sets: []

# Primary roles specify the short role names of roles in the primary (identity)
# account that are allowed to assume this role.
trusted_teams: []
denied_teams: ["viewer"]

# Role ARNs specify Role ARNs in any account that are allowed to assume this role.
# BE CAREFUL: there is nothing limiting these Role ARNs to roles within our organization.
trusted_role_arns: []
denied_role_arns: []

<<: *user-template
"Team with PowerUserAccess permissions in `identity` and AdministratorAccess to all other accounts except
# Limit `admin` to Power User to prevent accidentally destroying the admin role itself
# Use SuperAdmin to administer IAM access
role_policy_arns: ["arn:aws:iam::aws:policy/PowerUserAccess"]

# TODO Create a "security" team with AdministratorAccess to audit and security, remove "admin" write access to those accounts
aws_saml_login_enabled: true
# list of roles in primary that can assume into this role in delegated accounts
# primary admin can assume delegated admin
trusted_teams: ["admin"]
# GH runner should be moved to its own `ghrunner` role
trusted_permission_sets: ["IdentityAdminTeamAccess"]

<<: *user-template
role_description: Team for our privileged Spacelift server
- team_role_access
aws_saml_login_enabled: false
- admin
trusted_role_arns: ["arn:aws:iam::123456789012:role/eg-ue2-auto-spacelift-worker-pool-admin"]


terraform>= 1.0.0
aws>= 4.9.0
local>= 1.3


aws>= 4.9.0
local>= 1.3




aws_iam_policy_document.assume_role_aggregateddata source
aws_iam_policy_document.team_role_accessdata source


account_map_environment_nameThe name of the environment where account_map is provisionedstring"gbl"no
account_map_stage_nameThe name of the stage where account_map is provisionedstring"root"no
additional_tag_mapAdditional key-value pairs to add to each map in tags_as_list_of_maps. Not added to tags or id.
This is for some rare cases where resources want additional configuration of tags
and therefore take a list of maps with tag key, value, and additional configuration.
attributesID element. Additional attributes (e.g. workers or cluster) to add to id,
in the order they appear in the list. New attributes are appended to the
end of the list. The elements of the list are joined by the delimiter
and treated as a single ID element.
aws_saml_environment_nameThe name of the environment where SSO is provisionedstring"gbl"no
aws_saml_stage_nameThe name of the stage where SSO is provisionedstring"identity"no
contextSingle object for setting entire context at once.
See description of individual variables for details.
Leave string and numeric variables as null to use default value.
Individual variable settings (non-null) override settings in context object,
except for attributes, tags, and additional_tag_map, which are merged.
"additional_tag_map": {},
"attributes": [],
"delimiter": null,
"descriptor_formats": {},
"enabled": true,
"environment": null,
"id_length_limit": null,
"label_key_case": null,
"label_order": [],
"label_value_case": null,
"labels_as_tags": [
"name": null,
"namespace": null,
"regex_replace_chars": null,
"stage": null,
"tags": {},
"tenant": null
delimiterDelimiter to be used between ID elements.
Defaults to - (hyphen). Set to "" to use no delimiter at all.
descriptor_formatsDescribe additional descriptors to be output in the descriptors output map.
Map of maps. Keys are names of descriptors. Values are maps of the form
{<br/> format = string<br/> labels = list(string)<br/>}
(Type is any so the map values can later be enhanced to provide additional options.)
format is a Terraform format string to be passed to the format() function.
labels is a list of labels, in order, to pass to format() function.
Label values will be normalized before being passed to format() so they will be
identical to how they appear in id.
Default is {} (descriptors output will be empty).
enabledSet to false to prevent the module from creating any resourcesboolnullno
environmentID element. Usually used for region e.g. 'uw2', 'us-west-2', OR role 'prod', 'staging', 'dev', 'UAT'stringnullno
id_length_limitLimit id to this many characters (minimum 6).
Set to 0 for unlimited length.
Set to null for keep the existing setting, which defaults to 0.
Does not affect id_full.
import_role_arnIAM Role ARN to use when importing a resourcestringnullno
label_key_caseControls the letter case of the tags keys (label names) for tags generated by this module.
Does not affect keys of tags passed in via the tags input.
Possible values: lower, title, upper.
Default value: title.
label_orderThe order in which the labels (ID elements) appear in the id.
Defaults to ["namespace", "environment", "stage", "name", "attributes"].
You can omit any of the 6 labels ("tenant" is the 6th), but at least one must be present.
label_value_caseControls the letter case of ID elements (labels) as included in id,
set as tag values, and output by this module individually.
Does not affect values of tags passed in via the tags input.
Possible values: lower, title, upper and none (no transformation).
Set this to title and set delimiter to "" to yield Pascal Case IDs.
Default value: lower.
labels_as_tagsSet of labels (ID elements) to include as tags in the tags output.
Default is to include all labels.
Tags with empty values will not be included in the tags output.
Set to [] to suppress all generated tags.
The value of the name tag, if included, will be the id, not the name.
Unlike other null-label inputs, the initial setting of labels_as_tags cannot be
changed in later chained modules. Attempts to change it will be silently ignored.
nameID element. Usually the component or solution name, e.g. 'app' or 'jenkins'.
This is the only ID element not also included as a tag.
The "name" tag is set to the full id string. There is no tag with the value of the name input.
namespaceID element. Usually an abbreviation of your organization name, e.g. 'eg' or 'cp', to help ensure generated IDs are globally uniquestringnullno
regex_replace_charsTerraform regular expression (regex) string.
Characters matching the regex will be removed from the ID elements.
If not set, "/[^a-zA-Z0-9-]/" is used to remove all characters other than hyphens, letters and digits.
regionAWS Regionstringn/ayes
stageID element. Usually used to indicate role, e.g. 'prod', 'staging', 'source', 'build', 'test', 'deploy', 'release'stringnullno
tagsAdditional tags (e.g. {'BusinessUnit': 'XYZ'}).
Neither the tag keys nor the tag values will be modified by this module.
teams_configA roles map to configure the accounts.
denied_teams = list(string)
denied_permission_sets = list(string)
denied_role_arns = list(string)
max_session_duration = number # in seconds 3600 <= max <= 43200 (12 hours)
role_description = string
role_policy_arns = list(string)
aws_saml_login_enabled = bool
allowed_roles = optional(map(list(string)), {})
trusted_teams = list(string)
trusted_permission_sets = list(string)
trusted_role_arns = list(string)
tenantID element _(Rarely used, not included by default)_. A customer identifier, indicating who this instance of a resource is forstringnullno
trusted_github_reposMap where keys are role names (same keys as teams_config) and values are lists of
GitHub repositories allowed to assume those roles. See account-map/modules/
for specifics about repository designations.


role_arnsList of role ARNs
team_name_role_arn_mapMap of team names to role ARNs
team_namesList of team names
teams_configMap of team config with name, target arn, and description

Known Problems

Error: assume role policy: LimitExceeded: Cannot exceed quota for ACLSizePerRole: 2048

The aws-teams architecture, when enabling access to a role via lots of AWS SSO Profiles, can create large "assume role" policies, large enough to exceed the default quota of 2048 characters. If you run into this limitation, you will get an error like this:

Error: error updating IAM Role (acme-gbl-root-tfstate-backend-analytics-ro) assume role policy: LimitExceeded: Cannot exceed quota for ACLSizePerRole: 2048

This can happen in either/both the identity and root accounts (for Terraform state access). So far, we have always been able to resolve this by requesting a quota increase, which is automatically granted a few minutes after making the request. To request the quota increase:

  • Log in to the AWS Web console as admin in the affected account

  • Set your region to N. Virginia us-east-1

  • Navigate to the Service Quotas page via the account dropdown menu

  • Click on AWS Services in the left sidebar

  • Search for "IAM" and select "AWS Identity and Access Management (IAM)". (If you don't find that option, make sure you have selected the us-east-1 region.

  • Find and select "Role trust policy length"

  • Request an increase to 4096 characters

  • Wait for the request to be approved, usually less than a few minutes