feat(apigateway): private APIs #762
Merged
Conversation
This file contains 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
ml019
force-pushed
the
feat/api-gateway-private-api
branch
from
d84f965
to
0ed2bb3
Compare
ml019
force-pushed
the
feat/api-gateway-private-api
branch
from
0ed2bb3
to
8421c35
Compare
Add support for private APIs, with resource policy control based on vpc endpoints, following the pattern already used for IP address filtering on public APIs. Consumer VPC endpoints are obtained via inbound links from external services. Like IP address group support, if no limit is to be placed on where traffic to the API can originate, then an external service with a endpoint value of `_global` (or equivalent) must be provided.
ml019
force-pushed
the
feat/api-gateway-private-api
branch
from
8421c35
to
4d654c4
Compare
roleyfoley
approved these changes
Jul 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Intent of Change
Description
Add support for private APIs, with resource policy control based on vpc endpoints, following the pattern already used for IP address filtering on public APIs.
Consumer VPC endpoints are obtained via inbound links from external services.
Like IP address group support, if no limit is to be placed on where traffic to the API can originate, then an external service with a endpoint value of
_global(or equivalent) must be provided.Motivation and Context
How Has This Been Tested?
Related Changes
Prerequisite PRs:
Dependent PRs:
Consumer Actions: