Add Edge service as central API entry point; release v 0.11.0#2250
Merged
Add Edge service as central API entry point; release v 0.11.0#2250
Conversation
This was referenced Apr 4, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds an edge service that acts as central entry point for all API invocations. The edge service listens on a configurable port (
EDGE_PORT,4566by default) and can be used to access any of the underlying LocalStack APIs.This is a breaking change - , although backwards compatibility has been preserved for now. Users should start reconfiguring their client SDKs to use the edge service endpoint URL, instead of the API-specific endpoints.
In a future version of LocalStack, we will remove the service-specific ports and route all API requests through the single edge endpoint only.
Addresses #2173, #151