Expected behavior:

The AWS integration name is mapped appropriately into app access with a working dns name.

Current behavior:

The name of the app is set as the <integration name>.<proxydomain>. So if the AWS integration name is aws.env and the proxy domain in teleport.example.com then the domain beccomes aws.env.teleport.example.com. In the case of Teleport Cloud that domain is not included in the Let's Encrypt cert and typically not for self-hosted.

Bug details:

• Teleport version: 15.4.9
• Recreation steps
  1. Create a AWS integration name that includes .
  2. Create a AWS Console/CLI using that integration name with enrolling resource in discover