Data source for AWS Organizations account tagging

[pascal-hofmann]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

#8896 added support for AWS Organizations account tagging to aws_organizations_account.
Unfortunately there is no way to get the list of tags for an account via data source.

• I suggest to introduce a new data source aws_organizations_account that exposes account details including tags.
• Alternatively there could be a new data source aws_organizations_account_tags.
• Or maybe even a more generic data source aws_resource_tags.

Related API calls: ListTagsForResource, ListAccounts

New or Affected Resource(s)

• new data source aws_organizations_account or
• new data source aws_organizations_account_tags or
• new data source aws_resource_tags

Potential Terraform Configuration

data "aws_organizations_account" "example" {
  filter {
    name   = "id"
    values = ["987654321234"]
  }
  filter {
    name   = "name"
    values = […]
  }
  …
}

data "aws_organizations_account_tags" "example" {
  id = "987654321234"
}

data "aws_resource_tags" "example" {
  id = "987654321234"
}

References

• AWS Organizations account tagging #8896

[AMMullan]

Can definitely see massive use-cases for this - especially if we can get a list of accounts based on a tag. Potentially we could look at expanding AWS behaviour to allow applying SCP's based on a Tag which would be amazing!

[gramsa49]

My use case for this capability is to store key information, per AWS account, that can be used to retrieve data from external systems (Terraform data source) to drive Terraform automation. As an example, if AWS account X hosts application system Y, the AWS Orgs Account tags should have an identifier for application system Y. This can be used to retrieve other critical information regarding cost allocations, availability goals, contact information, criticality rating, etc., which can in turn be used to drive other Terraform automation.

In our case, AWS accounts are not created using Terraform, so this information is otherwise inaccessible.

[github-actions]

This functionality has been released in v3.71.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.