Terraform module to create Iam role resource on AWS.
We eat, drink, sleep and most importantly love DevOps. We are working towards strategies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy Bigger problems are always solved by breaking them into smaller manageable problems. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller connected yet manageable pieces within the infrastructure.
This module is basically combination of Terraform open source and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
We have fifty plus terraform modules. A few of them are comepleted and are available for open source usage while a few others are in progress.
This module has a few dependencies:
- Terraform 0.13
- Go
- github.com/stretchr/testify/assert
- github.com/gruntwork-io/terratest/modules/terraform
IMPORTANT: Since the master
branch used in source
varies based on new modifications, we suggest that you use the release versions here.
Here is an example of how you can use this module in your inventory structure:
module "iam-role" {
source = "clouddrove/iam-role/aws"
version = "0.13.0"
name = "iam-role"
application = "clouddrove"
environment = "test"
label_order = ["environment", "application", "name"]
assume_role_policy = data.aws_iam_policy_document.default.json
policy_enabled = true
policy = data.aws_iam_policy_document.iam-policy.json
}
data "aws_iam_policy_document" "default" {
statement {
effect = "Allow"
actions = ["sts:AssumeRole"]
principals {
type = "Service"
identifiers = ["ec2.amazonaws.com"]
}
}
}
data "aws_iam_policy_document" "iam-policy" {
statement {
actions = [
"ssm:UpdateInstanceInformation",
"ssmmessages:CreateControlChannel",
"ssmmessages:CreateDataChannel",
"ssmmessages:OpenControlChannel",
"ssmmessages:OpenDataChannel" ]
effect = "Allow"
resources = ["*"]
}
}
Name | Description | Type | Default | Required |
---|---|---|---|---|
application | Application (e.g. cd or clouddrove ). |
string |
"" |
no |
assume_role_policy | Whether to create Iam role. | any |
n/a | yes |
attributes | Additional attributes (e.g. 1 ). |
list |
[] |
no |
delimiter | Delimiter to be used between organization , environment , name and attributes . |
string |
"-" |
no |
description | The description of the role. | string |
"" |
no |
enabled | Whether to create Iam role. | bool |
true |
no |
environment | Environment (e.g. prod , dev , staging ). |
string |
"" |
no |
force_detach_policies | The policy that grants an entity permission to assume the role. | bool |
false |
no |
label_order | Label order, e.g. name ,application . |
list |
[] |
no |
managedby | ManagedBy, eg 'CloudDrove' or 'AnmolNagpal'. | string |
"[email protected]" |
no |
max_session_duration | The maximum session duration (in seconds) that you want to set for the specified role. If you do not specify a value for this setting, the default maximum of one hour is applied. This setting can have a value from 1 hour to 12 hours. | number |
3600 |
no |
name | Name (e.g. app or cluster ). |
string |
"" |
no |
path | The path to the role. | string |
"/" |
no |
permissions_boundary | The ARN of the policy that is used to set the permissions boundary for the role. | string |
"" |
no |
policy | The policy document. | any |
null |
no |
policy_arn | The ARN of the policy you want to apply. | string |
"" |
no |
policy_enabled | Whether to Attach Iam policy with role. | bool |
false |
no |
tags | Additional tags (e.g. map(BusinessUnit ,XYZ ). |
map |
{} |
no |
Name | Description |
---|---|
arn | The Amazon Resource Name (ARN) specifying the role. |
name | Name of specifying the role. |
tags | A mapping of tags to assign to the resource. |
In this module testing is performed with terratest and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a GO environment in your system.
You need to run the following command in the testing folder:
go test -run Test
If you come accross a bug or have any feedback, please log it in our issue tracker, or feel free to drop us an email at [email protected].
If you have found it worth your time, go ahead and give us a ★ on our GitHub!
At CloudDrove, we offer expert guidance, implementation support and services to help organisations accelerate their journey to the cloud. Our services include docker and container orchestration, cloud migration and adoption, infrastructure automation, application modernisation and remediation, and performance engineering.
We are The Cloud Experts!
We ❤️ Open Source and you can check out our other modules to get help with your new Cloud ideas.