Describe the bug
When I try to run terragrunt apply on the openedx_devops/terraform/stacks/service/kubernetes, I encounter the MalformedPolicyDocumentException on creating the KMS key, this is the following error:
│ Error: creating KMS Key: MalformedPolicyDocumentException: Policy contains a statement with one or more invalid principals.
│
│ with module.eks.module.kms.aws_kms_key.this[0],
│ on .terraform/modules/eks.kms/main.tf line 8, in resource "aws_kms_key" "this":
│ 8: resource "aws_kms_key" "this" {
│
Workflow
This the full workflow on running the terraform & terragrunt command:
cd ./terraform/common/cookiecutter_meta
terraform init
terraform apply
cd ../../stacks/service
terragrunt run-all init
cd vpc
terragrunt apply -target module.cookiecutter_meta
terragrunt apply
cd ../kubernetes
terragrunt apply -target module.cookiecutter_meta
terragrunt apply
Getting the above error on the last step of commands. I didn't add any new IAM user as owner with admin permission in the kms_key_owners list and map_users list in the terraform/stacks/service/kubernetes/terragrunt.hcl files on first trial, just using default setting of including the IAM user for the bastion server inside these two list. Then this error happened. On the second trial, I try to add a new IAM user with admin permission but the same error occurred again.
Expected behavior
The error above does not occur.
Additional context
It will be a great gratitude if you can help me on resolving this issue. Thank you for your time to work on this.
Describe the bug
When I try to run
terragrunt applyon theopenedx_devops/terraform/stacks/service/kubernetes, I encounter theMalformedPolicyDocumentExceptionon creating the KMS key, this is the following error:Workflow
This the full workflow on running the terraform & terragrunt command:
Getting the above error on the last step of commands. I didn't add any new IAM user as owner with admin permission in the
kms_key_ownerslist andmap_userslist in theterraform/stacks/service/kubernetes/terragrunt.hclfiles on first trial, just using default setting of including the IAM user for the bastion server inside these two list. Then this error happened. On the second trial, I try to add a new IAM user with admin permission but the same error occurred again.Expected behavior
The error above does not occur.
Additional context
It will be a great gratitude if you can help me on resolving this issue. Thank you for your time to work on this.