This task is simple enough in theory, but artifact-manager-s3 and pipeline-cloudwatch-logs depend on the API provided by this plugin and might need to be updated in lockstep, depending on whether they use the changed API.

Another minor wrinkle is that this plugin relies on the v1 SDK to fill in the descriptions of the various regions, but that information is not available in the v2 SDK (just the IDs of the regions). The descriptions are available through a call to the EC2 DescribeRegions API, but this needs a valid token. I suppose we could attempt to get the descriptions and fall back to the IDs if we don't have read access to EC2. Another option is simply to dispense with the descriptions in the UI: this is simply a list box and the IDs would probably suffice here, even if the UI doesn't look as good.

https://github.com/jenkinsci/aws-global-configuration-plugin/pull/93 provides an (untested) sketch of what this might look like.

Updated https://github.com/jenkinsci/aws-global-configuration-plugin/pull/93 to include a compatibility layer for dependent plugins. At this point the next step is to test manually on a real AWS account, focusing on the areas mentioned in https://github.com/jenkinsci/aws-global-configuration-plugin/pull/93 (including getting session credentials from an instance profile).

Fixed in jenkinsci/aws-global-configuration-plugin#93. Released in 139.v0b_c2603876b_c.