How to hide AWS secret key in AWS elastic beanstalk plugin of Jenkins?

[kanungo...@gmail.com]

I am unable to hide my AWS secret key in the AWS elastic beanstalk plugin which helps in automatic deployment in Elastic beanstalk............Please help....

Its urgent

Thanks

Amrita

[Aldrin Leal]

Hi Amrita,

Currently there's no way to do it. I'm evaluating other options (including using the credentials file and environment properties, as well as Instance Profiles), but the shortest path is: Simply use an IAM Key with constrained roles. Likely: s3:* and elasticbeanstalk;*

Thank you

--
-- Aldrin Leal, <ald...@leal.eng.br> / http://about.me/aldrinleal

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b868a33f-c668-4c29-9dc7-1d3ad367bdff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter Lai]

can you not treat it like a password and get it injected. 

Set a password called aws_key and in the key section "$aws_key"

Jenkins will then mask it for you. 

[Amrita Kanungo]

Thank you..But I am write now using AWS Elastic Beanstalk Publisher Plugin in which I am declaring the credentials globally and in the job level its hidden.

Thank you all for your answers..

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/LECdqIGglyI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8c0dc646-6d89-4329-8dac-fcdfce719edc%40googlegroups.com.

[Amrita Kanungo]

Hii...Right now another issue am facing...In our pom.xml the version keeps on changing for each war. We are actually increasing the pom version so our war is also being generated by abc-0.1.16-SNAPSHOT.war. And this number keeps on increasing. So how to declare the path in the AWS Deployment plugin, in the root object(file/directory) value. I have to give the exact name else its not taking target/abc-.*-war.

Can you please help me in this..