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

Add support for regional VPC Endpoints in STS and SQS api calls #144

Closed
dlpzx opened this issue Sep 23, 2022 · 0 comments
Closed

Add support for regional VPC Endpoints in STS and SQS api calls #144

dlpzx opened this issue Sep 23, 2022 · 0 comments
Assignees
Labels
type: enhancement Feature enhacement

Comments

@dlpzx
Copy link
Contributor

dlpzx commented Sep 23, 2022

Is your idea related to a problem? Please describe.
This enhacement is only relevant if VPC endpoints are created outside of data.all and those endpoints are regional and we are using the VPC facing architecture. For some of these VPC endpoints (SQS and STS) we need to explictly specify the endpoint url for the api calls to the service. Otherwise it tries to reach the global endpoint which is not reachable, resulting in failure of the creation of environments and other functionalities that use STS or SQS in the backend.

This issue is described here: boto/boto3#1859

Describe the solution you'd like
data.all to route these api calls independently from the type of endpoints used

@dlpzx dlpzx added the type: enhancement Feature enhacement label Sep 23, 2022
@dlpzx dlpzx self-assigned this Sep 23, 2022
@dlpzx dlpzx closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Feature enhacement
Projects
None yet
Development

No branches or pull requests

1 participant