[#375] Allow cross-account AWS IAM role assumption into opt-in regions #376
Conversation
… opt-in regions Added authRegion drop-down list-box & variable to allow explicitly stating the region for authenticating with AWS IAM.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| return RegionUtils.getRegion(regionName); | ||
| } else { | ||
| return Region.getRegion(Regions.US_EAST_1); | ||
| public ListBoxModel doFillAuthRegionItems() { |
Check warning
Code scanning / Jenkins Security Scan
Stapler: Missing permission check Warning
| return RegionUtils.getRegion(regionName); | ||
| } else { | ||
| return Region.getRegion(Regions.US_EAST_1); | ||
| public ListBoxModel doFillAuthRegionItems() { |
Check warning
Code scanning / Jenkins Security Scan
Stapler: Missing POST/RequirePOST annotation Warning
| return options; | ||
| } | ||
|
|
||
| public ListBoxModel doFillRegionNameItems() { |
Check warning
Code scanning / Jenkins Security Scan
Stapler: Missing permission check Warning
| return options; | ||
| } | ||
|
|
||
| public ListBoxModel doFillRegionNameItems() { |
Check warning
Code scanning / Jenkins Security Scan
Stapler: Missing POST/RequirePOST annotation Warning
| @@ -507,9 +526,17 @@ | |||
| } | |||
| return options; | |||
| } | |||
|
|
|||
| public ListBoxModel doFillAuthRegionItems() { | |||
Check warning
Code scanning / Jenkins Security Scan
Stapler: Missing permission check Warning
| @@ -507,9 +526,17 @@ | |||
| } | |||
| return options; | |||
| } | |||
|
|
|||
| public ListBoxModel doFillAuthRegionItems() { | |||
Check warning
Code scanning / Jenkins Security Scan
Stapler: Missing POST/RequirePOST annotation Warning
|
@Stericson appreciate your input here. Many thanks! |
Added authRegion drop-down list-box & variable to allow explicitly stating the region for authenticating with AWS IAM. This will address Issue #375 by permitting authentication with a region that is opted-in in the source AWS account, while accessing ECS clusters in an opt-in region in the target account (which is not opted-in for the source account).
The solution was adding an
authRegionlist-box to choose the region used for IAM authentication, which is stored in anauthRegionvariable. This box works in exactly the same manner as theregionNamevariable box, but by separating them it is now possible to authenticate with AWS IAM in region A while using ECS clusters in region B.Testing done by:
Submitter checklist