Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Configure Services' Endpoint URLs via Environment Variables #3236

Closed
mikicho opened this issue May 1, 2020 · 5 comments
Closed
Labels
feature-request A feature should be added or improved.

Comments

@mikicho
Copy link

mikicho commented May 1, 2020

Is your feature request related to a problem? Please describe.
I've been looking at the documentation about environment variables and see that you are able to configure credentials, regions, and profiles using environment variables, but I do not see a way to configure the endpoint URL option to point to our internal proxy.

Describe the solution you'd like
My suggestion is to configure the endpoint URL if either the AWS__ENDPOINT or AWS_ENDPOINT (in that order of priority) environment variables are available.

Describe alternatives you've considered
Use environment variable in code:

  new AWS.Lambda({ endpoint: process.env.AWS_URL })

Additional context
I need it for localstack :)

@mikicho mikicho added the feature-request A feature should be added or improved. label May 1, 2020
@codyhazelwood
Copy link

+1

This would be very helpful for pointing at MinIO on our local dev machines (so we can still dev on an airplane, bad connection, etc), but then easily default back to S3 in production.

If implemented, it would be helpful to be per-service (like AWS_S3_ENDPOINT). For example - we might want Lambda to point at local SAM, but S3 to point at local MinIO.

There's an easy work around here, but it would still be nice to have.

@github-actions
Copy link

github-actions bot commented Nov 7, 2021

Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.

@github-actions github-actions bot added closing-soon This issue will automatically close in 4 days unless further comments are made. closed-for-staleness and removed closing-soon This issue will automatically close in 4 days unless further comments are made. labels Nov 7, 2021
@kdaily kdaily reopened this Nov 17, 2021
@kellertk
Copy link
Contributor

Thank you for posting your feedback here, and our apologies that we’ve been thinking this over for a long time without much forward motion. There are similar requests to implement this feature in a few of the AWS SDKs and the AWS CLI, so in order to coordinate those teams - and hopefully make the discussions a little easier to follow - we’ve created a new issue in aws/aws-sdk here: aws/aws-sdk#229

@aws aws locked and limited conversation to collaborators Apr 26, 2022
@tim-finnigan
Copy link

Hi all,

We recently added a pull request (aws/aws-sdk#230) that contains a proposal based on community comments and suggestions and our own discussions. This document proposes to extend the options for configuring the endpoint to allow users to provide an endpoint URL independently for each AWS service via an environment variable or a profile subsection in the shared configuration file.

You can read the proposal here.

For more information on how to give feedback, please see this comment on the aws/aws-sdk repository:

aws/aws-sdk#229 (comment)

Thanks!

@kellertk
Copy link
Contributor

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

5 participants