Skip to content
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

Use EFS DNS name instead of Mount Target DNS name. Fix README.md #9

Merged
merged 6 commits into from
Sep 30, 2017

Conversation

aknysh
Copy link
Member

@aknysh aknysh commented Sep 30, 2017

What

  • Fixed README.md
  • Added tags and attributes to all modules
  • Used the EFS DNS name instead of the Mount Target DNS name

Why

  • 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 the EFS.

References

@aknysh aknysh added the enhancement New feature or request label Sep 30, 2017
@aknysh aknysh self-assigned this Sep 30, 2017
variables.tf Outdated

variable "region" {}
variable "region" {
type = "string"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be derived from the VPC

@aknysh aknysh requested a review from osterman September 30, 2017 03:46
@aknysh aknysh changed the title Use EFS DNS name instead of Mount Target DNS name. Fixed README.md Use EFS DNS name instead of Mount Target DNS name. Fix README.md Sep 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants