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.

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

AWS OIDC Integration Dashboard #41909

Open
18 of 25 tasks
marcoandredinis opened this issue May 22, 2024 · 0 comments
Open
18 of 25 tasks

AWS OIDC Integration Dashboard #41909

marcoandredinis opened this issue May 22, 2024 · 0 comments
Assignees
Labels
aws Used for AWS Related Issues. discover Issues related to Teleport Discover feature-request Used for new features in Teleport, improvements to current should be #enhancements

Comments

@marcoandredinis
Copy link
Contributor

marcoandredinis commented May 22, 2024

We should give the user the visibility and management tools, so they can understand the current status and fix/change any configuration related to the Integration.
The following components must be part of this dashboard.

AWS App Access

Whether the AWS App Access is enabled for the integration.
Users should be able to enable or disable the AWS App.
Enabling it will redirect them to the Discover flow.

RDS, EC2 and EKS

RDS databases, EC2 instances and EKS clusters can be enrolled and accessed from teleport.

Enrollment is done by creating a new DiscoveryConfig associated with an existing DiscoveryService's DiscoveryGroup (self-hosted users must manage their own DiscoveryService).
The dashboard must show the DiscoveryConfig rules created for each type of resource.

For RDS, the flow deploys a Database Service in user's AWS Account using Amazon ECS.
Users should see how many database agents deployed in ECS exist (name, teleport version, config, ...).

Listing ECS Services requires a region. In order to get the region we'll use two sources: a) regions in use by the DiscoveryConfig rules; b) regions in use by the onboarded RDS databases

Tasks

Tasks will allow users to see which resources failed to enroll.
When opening the Integration, users should see how many tasks exists and possibly open the Tasks view.

Final design (internal only)
https://www.figma.com/design/v6GunK50D2VC7w7I2FBDNf/Access-(Management)?node-id=4143-2783&node-type=canvas&t=r1DInS5qFyYyH1vw-0

Dashboard

  1. backport/branch/v15 backport/branch/v16 no-changelog size/sm
  2. backport/branch/v16 discovery no-changelog size/sm
  3. backport/branch/v16 no-changelog size/sm
  4. no-changelog size/sm
  5. backport/branch/v16 discover no-changelog size/sm
  6. backport/branch/v16 discover discovery no-changelog size/md
  7. backport/branch/v16 backport/branch/v17 discover no-changelog size/sm
  8. backport/branch/v16 backport/branch/v17 database-access discover discovery no-changelog size/md
  9. backport/branch/v16 backport/branch/v17 discover no-changelog
  10. backport/branch/v16 backport/branch/v17 no-changelog

Tasks

  1. backport/branch/v16 no-changelog size/md
  2. backport/branch/v16 no-changelog size/xl tctl
  3. backport/branch/v16 no-changelog size/md
  4. backport/branch/v16 no-changelog size/sm
  5. backport/branch/v16 no-changelog size/md
  6. backport/branch/v16 no-changelog size/md
  7. backport/branch/v16 no-changelog size/md
  8. backport/branch/v16 discovery no-changelog size/md
  9. audit-log backport/branch/v16 no-changelog size/md ui
  10. backport/branch/v16 discovery no-changelog size/sm
  11. backport/branch/v16 discovery no-changelog size/md
  12. backport/branch/v16 backport/branch/v17 do-not-merge no-changelog size/md
  13. backport/branch/v16 backport/branch/v17 discover discovery do-not-merge no-changelog size/md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws Used for AWS Related Issues. discover Issues related to Teleport Discover feature-request Used for new features in Teleport, improvements to current should be #enhancements
Projects
None yet
Development

No branches or pull requests

1 participant