Попытка использовать Terragrunt (терраформ) с Okta

Я пытаюсь использовать Okta в Terragrunt, и у меня возникают проблемы при принятии на себя этой роли. Мой файл ~ / .aws / config

aws_saml_url = home/amazon_aws/XXXXXXXXX/XXXXXXXXX

[profile assume-admin]
role_arn = arn:aws:iam::XXXXXXXXX:role/assumeAdmin
region = us-west-2

[profile dev]
source_profile = assume-admin
role_arn = arn:aws:iam::XXXXXXXXX:role/adminUser

Без terragrunt, используя только Terraform и Okta, я не вижу никаких проблем.

$ aws-okta exec dev -- bash
$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.terraform_remote_state.bastion: Refreshing state...
data.terraform_remote_state.vpc: Refreshing state...
data.terraform_remote_state.bastion: Refreshing state...
data.terraform_remote_state.vpc: Refreshing state...
data.aws_caller_identity.current: Refreshing state...

SNIP

Plan: 0 to add, 2 to change, 0 to destroy.

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.

Теперь использую Terragrunt

terragrunt plan
[terragrunt] [/Users/user/dev/infrastructure/terraform/accounts/dev/us-west-2/dev/app] 2018/07/23 17:32:56 Running command: terraform --version
[terragrunt] 2018/07/23 17:32:56 Reading Terragrunt config file at /Users/user/dev/infrastructure/terraform/accounts/dev/us-west-2/dev/app/terraform.tfvars
[terragrunt] 2018/07/23 17:32:56 Backend s3 has not changed.
[terragrunt] 2018/07/23 17:32:56 Error initializing session: SharedConfigAssumeRoleError: failed to load assume role for arn:aws:iam::XXXXXXXXX:role/adminUser, source profile has no shared credentials
[terragrunt] 2018/07/23 17:32:56 Unable to determine underlying exit code, so Terragrunt will exit with error code 1

Спасибо.


person sebastian    schedule 24.07.2018    source источник


Ответы (1)


Я смог решить эту проблему, установив AWS_CONFIG_FILE=/dev/null после выполнения aws-okta exec takt-dev -- bash, который загрузил мои AWS_ * creds / переменные.

Использование AWS_PROFILE=PROFILE_NAME или неопределенность переменных оболочки с unset AWS_* вернет ошибку, о которой я упоминал выше.

К вашему сведению. Я использую Terraform v0.11.7

person sebastian    schedule 24.07.2018