Uploaded image for project: 'Libcloud'
  1. Libcloud
  2. LIBCLOUD-108

Change EC2 Provider to support AWS separately so that AWS endpoints are not hard coded

    XMLWordPrintableJSON

    Details

      Description

      Currently, calling AWS endpoints requires that a provider be selected by region. Based on the provider chosen (for example Provider.EC2_US_WEST, EC2_US_EAST, etc), the internal code creates the endpoint. Since Amazon constructs the endpoints in a well know fashion:

      https://ec2.

      {region}

      .amazonaws.com

      It makes more sense to create a Provider for AWS that simply takes the region as a parameter and constructs the endpoint on the fly. That way, if libcloud is deployed as the base for other software, the entire suite does not have to be updated when Amazon adds a new region.

      Currently, I use Provider.EUCALYPTUS for AWS endpoints by constructing the the URL myself based on the region before calling libcloud to accomplish this.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rabinnh Richard Bross
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 1h
                1h
                Remaining:
                Remaining Estimate - 1h
                1h
                Logged:
                Time Spent - Not Specified
                Not Specified