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
When attempting to encrypt a url string with aws kms encrypt the following error occurs:
aws kms encrypt --key-id $KEY --plaintext https://atesturl.google.com
Error parsing parameter '--plaintext': Unable to retrieve https://atesturl.google.com: ('Connection aborted.', gaierror(8, 'nodename nor servname provided, or not known'))
When attempting to escape the text with single or double quotes does not help, and returns the same error.
The only way to get the tool to encrypt the string correctly is to enclose it in double quotes, which will, in the example case, decrypt to "https://atesturl.google.com"
The text was updated successfully, but these errors were encountered:
So if a value begins with http:// or https:// the CLI will grab the contents of the remote URL and use that as the value to the parameter. For parameters that require that literal value, we typically turn the feature off, but for --plaintext I am not sure that we will be able to do that given plaintext is not limited to URL values. In terms of workarounds, there are:
Use the --cli-input-json parameter for plaintext.
Add your value to a file and specify the file with file:// to the --plaintext parameter.
That being said the workarounds are not great and we would like to allow users the ability to turn the feature off. We currently have the following conversation going related to it: #2507. I would prefer to keep the conversation to that thread.
When attempting to encrypt a url string with
aws kms encrypt
the following error occurs:When attempting to escape the text with single or double quotes does not help, and returns the same error.
The only way to get the tool to encrypt the string correctly is to enclose it in double quotes, which will, in the example case, decrypt to "https://atesturl.google.com"
The text was updated successfully, but these errors were encountered: