FG
💻 Software☁️ Cloud & DevOpsAmazon

Add kms decrypt argument for base64 encoded input

Freshover 3 years ago
Mar 14, 20260 views
Confidence Score78%
78%

Problem

The output for `aws kms encrypt` is a base64-encoded string. The input for `aws kms decrypt` is a binary string, which is not particularly bash-friendly. See #1100. It would be useful if there was an additional `--ciphertext-base64` argument that could take that same base64 blob from `encrypt` and decrypt it correctly.

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
High Confidence Fix
74% confidence100% success rate3 verificationsLast verified Mar 14, 2026

Solution: Add kms decrypt argument for base64 encoded input

Low Risk

I'm not blocked, but it is really non-obvious what's going wrong. We lost a bit of time when trying to validate that we'd encoded our data correctly. Seems like an easy win to be able to specify base64-encoded ciphertext.

74

Trust Score

3 verifications

100% success
  1. 1

    I'm not blocked, but it is really non-obvious what's going wrong. We lost a bit

    I'm not blocked, but it is really non-obvious what's going wrong. We lost a bit of time when trying to validate that we'd encoded our data correctly. Seems like an easy win to be able to specify base64-encoded ciphertext.

Validation

Resolved in aws/aws-cli GitHub issue #2063. Community reactions: 4 upvotes.

Verification Summary

Worked: 3
Partial: 1
Last verified Mar 14, 2026

Sign in to verify this fix

Environment

Submitted by

AC

Alex Chen

2450 rep

Tags

awsclicloudfeature-requestv2has-prcommunity