Does anyone use AWS_ENDPOINT_URL in their environment?

[stobrien89]

Hello everyone,

We're in the process of implementing #1239 as a cross-sdk effort. We will now be allowing customers to configure a per-service endpoint override (already made possible in the client constructor using the endpoint config option) using new configuration options: endpoint_url in the client constructor, AWS_ENDPOINT_URL_<SERVICE> as an env var and a new per-service configuration option/section in the config file, which will be as follows:

[default]
region = us-west-2
services = my-services

[services my-services]
s3 =
  endpoint_url = https://s3-endpoint-override.aws
elastic_beanstalk =
  endpoint_url = https://elastic-beanstalk-endpoint-override.aws

They will be resolved upon client instantiation in that order of precedence. Additionally, we will now be allowing customers to configure a global endpoint override (for all service clients) using the AWS_ENDPOINT_URL env var and the top-level endpoint_url config file option (located on the profile itself), which we will fall back to if we're unable to resolve any of the more specific configuration options.

Because the PHP SDK has historically not supported AWS_ENDPOINT_URL, which the CLI has supported for some time, I'm wondering if we have customers who are using both the CLI and the PHP SDK in their environments while using the AWS_ENDPOINT_URL env var or endpoint_url in their aws config file. I'd imagine this feature would break some customers if that is the case. Please comment and let us know if this is true of your environment.

Alongside this feature, we do have a way to opt out, in the form of the ignore_configured_endpoint_urls option, which is also configurable via the client, the environment via the AWS_IGNORE_CONFIGURED_ENDPOINT_URLS and the top-level ignore_configured_endpoint_urls config file option (located on the profile itself).

If anyone has any questions or comments, feel free to reply. More information about this feature is available here.