Aws-cli: getting a certificate in the correct format

Created on 6 Oct 2017 · 3Comments · Source: aws/aws-cli

Description

Right now I can get the certification like so aws iam get-server-certificate --server-certificate-name certificateName

would like to be able to grab the cert without having to use openssl to -text -noout

the work flow now I have is to format the query

aws iam get-server-certificate --server-certificate-name certificateName --query "ServerCertificate.CertificateBody" | awk 'gsub(/"/,"",s); {gsub(/\\n/,"\n")}1' > cert.crt

then use openssl x509 -in cert.cert -text -noout

automation-exempt feature-request

Source

kangman

Most helpful comment

Marking as a feature request. In the meantime, you can use --output text to remove the need for the awk command:

$ aws iam get-server-certificate \
        --server-certificate-name certificateName \
        --query ServerCertificate.CertificateBody \
        --output text | openssl x509 -text -noout

jamesls on 10 Oct 2017

👍3

All 3 comments

Marking as a feature request. In the meantime, you can use --output text to remove the need for the awk command:

$ aws iam get-server-certificate \
        --server-certificate-name certificateName \
        --query ServerCertificate.CertificateBody \
        --output text | openssl x509 -text -noout

jamesls on 10 Oct 2017

👍3

Good Morning!

We're closing this issue here on GitHub, as part of our migration to UserVoice for feature requests involving the AWS CLI.

This will let us get the most important features to you, by making it easier to search for and show support for the features you care the most about, without diluting the conversation with bug reports.

As a quick UserVoice primer (if not already familiar): after an idea is posted, people can vote on the ideas, and the product team will be responding directly to the most popular suggestions.

We’ve imported existing feature requests from GitHub - Search for this issue there!

And don't worry, this issue will still exist on GitHub for posterity's sake. As it’s a text-only import of the original post into UserVoice, we’ll still be keeping in mind the comments and discussion that already exist here on the GitHub issue.

GitHub will remain the channel for reporting bugs.

Once again, this issue can now be found by searching for the title on: https://aws.uservoice.com/forums/598381-aws-command-line-interface

-The AWS SDKs & Tools Team