Should Go driver honor AWS_STS_REGIONAL_ENDPOINTS/AWS_REGION in AssumeRoleProvider.RetrieveWithContext

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Won't Do
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Go Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      The AssumeRoleProvider in internal/credproviders constructs it’s STS URI with a hard-coded http://sts.amazqon.com endpoint. This ignores the standard AWS SDK environment variables, so users cannot force the provider to call the regional STS endpoint.

      Should we modifying AssumeRoleProvider.RetrieveWithContext so that before formatting stsURI it checks

      1. If AWS_STS_REGIONAL_ENDPOIN=regional and
      2. If AWS_REGION is set

      Then replace the host in the request URL to use the specific region?

      It's unlikely other drivers make this check and it adds complexity to our current "bare bones" implementation. However, it's super confusing. This ticket could potentially be closed by GODRIVER-3567 which will offer a pure-AWS SDK solution to this exact problem.

            Assignee:
            Unassigned
            Reporter:
            Preston Vasquez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: