You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
This tries to find the key in the current AWS role, but we use role assuming, so our base role doesn't actually have access to the account and resources. The general aws provider does role-assuming based on how it's configured but bless doesn't currently support that so it cannot switch to the correct role to access KMS. Profile doesn't work either because our base STS credentials are env-only thus role-assuming based on ~/.aws/config fails with a message about the base profile not having credentials (which is correct, the base profile is loaded via aws-vault using STS creds):
provider "aws" {
version = ">= 2.0.0"
region = "eu-west-1"
assume_role {
role_arn = "${lookup(var.role_arns, var.account)}"
}
}
A few edits later: I suppose this is more like a feature request than a bug.
The text was updated successfully, but these errors were encountered:
johnkeates
changed the title
bless bless_ca fails to call KMS
bless bless_ca fails to call KMS when using roles
Nov 24, 2019
Running a bare minimum config:
This tries to find the key in the current AWS role, but we use role assuming, so our base role doesn't actually have access to the account and resources. The general aws provider does role-assuming based on how it's configured but bless doesn't currently support that so it cannot switch to the correct role to access KMS. Profile doesn't work either because our base STS credentials are env-only thus role-assuming based on ~/.aws/config fails with a message about the base profile not having credentials (which is correct, the base profile is loaded via aws-vault using STS creds):
A few edits later: I suppose this is more like a feature request than a bug.
The text was updated successfully, but these errors were encountered: