[JIRA] (JENKINS-60132) Add support for AWS parameter store as a backend for storing credentials

[chris+jenk...@chriskilding.com (JIRA)]

Title: Message Title

Chris Kilding updated an issue   Jenkins / JENKINS-60132 Add support for AWS parameter store as a backend for storing credentials Change By: Chris Kilding Particularly, storing *Feature* Allow Jenkins to look up credentials in AWS Parameter Store. (They will be stored as secure strings Secure String parameters can have a lower cost relative to secrets manager. [https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-paramstore-securestring.html] ).   *Benefits* - Storing credentials in Parameter Store can be cheaper than storing them  in Secrets Manager. *Pitfalls* - Secrets Manager may offer higher API rate limits or better QoS since it is a paid-for service. We would need to find out whether Parameter Store offers acceptable rate limits and performance for Jenkins to rely on. * Questions : * # - Does this belong in its own project/plugin or is there opportunity for code reuse as part of aws-secrets-manager-credentials-provider-plugin? # Is there opportunity to - Could we reuse the naming or storage conventions, such as tagging, that were defined when adding multiple credential support (JENKINS-58339)? # Any *Constraints* - Jenkins should be able to source credentials from both Secrets Manager and Parameter Store. (Using one should not rule out using the other comments? .) - If Jenkins encounters an error looking up secrets in one of the services, this should not impede lookups in the other. (An exception from a Secrets Manager API call should not break secret resolution in Parameter Store if PS is still functioning.) - Tag naming conventions should be shared in both PS and SM. (Eg a username tag should be called jenkins:credentials:username in PS, just like it is in SM today.) Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202985.1573481513000.7329.1574788380250%40Atlassian.JIRA.