Allow more than one cloud definition per region, to support multiple accounts using the same region.

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Currently "... At most one EC2 cloud can be defined per region, as the region serves as the identifier for the cloud.". This restriction prevents one from defining multiple slaves spread across EC2 accounts, such as development and production for example, when both accounts are deploying instances in the same region.

      The API key is what identifies the cloud account on the EC2 side, so I'm curious why this restriction exists and am hopeful it can be removed? Thanks!

            Assignee:
            Francis Upton
            Reporter:
            Matt Jamison
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: