-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support For Sign operation in KMS Enclave SDK Apis #127
Comments
Are you running the enclave in debug mode? |
Hello Richard and thanks for your response. as visible in cloudtrail log, request is "AccessDenied"
|
Cloud trail logs of previously successful call when KMS policy doesn't contain Attestation value conditions
I am making sure that Attestation documents are getting passed in KMS C SDK Code.
|
I face the same issue. I think kms sign action don't support pcr config. kms:RecipientAttestation:ImageSha384 only support: Here is the doc: |
Hi , We have modified AWS Nitro C SDK to Support Sign operations within Enclave. It works well without attestation document and gives the desired output. But when PCR value is added in KMS policy,
Like below,
It would end up giving following error.
Got non-200 answer from KMS: 400 - {"__type":"AccessDeniedException","Message":"User: arn:aws:sts::3598780XXXXX:assumed-role/nume-enclave-role/i-0b11f180a81f2fea2 is not authorized to perform: kms:Sign on resource: arn:aws:kms:us-east-1:3598780XXXXX:key/fb506b65-0192-4881-b1d2-8ce98aXXXXX because no resource-based policy allows the kms:Sign action"}
Could the team please add the support for Attestation document check verification for KMS Sign and PutKeyPolicy APIs (at KMS Backend)
We have a use case where we want to securely Sign the message as well as update update KMS policy from enclave.
The text was updated successfully, but these errors were encountered: