You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
awsUsed for AWS Related Issues.discoverIssues related to Teleport Discoverfeature-requestUsed for new features in Teleport, improvements to current should be #enhancements
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.
The content you are editing has changed. Please copy your edits and refresh the page.
awsUsed for AWS Related Issues.discoverIssues related to Teleport Discoverfeature-requestUsed for new features in Teleport, improvements to current should be #enhancements
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.
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 databasesUsers should see how many database agents deployed in ECS exist (name, teleport version, config, ...).
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.
Dashboard
Tasks
discover-ec2
task type #47062user_task_state
event proto #47380The text was updated successfully, but these errors were encountered: