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.

Sign up for GitHub

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

feat(nomad): add metadata_options to enable imdsv2 #297

Merged
merged 11 commits into from
Dec 1, 2023
Merged

feat(nomad): add metadata_options to enable imdsv2 #297

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
9703c74
add metadata_options
Tingweiftw Nov 24, 2023
dc73fdc
nomad server to use copied nomad-cluster
Tingweiftw Nov 29, 2023
d17fb04
add spot price
Tingweiftw Nov 29, 2023
e74e8bc
empty string for dedicated instance price
Tingweiftw Nov 29, 2023
f9212df
copy vault cluster source code
Tingweiftw Dec 1, 2023
43eb71f
inout for vault-cluster
Tingweiftw Dec 1, 2023
bf4fe37
add in vault-security-group
Tingweiftw Dec 1, 2023
d41d938
add in copied consul-cluster source code
Tingweiftw Dec 1, 2023
152a19a
fmt
Tingweiftw Dec 1, 2023
4c69524
add consul-client-sg-rules
Tingweiftw Dec 1, 2023
70d6b4d
remove unsupported tags
Tingweiftw Dec 1, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions modules/nomad-cluster/main.tf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,12 @@ resource "aws_launch_configuration" "launch_configuration" {
spot_price = var.spot_price
user_data = var.user_data

metadata_options {
http_endpoint = "enabled"
http_tokens = "required"
http_put_response_hop_limit = 3
Copy link
Contributor Author

Choose a reason for hiding this comment

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

based on: https://support.hashicorp.com/hc/en-us/articles/1500005343862-Required-Additional-Configuration-When-Using-IMDSv2

When enabling IMDSv2 on a Terraform Enterprise EC2 host, it is required to set the http-put-response-hop-limit option key to a value of 2 or greater. This meta-data option key
limits the number of hops that metadata requests can travel across a network, and will affect Terraform Enterprise’s ability to interact with S3 buckets. This is required due to the Terraform Enterprise application being a set of containers running on the EC2 instance, making the minimum hop limit 2. Please note the exact setting required is entirely dependent on the environment that Terraform Enterprise is deployed in. The maximum value for the http-put-response-hop-limit key is 64, but testing may be required to determine an exact value to set the key to.

}

iam_instance_profile = aws_iam_instance_profile.instance_profile.name
key_name = var.ssh_key_name

Expand Down
Loading