AWS IAM Policy for Vault AWS Auth method

examples/vault-cluster-private/main.tf

@@ -36,6 +36,7 @@ module "vault_cluster" {
   allowed_inbound_security_group_ids   = []
   allowed_inbound_security_group_count = 0
   ssh_key_name                         = "${var.ssh_key_name}"
+  enable_EC2_IAM_Auth                  = "${var.enable_EC2_IAM_Auth}"
 }
 
 # ---------------------------------------------------------------------------------------------------------------------
@@ -74,11 +75,11 @@ data "template_file" "user_data_vault_cluster" {
 module "security_group_rules" {
   source = "github.com/hashicorp/terraform-aws-consul.git//modules/consul-client-security-group-rules?ref=v0.3.3"
 
-  security_group_id           = "${module.vault_cluster.security_group_id}"
+  security_group_id = "${module.vault_cluster.security_group_id}"
 
   # To make testing easier, we allow requests from any IP address here but in a production deployment, we *strongly*
   # recommend you limit this to the IP address ranges of known, trusted servers inside your VPC.
-  
+
   allowed_inbound_cidr_blocks = ["0.0.0.0/0"]
 }
 
@@ -139,6 +140,10 @@ data "aws_vpc" "default" {
 
 data "aws_subnet_ids" "default" {
   vpc_id = "${data.aws_vpc.default.id}"
+
+  tags {
+    SubnetType = "private"
+  }
 }
 
-data "aws_region" "current" {}
+data "aws_region" "current" {}

examples/vault-cluster-private/variables.tf

@@ -64,3 +64,8 @@ variable "vpc_id" {
   description = "The ID of the VPC to deploy into. Leave an empty string to use the Default VPC in this region."
   default     = ""
 }
+
+variable "enable_EC2_IAM_Auth" {
+  description = "Configure IAM Instance Profile on Vault cluster members to permit the user to enable AWS Auth backend. Note that this does NOT actually enable the backend, but merely sets policies that will permit it to function as expected."
+  default     = false
+}

examples/vault-s3-backend/main.tf

@@ -79,11 +79,11 @@ data "template_file" "user_data_vault_cluster" {
 module "security_group_rules" {
   source = "github.com/hashicorp/terraform-aws-consul.git//modules/consul-client-security-group-rules?ref=v0.3.3"
 
-  security_group_id           = "${module.vault_cluster.security_group_id}"
+  security_group_id = "${module.vault_cluster.security_group_id}"
 
   # To make testing easier, we allow requests from any IP address here but in a production deployment, we *strongly*
   # recommend you limit this to the IP address ranges of known, trusted servers inside your VPC.
-  
+
   allowed_inbound_cidr_blocks = ["0.0.0.0/0"]
 }
 
@@ -146,4 +146,4 @@ data "aws_subnet_ids" "default" {
   vpc_id = "${data.aws_vpc.default.id}"
 }
 
-data "aws_region" "current" {}
+data "aws_region" "current" {}

examples/vault-s3-backend/outputs.tf

@@ -84,4 +84,4 @@ output "consul_cluster_cluster_tag_value" {
 
 output "s3_bucket_arn" {
   value = "${module.vault_cluster.s3_bucket_arn}"
-}
+}

examples/vault-s3-backend/variables.tf

@@ -73,4 +73,4 @@ variable "s3_bucket_name" {
 variable "force_destroy_s3_bucket" {
   description = "If you set this to true, when you run terraform destroy, this tells Terraform to delete all the objects in the S3 bucket used for backend storage (if configured). You should NOT set this to true in production or you risk losing all your data! This property is only here so automated tests of this module can clean up after themselves."
   default     = false
-}
+}

main.tf

@@ -117,11 +117,11 @@ data "template_file" "user_data_vault_cluster" {
 module "security_group_rules" {
   source = "github.com/hashicorp/terraform-aws-consul.git//modules/consul-client-security-group-rules?ref=v0.3.3"
 
-  security_group_id           = "${module.vault_cluster.security_group_id}"
+  security_group_id = "${module.vault_cluster.security_group_id}"
 
   # To make testing easier, we allow requests from any IP address here but in a production deployment, we *strongly*
   # recommend you limit this to the IP address ranges of known, trusted servers inside your VPC.
-  
+
   allowed_inbound_cidr_blocks = ["0.0.0.0/0"]
 }
 
@@ -223,4 +223,4 @@ data "aws_subnet_ids" "default" {
   tags   = "${var.subnet_tags}"
 }
 
-data "aws_region" "current" {}
+data "aws_region" "current" {}

modules/vault-cluster/main.tf

@@ -202,7 +202,8 @@ resource "aws_iam_role_policy" "vault_s3" {
 }
 
 data "aws_iam_policy_document" "vault_s3" {
-  count  = "${var.enable_s3_backend ? 1 : 0}"
+  count = "${var.enable_s3_backend ? 1 : 0}"
+
   statement {
     effect  = "Allow"
     actions = ["s3:*"]
@@ -213,3 +214,27 @@ data "aws_iam_policy_document" "vault_s3" {
     ]
   }
 }
+
+resource "aws_iam_role_policy" "vault_aws_EC2_IAM_Auth" {
+  count  = "${var.enable_EC2_IAM_Auth ? 1 : 0}"
+  name   = "vault_aws_EC2_IAM_Auth"
+  role   = "${aws_iam_role.instance_role.id}"
+  policy = "${element(concat(data.aws_iam_policy_document.vault_aws_EC2_IAM_Auth.*.json, list("")), 0)}"
+}
+
+data "aws_iam_policy_document" "vault_aws_EC2_IAM_Auth" {
+  count = "${var.enable_EC2_IAM_Auth ? 1 : 0}"
+
+  statement {
+    effect = "Allow"
+
+    actions = [
+      "ec2:DescribeInstances",
+      "iam:GetInstanceProfile",
+      "iam:GetUser",
+      "iam:GetRole",
+    ]
+
+    resources = ["*"]
+  }
+}

modules/vault-cluster/outputs.tf

@@ -32,4 +32,4 @@ output "security_group_id" {
 
 output "s3_bucket_arn" {
   value = "${join(",", aws_s3_bucket.vault_storage.*.arn)}"
-}
+}

modules/vault-cluster/variables.tf

@@ -185,3 +185,8 @@ variable "force_destroy_s3_bucket" {
   description = "If 'configure_s3_backend' is enabled and you set this to true, when you run terraform destroy, this tells Terraform to delete all the objects in the S3 bucket used for backend storage. You should NOT set this to true in production or you risk losing all your data! This property is only here so automated tests of this module can clean up after themselves. Only used if 'enable_s3_backend' is set to true."
   default     = false
 }
+
+variable "enable_EC2_IAM_Auth" {
+  description = "Configure IAM Instance Profile on Vault cluster members to permit the user to enable AWS Auth backend. Note that this does NOT actually enable the backend, but merely sets policies that will permit it to function as expected."
+  default     = false
+}

modules/vault-elb/main.tf

@@ -19,8 +19,8 @@ resource "aws_elb" "vault" {
   connection_draining         = "${var.connection_draining}"
   connection_draining_timeout = "${var.connection_draining_timeout}"
 
-  security_groups    = ["${aws_security_group.vault.id}"]
-  subnets            = ["${var.subnet_ids}"]
+  security_groups = ["${aws_security_group.vault.id}"]
+  subnets         = ["${var.subnet_ids}"]
 
   # Run the ELB in TCP passthrough mode
   listener {