The KMS does not support any other cipher other than AES/CTR in the current implementation. One can change the cipher in core-site.xml but that will throw an error since AES/CTR has been hardcoded.
Cool, thanks for explaining.
I havent put some information in the logs because of either sensitive matter or access control.
Agreed. Though I was referring to the input parameters (from HTTP requests), such as eekOp of decryptEncryptedKey.
I think we should make that as a separate effort for the KMS.