Unable to set custom Teleport node names for EC2 instances auto-enrolled via SSM in Teleport Cloud

[spiffaz]

I am using Teleport Cloud with EC2 Auto Enrollment via SSM across multiple AWS accounts. I need to set custom node names using AWS tags instead of default EC2 hostnames. Currently, the only known method is manually changing each EC2 hostname, which is impractical at scale.

Environment:
Teleport Cloud (no direct access to teleport.yaml)
EC2 Auto Enrollment via SSM
50+ AWS Organization accounts

Request:
I need guidance on configuring Teleport to use a specific AWS tag as the node name for EC2 instances enrolled through SSM, or alternative solutions for custom node naming at scale.

[webvictim]

The TeleportHostname tag should override the displayed hostname: https://goteleport.com/docs/admin-guides/management/guides/ec2-tags/

[spiffaz]

It doesnt update the name after manually removing the nodename from the configuration.

Removing the nodename and restarting Teleport on the node also removes some auto-provisioned tags from AWS. See an example below

The tags eventually come back up. But it does not update the nodename.

These were provisioned using EC2 Auto Enrollment via SSM.

[spiffaz]

Hi @webvictim following up on this in case theres a new update

[webvictim]

Can you search the Teleport logs on this machine for the string "cloud tag" please, and share them if you find any?

sudo journalctl -u teleport | grep "cloud tag" should do it.

If the tag is being rejected for some reason, it will generate an error.

[spiffaz]

Hi @webvictim , reviewing the logs of instances provisioned via SSM, there is no result checking through the logs for "cloud tag". Please see below:

My Teleport version is - Teleport Enterprise v16.4.7 git:v16.4.7-0-g15dfef1 go1.22.9

[spiffaz]

Hi team, checking in on this