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

Document AWS cross-account EKS discovery #28834

Closed
6 tasks
GavinFrazar opened this issue Jul 7, 2023 · 1 comment
Closed
6 tasks

Document AWS cross-account EKS discovery #28834

GavinFrazar opened this issue Jul 7, 2023 · 1 comment

Comments

@GavinFrazar
Copy link
Contributor

Applies To

https://goteleport.com/docs/reference/config/
https://goteleport.com/docs/kubernetes-access/discovery/aws/
https://goteleport.com/docs/kubernetes-access/register-clusters/dynamic-registration/

Details

Config file reference updates

  • Document the discovery_service.aws fields assume_role_arn and external_id in config file reference.
  • Document aws field in kubernetes_service.resources config reference.

Create a guide for configuring the discovery service for cross-account AWS discovery.

  • Explain how to use teleport-kube-agent chart value teleportConfig to provide custom config with discovery_service
  • Explain how to setup IAM permissions like we do in https://goteleport.com/docs/database-access/guides/aws-cross-account/ (consider merging these into one guide?)
  • Explain how to setup the discovery service to assume an AWS role.
  • Explain how to setup the kubernetes_service to assume an AWS role for the dynamic resources it matches.

How will we know this is resolved?

A user can follow the guide to setup cross-account EKS discovery.

Related Issues

Related, we need to update docs in general to use discovery_service, which includes the current AWS cross-account db access guide and config file reference for discovery_service

@tigrato
Copy link
Contributor

tigrato commented Aug 28, 2024

Closed as complete by #42107

@tigrato tigrato closed this as completed Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants