Use EFS
DNS name instead of Mount Target DNS name. Fix README.md
#9
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.
What
README.md
tags
andattributes
to all modulesEFS
DNS name instead of the Mount Target DNS nameWhy
Fixed discrepancies and added more examples in
README.md
We can assign arbitrary tags to AWS resources
Using the EFS file system's DNS name is the simplest mounting option.
The file system DNS name will automatically resolve to the mount target’s IP address in the Availability Zone of the connecting Amazon EC2 instance, so instances from any AZ could access the
EFS
.AWS
will automatically resolve the DNS name to the IP address of the correct mount point depending on AZ/subnet the instance is requesting access to theEFS
.References