Skip to content

Adds AWS auth docs#1104

Open
tr0njavolta wants to merge 4 commits intoupbound:mainfrom
tr0njavolta:aws-auth-updates
Open

Adds AWS auth docs#1104
tr0njavolta wants to merge 4 commits intoupbound:mainfrom
tr0njavolta:aws-auth-updates

Conversation

@tr0njavolta
Copy link
Member

Description

Type of change

  • Bug fix (typo, broken link, incorrect info)
  • Content update (new info, clarification, reorganization)
  • New content (new page, section, or guide)

Checklist

  • I ran make vale-file FILE=docs/path/to/file.md locally for files changed (or will fix Vale suggestions in review)
  • Links work and point to the right places
  • If this adds new content, I tested the examples/instructions

Additional notes

@vercel
Copy link

vercel bot commented Mar 4, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 12, 2026 2:24pm

Request Review

Copy link
Contributor

@jahabibi jahabibi left a comment

Choose a reason for hiding this comment

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

Overall looks great! A couple comments on the S3 bucket naming and it looks like we may have broken formatting in aws-access-keys

long-lived secrets in the cluster.

:::warning
When running on EKS, prefer [IRSA], [EKS Pod Identity], or [WebIdentity] over
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 maybe better to frame this as a security concern like:

On EKS, Upbound recommends using IRSA, EKS Pod Identity, or WebIdentity rather than static access keys to avoid the risk of long-standing static credentials.

It also looks like the EKS POD Identity link is broken here on this render: https://docs-gp29ya3u4-upboundio.vercel.app/manuals/packages/providers/aws-auth/aws-access-keys/

apiVersion: s3.aws.m.upbound.io/v1beta1
kind: Bucket
metadata:
name: my-crossplane-test-bucket
Copy link
Contributor

Choose a reason for hiding this comment

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

We may want to add a note that s3 buckets are globally unique so that they should customize the name of their bucket to avoid a conflict.

apiVersion: s3.aws.m.upbound.io/v1beta1
kind: Bucket
metadata:
name: my-crossplane-test-bucket
Copy link
Contributor

Choose a reason for hiding this comment

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

We may want to add a note that s3 buckets are globally unique so that they should customize the name of their bucket to avoid a conflict.

apiVersion: s3.aws.m.upbound.io/v1beta1
kind: Bucket
metadata:
name: my-crossplane-test-bucket
Copy link
Contributor

Choose a reason for hiding this comment

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

We may want to add a note that s3 buckets are globally unique so that they should customize the name of their bucket to avoid a conflict.

apiVersion: s3.aws.m.upbound.io/v1beta1
kind: Bucket
metadata:
name: my-crossplane-test-bucket
Copy link
Contributor

Choose a reason for hiding this comment

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

We may want to add a note that s3 buckets are globally unique so that they should customize the name of their bucket to avoid a conflict.

apiVersion: s3.aws.m.upbound.io/v1beta1
kind: Bucket
metadata:
name: my-s3-bucket
Copy link
Contributor

Choose a reason for hiding this comment

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

We may want to add a note that s3 buckets are globally unique so that they should customize the name of their bucket to avoid a conflict. Additionally this name diverges from other doc pages naming the bucket my-s3-bucket instead of my-crossplane-test-bucket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants