Terraform module to aggregate multiple IAM policy documents into single policy document.
NOTE: This module is now deprecated due to new functionality in the Terraform AWS Provider. See below on migration steps
Now that the AWS provider supports the override_policy_documents argument on the aws_iam_policy_document data source, this module is no longer necessary. All code using this module can be migrated to natively use the aws_iam_policy_document data source by doing the following change:
# Previous module usage:
module "aggregated_policy" {
source = "cloudposse/iam-policy-document-aggregator/aws"
version = "0.8.0"
source_documents = [
data.aws_iam_policy_document.base.json,
data.aws_iam_policy_document.resource_full_access.json
]
}Replace the above with:
data "aws_iam_policy_document" "aggregated" {
override_policy_documents = [
data.aws_iam_policy_document.base.json,
data.aws_iam_policy_document.resource_full_access.json
]
}And then update your references to module.aggregated_policy.result_document with data.aws_iam_policy_document.aggregated.json.
Please see the discussion in #31 for further details.
This project is part of our comprehensive "SweetOps" approach towards DevOps.
It's 100% Open Source and licensed under the APACHE2.
We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!
Security scanning is graciously provided by Bridgecrew. Bridgecrew is the leading fully hosted, cloud-native solution providing continuous Terraform security and compliance.
| Benchmark | Description |
|---|---|
| Infrastructure Security Compliance | |
| Center for Internet Security, KUBERNETES Compliance | |
| Center for Internet Security, AWS Compliance | |
| Center for Internet Security, AZURE Compliance | |
| Payment Card Industry Data Security Standards Compliance | |
| National Institute of Standards and Technology Compliance | |
| Information Security Management System, ISO/IEC 27001 Compliance | |
| Service Organization Control 2 Compliance | |
| Center for Internet Security, GCP Compliance | |
| Health Insurance Portability and Accountability Compliance |
IMPORTANT: We do not pin modules to versions in our examples because of the difficulty of keeping the versions in the documentation in sync with the latest released versions. We highly recommend that in your code you pin the version to the exact version you are using so that your infrastructure remains stable, and update versions in a systematic way so that they do not catch you by surprise.
Also, because of a bug in the Terraform registry (hashicorp/terraform#21417), the registry shows many of our inputs as required when in fact they are optional. The table below correctly indicates which inputs are required.
For a complete example, see examples/complete.
For automated tests of the complete example using bats and Terratest (which tests and deploys the example on AWS), see test.
This example creates a single IAM policy document from multiple IAM policy documents.
data "aws_iam_policy_document" "resource_full_access" {
statement {
sid = "FullAccess"
effect = "Allow"
resources = ["arn:aws:s3:::bucketname/path/*"]
actions = [
"s3:PutObject",
"s3:PutObjectAcl",
"s3:GetObject",
"s3:DeleteObject",
"s3:ListBucket",
"s3:ListBucketMultipartUploads",
"s3:GetBucketLocation",
"s3:AbortMultipartUpload"
]
}
}
data "aws_iam_policy_document" "base" {
statement {
sid = "BaseAccess"
effect = "Allow"
resources = ["*"]
actions = [
"s3:ListBucket",
"s3:ListBucketVersions"
]
}
}
module "aggregated_policy" {
source = "cloudposse/iam-policy-document-aggregator/aws"
# Cloud Posse recommends pinning every module to a specific version
# version = "x.x.x"
source_documents = [
data.aws_iam_policy_document.base.json,
data.aws_iam_policy_document.resource_full_access.json
]
}The example directory contains the example.
| Name | Version |
|---|---|
| terraform | >= 0.13.0 |
| aws | >= 2.23 |
| Name | Version |
|---|---|
| aws | >= 2.23 |
No modules.
| Name | Type |
|---|---|
| aws_iam_policy_document.default | data source |
| aws_iam_policy_document.eight | data source |
| aws_iam_policy_document.empty | data source |
| aws_iam_policy_document.five | data source |
| aws_iam_policy_document.four | data source |
| aws_iam_policy_document.nine | data source |
| aws_iam_policy_document.one | data source |
| aws_iam_policy_document.seven | data source |
| aws_iam_policy_document.six | data source |
| aws_iam_policy_document.three | data source |
| aws_iam_policy_document.two | data source |
| aws_iam_policy_document.zero | data source |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| source_documents | List of JSON IAM policy documents. Limits: * List size max 10 * Statement can be overriden by the statement with the same sid from the latest policy. |
list(string) |
[] |
no |
| Name | Description |
|---|---|
| result_document | Aggregated IAM policy |
Like this project? Please give it a ★ on our GitHub! (it helps us a lot)
Are you using this project or any of our other projects? Consider leaving a testimonial. =)
Check out these related projects.
- terraform-aws-iam-role - A Terraform module that creates IAM role with provided JSON IAM polices documents.
- terraform-aws-iam-chamber-s3-role - Terraform module to provision an IAM role with configurable permissions to access S3 as chamber backend.
Got a question? We got answers.
File a GitHub issue, send us an email or join our Slack Community.
We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
- Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
- Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
- Site Reliability Engineering. You'll have total visibility into your apps and microservices.
- Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
- GitOps. You'll be able to operate your infrastructure via Pull Requests.
- Training. You'll receive hands-on training so your team can operate what we build.
- Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
- Troubleshooting. You'll get help to triage when things aren't working.
- Code Reviews. You'll receive constructive feedback on Pull Requests.
- Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.
Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.
Participate in our Discourse Forums. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!
Please use the issue tracker to report any bugs or file feature requests.
If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull Request so that we can review your changes
NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!
Copyright © 2017-2022 Cloud Posse, LLC
See LICENSE for full details.
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
All other trademarks referenced herein are the property of their respective owners.
This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!
We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.
We offer paid support on all of our projects.
Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.
 Igor Rodionov |
 Maxim Mironenko |
 Erik Osterman |
 Andriy Knysh |
|---|