Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add VPC endpoints as alternative to NAT gateway #283

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

Merged
merged 2 commits into from
May 25, 2021

Conversation

GoodMirek
Copy link
Contributor

Error messages in Lambda console indicate that it is possible to use AWS VPC Endpoints for LAmbda and STS services, instead of NAT gateway. It indeed works, but this alternative was not documented so far.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

GoodMirek and others added 2 commits May 24, 2021 21:42
Error messages in Lambda console indicate that it is possible to use AWS VPC Endpoints for LAmbda and STS services, instead of NAT gateway. It indeed works, but this alternative was not documented so far.
@devlinbd2 devlinbd2 merged commit 84b550b into awsdocs:main May 25, 2021
@devlinbd2
Copy link
Contributor

Thank you for the suggested improvement.

@GoodMirek GoodMirek deleted the patch-1 branch May 25, 2021 18:23
@GoodMirek
Copy link
Contributor Author

@devlinbd2 Any idea when the merged change will propagate to https://docs.aws.amazon.com/lambda/latest/dg/with-msk.html ?

@devlinbd2
Copy link
Contributor

@GoodMirek Unfortunately, it is a manual propagation from github to our source files. I have just done a build with the update in it, so it should show up on that web page in an hour or two.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants