Skip to content

Health check the AWS OIDC Integration before saving it #45703

Open

Description

What would you like Teleport to do?
When creating a new AWS OIDC Integration, if something is not correctly set up, the user must be warned about it.

What problem does this solve?
If the integration is not correctly set up, users are only aware of it much later, when using a specific feature.
Eg, when the cluster is not publicly accessible, the user sets up the integration and only finds out that it is not working when they try to use any feature that depends on it (eg, auto-enroll ec2 instances)

If a workaround exists, please include it.

Tasks

  1. backport/branch/v16 no-changelog size/md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

awsUsed for AWS Related Issues.discoverIssues related to Teleport Discoverfeature-requestUsed for new features in Teleport, improvements to current should be #enhancements

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions