Skip to content

Conversation

@dghubble
Copy link
Member

  • Use EC2 resource-based hostnames instead of IP-based hostnames. The Amazon DNS server can resolve A and AAAA queries to IPv4 and IPv6 node addresses
  • For example, nodes used to be named like ip-10-11-12-13.us-east-1.compute.internal but going forward use the instance id i-0123456789abcdef.us-east-1.compute.internal
  • Tag controller node EBS volumes with a name based on the controller node name

* Use EC2 resource-based hostnames instead of IP-based hostnames. The Amazon
DNS server can resolve A and AAAA queries to IPv4 and IPv6 node addresses
* For example, nodes used to be named like `ip-10-11-12-13.us-east-1.compute.internal`
but going forward use the instance id `i-0123456789abcdef.us-east-1.compute.internal`
* Tag controller node EBS volumes with a name based on the controller node name
@dghubble dghubble merged commit 808b8a9 into main Aug 23, 2024
@dghubble dghubble deleted the resource-name branch August 23, 2024 04:02
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.

2 participants