NEW Serverless Pattern - Invoke a Private Custom Domain Name cross account #2541
Conversation
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
parikhudit
reviewed
Jan 2, 2025
parikhudit
reviewed
Jan 2, 2025
parikhudit
reviewed
Jan 2, 2025
added 7 commits
January 2, 2025 09:39
luketr03
force-pushed
the
luketr03-private-custom-domain-name-cross-account
branch
from
accec1a to
926084e
Compare
parikhudit
added
Patterns Guardian approved
and removed
requested-changes
missing-example-pattern-file
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Issue #, if available: #2542
Description of changes:
New pattern that enables an AWS Account to send requests to a Private API Gateway via a Private Custom Domain Name hosted in a different AWS Account.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.