#cloudposse (2024-03)
| <http://cloudposse.com/quiz | cloudposse.com/quiz> |
| Want to hire Cloud Posse? Take our quiz. <http://cloudposse.com/quiz | cloudposse.com/quiz> |
2024-03-04
2024-03-13
Hello Folks!!, related to this repo https://github.com/cloudposse/terraform-spacelift-cloud-infrastructure-automation wondering how do you manage integrations for the stacks created. Those are not referenced in the modules
this module is used by these components (terraform root modules) https://github.com/cloudposse/terraform-aws-components/tree/main/modules/spacelift, which create Spacelift worker pools, Spacelift admin stacks (which create regular stacks), and Spacelift policies
yeah, thanks, but Im still failing to understand how Cloud Integrations (in my case AWS) are attached to every stack created by the admin-stack
if you use private workers, the role to assume is the EC2 profile https://github.com/cloudposse/terraform-aws-components/blob/main/modules/spacelift/worker-pool/iam.tf#L83
if you use public workers, then you can provide an IAM role to asume to each stack
ah, ok, thats the reason, I use the public ones
variable "aws_role_arn" {
type = string
description = "ARN of the AWS IAM role to assume and put its temporary credentials in the runtime environment"
default = null
}
variable "aws_role_enabled" {
type = bool
description = "Flag to enable/disable Spacelift to use AWS STS to assume the supplied IAM role and put its temporary credentials in the runtime environment"
default = false
}
yeah, make sense now, thanks for the inputs
Im using the “new” approach, thats why I was not able to find what I was looking for