Files
threshold/enos/modules/iam_setup/main.tf
T
Mike Baum e1d078fa9f [QT-444] Use repo isolated AWS account for enos CI tests (#2727)
* [QT-444] Use repo isolated AWS account for enos CI tests
2023-02-16 17:07:30 -05:00

50 lines
1.3 KiB
Terraform

# Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: MPL-2.0
data "aws_caller_identity" "current" {}
variable "test_id" {}
variable "test_email" {}
locals {
# Use the AWS provided email if users are running this, override with variable for CI
user_email = var.test_email == null ? split(":", data.aws_caller_identity.current.user_id)[1] : var.test_email
}
resource "aws_iam_user" "boundary" {
name = "boundary-e2e-${var.test_id}"
# These are disabled currently, as we cannot lock down this user and still perform certain tests with the service user
# tags = { boundary-demo = local.user_email }
# permissions_boundary = "arn:aws:iam::${data.aws_caller_identity.current.account_id}:policy/BoundaryDemoPermissionsBoundary"
}
resource "aws_iam_user_policy" "boundary" {
name = "boundary_e2e_${var.test_id}"
user = aws_iam_user.boundary.name
policy = jsonencode({
"Version" : "2012-10-17",
"Statement" : [
{
"Action" : [
"ec2:DescribeInstances"
],
"Effect" : "Allow",
"Resource" : "*"
}
]
})
}
resource "aws_iam_access_key" "boundary" {
user = aws_iam_user.boundary.name
}
output "access_key_id" {
value = aws_iam_access_key.boundary.id
}
output "secret_access_key" {
value = aws_iam_access_key.boundary.secret
sensitive = true
}