[JIRA] (JENKINS-59670) Support retrieval of secrets from multiple AWS accounts

chris+jenkins@chriskilding.com (JIRA)

unread,

Oct 4, 2019, 4:29:03 PM10/4/19

to jenkinsc...@googlegroups.com

Chris Kilding created an issue

Jenkins /

JENKINS-59670

Support retrieval of secrets from multiple AWS accounts

Issue Type:	Improvement
Assignee:	Chris Kilding
Components:	aws-secrets-manager-credentials-provider-plugin
Created:	2019-10-04 20:28
Priority:	Minor
Reporter:	Chris Kilding

The plugin should be able to retrieve secrets from multiple AWS accounts at the same time, and merge the results into one combined list of credentials.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

chris+jenkins@chriskilding.com (JIRA)

unread,

Feb 6, 2020, 12:50:02 PM2/6/20

to jenkinsc...@googlegroups.com

Chris Kilding updated an issue

Jenkins /

JENKINS-59670

Support retrieval of secrets from multiple AWS accounts

Change By:	Chris Kilding

The plugin should be able to retrieve secrets from multiple AWS accounts at the same time, and merge the results into one combined list of credentials.

h2. Use case: Separate AWS accounts for deployment environments

- I have a Jenkins in my environment-independent tools account.
- I have dev secrets in my dev account.
- I have production secrets in my production account.
- And I want Jenkins to access secrets in the dev and production accounts.

Add Comment

chris+jenkins@chriskilding.com (JIRA)

unread,

Feb 6, 2020, 12:52:03 PM2/6/20

to jenkinsc...@googlegroups.com

Chris Kilding updated an issue

Jenkins /

JENKINS-59670

Support retrieval of secrets from multiple AWS accounts

Change By:	Chris Kilding

The plugin should be able to retrieve secrets from multiple AWS accounts at the same time, and merge the results into one combined list of credentials.

h2. Use case: Separate AWS accounts for deployment environments

- I have a Jenkins in my environment-independent tools account.
- I have dev secrets in my dev account.
- I have production secrets in my production account.
- And I want Jenkins to access secrets in the dev and production accounts.

(I may also want to combine this with optional access control rules from JEP-225, to ensure that only the relevant jobs can see an environment's secrets. But that is another story.)