feat(apigateway): private APIs #2115
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
roleyfoley
requested changes
Jul 3, 2023
ml019
force-pushed
the
feat/api-gateway-private-api
branch
3 times, most recently
from
d503c8a
to
c54bbca
Compare
roleyfoley
approved these changes
Jul 3, 2023
Add the option of private APIs. For these APIS, traffic filtering is done on the basis of VPC endpoints rather than IP addresses. The VPC endpoints are assumed to be configured via inbound links to external services, which should provide a VPC_ENDPOINTS attribute containing a command separated list of vpc endpoint names. Adjust the available values for the authorisation model to support either IPs or VPC Endpoints.
roleyfoley
force-pushed
the
feat/api-gateway-private-api
branch
from
c54bbca
to
75dcdd1
Compare
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 the option of private APIs. For these APIS, traffic filtering is done on the basis of VPC endpoints rather than IP addresses. The VPC endpoints are assumed to be configured via inbound links to external services, which should provide a VPC_ENDPOINTS attribute containing a command separated list of vpc endpoint names.
Adjust the available values for the authorisation model to support either IPs or VPC Endpoints.
Motivation and Context
How Has This Been Tested?
Local template generation
Related Changes
Prerequisite PRs:
Dependent PRs:
Consumer Actions: