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

Workload ID: Guide for AWS JWT OIDC Federation #47581

Merged
merged 14 commits into from
Oct 24, 2024

Conversation

strideynet
Copy link
Contributor

@strideynet strideynet commented Oct 15, 2024

Add a guide similar to the GCP one, with the steps needed to use Teleport Workload Identity to authenticate with AWS with JWT SVIDs.

@strideynet strideynet added no-changelog Indicates that a PR does not require a changelog entry backport/branch/v16 labels Oct 15, 2024
Copy link

🤖 Vercel preview here: https://docs-coer8t49i-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-pnfdqnbup-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-a5otiigax-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-olfl4op6y-goteleport.vercel.app/docs/ver/preview

@strideynet strideynet marked this pull request as ready for review October 16, 2024 09:36
Comment on lines +27 to +36
This implementation differs from using the Teleport Application Service to protect
AWS APIs in a few ways:

- Requests to AWS are not proxied through the Teleport Proxy Service, meaning
reduced latency but also less visibility, as these requests will not be
recorded in Teleport's audit log.
- Workload Identity works with any AWS client, including the command-line tool
but also their SDKs.
- Using the Teleport Application Service to access AWS does not work with Machine
ID and therefore cannot be used when a machine needs to authenticate with AWS.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would make sense to move this text to the Workload Identity introduction to reduce the length of the non-instructional text in this guide. It's also not specific to the setup shown in this guide. We can then move the "OIDC Federation vs Roles Anywhere" text into this section.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this is specific to the setup shown in this guide, since it helps you realise if you should actually be following the "authenticating to AWS services using Workload Identity with certificates" guide instead.

Copy link

🤖 Vercel preview here: https://docs-rh2au819o-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-iabc48w1r-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-cjzn6zlqc-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-gku7hx2gj-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-10ckcezey-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-1soq3tpgl-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-ic5ad1f73-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-1adeqxp9v-goteleport.vercel.app/docs/ver/preview

@strideynet strideynet requested a review from ptgott October 22, 2024 21:27
@strideynet strideynet added this pull request to the merge queue Oct 24, 2024
Merged via the queue into master with commit 55d0c76 Oct 24, 2024
40 checks passed
@strideynet strideynet deleted the strideynet/aws-oidc-jwt-workload-identity-docs branch October 24, 2024 16:35
@public-teleport-github-review-bot

@strideynet See the table below for backport results.

Branch Result
branch/v16 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/branch/v16 documentation no-changelog Indicates that a PR does not require a changelog entry size/md
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants