Open ccabsolute opened 2 years ago
Similar issue on my side as I have used kms in similar fashion. No solution yet. Would ask the maintainer to resolve this soon
I have the same issue, same manner of assuming roles and getting the same error message. No solution...
Struggling with the same problem. Profile should be nothing written to the sops file, as it's highly individual and i suspect there is any use case where you have the same profile in ci and local environment.
I have the following set up to use SOPS AWS KMS decryption:
When I ran the following command locally it works:
But when I set it up in a GitLab CI pipeline job below:
It failed with the following error:
I'm using the same ~/.aws/* files inside the CI pipeline, so there shouldn't be any permission issue. If I install AWS CLI in the pipeline container, and use the same profile to list and describe the specified KMS key, then it also works. I'm not sure what else from SOPS can cause the above error. Please help shed some light. Thanks!