Skip to content
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

getting a certificate in the correct format #2876

Open
kangman opened this issue Oct 6, 2017 · 3 comments
Open

getting a certificate in the correct format #2876

kangman opened this issue Oct 6, 2017 · 3 comments
Labels
automation-exempt Issue will not be subject to stale-bot feature-request A feature should be added or improved. iam p3 This is a minor priority issue

Comments

@kangman
Copy link

kangman commented Oct 6, 2017

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

@jamesls
Copy link
Member

jamesls commented Oct 10, 2017

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 jamesls added the feature-request A feature should be added or improved. label Oct 10, 2017
@ASayre
Copy link
Contributor

ASayre commented Feb 6, 2018

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

@ASayre ASayre closed this as completed Feb 6, 2018
@jamesls jamesls reopened this Apr 6, 2018
@jamesls
Copy link
Member

jamesls commented Apr 6, 2018

Based on community feedback, we have decided to return feature requests to GitHub issues.

@kdaily kdaily added the automation-exempt Issue will not be subject to stale-bot label Sep 17, 2020
@tim-finnigan tim-finnigan added the p3 This is a minor priority issue label Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation-exempt Issue will not be subject to stale-bot feature-request A feature should be added or improved. iam p3 This is a minor priority issue
Projects
None yet
Development

No branches or pull requests

5 participants