This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
Update ec2-prefix-eni.md #232
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
Clarify that ENI prefixes can be used with any IPv6 addresses, not only private ones.
|
This change looks good to me. Thank you for your contribution. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Clarify that ENI prefixes can be used with any IPv6 addresses, not only private ones.
The current wording is ambiguous and can be read to imply that ENI prefixes are limited to private IPV6 addresses, which is incorrect.
For some public examples of when this line has caused real confusion see aws/containers-roadmap#835 (comment) and here.