v2.1.1
Release Notes
- Added support of assume role to create resources using AWS IAM roles in same or different AWS accounts
- Assume Role Configuration:
- Enhanced the provider.tf file to properly utilize the AWS assume role mechanism for cross-account resource creation.
- The configuration now supports both scenarios:
- If
assume_role_config
is not provided or therole_arn
is an empty string (length of local.role_arn is 0), the provider will default to using the AWS credentials configured on your local machine. - If a valid
role_arn
is specified (length of local.role_arn is greater than 0), the provider will assume the specified role for resource creation
- If
- Updated the role configuration as follows:
role_arn = "" # Pass role ARN of another AWS account where RDS should be created; ensure required policies are added to this role.
external_id = "" # Define your external ID here
assume_role_config = length(local.role_arn) > 0 ? { role_arn = local.role_arn } : null