EDU-159 Expand AWS ECR Public Registry documentation in Platform credentials#1614
Merged
Merged
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
justinegeffen
requested review from
christopher-hakkaart,
gavinelder and
munishchouhan
and removed request for
christopher-hakkaart
June 25, 2026 21:04
justinegeffen
added
1. Editor review
christopher-hakkaart
approved these changes
Jun 29, 2026
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
Member
There was a problem hiding this comment.
Reads really well.
munishchouhan
approved these changes
Jun 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands the AWS ECR credentials pages to properly document ECR Public Registry usage with Wave. Applied across all four affected doc surfaces.
The previous docs had a single-sentence note about
public.ecr.awsthat omitted the key information users need to successfully authenticate.Files changed
platform-cloud/docs/credentials/aws_registry_credentials.mdplatform-enterprise_docs/credentials/aws_registry_credentials.mdplatform-enterprise_versioned_docs/version-25.3/credentials/aws_registry_credentials.mdplatform-enterprise_versioned_docs/version-26.1/credentials/aws_registry_credentials.mdAll four pages are updated to:
sts:GetServiceBearerToken— the permission absent fromAmazonElasticContainerRegistryPublicReadOnlythat causes silent auth failures.public.ecr.awsas the registry server value.Related
The companion PR in
seqeralabs/waveadds the same public ECR guidance to the Wave authentication feature page (including self-hosted Wave config):→ seqeralabs/wave#1066
Motivation
Support ticket 5013 showed users were not authenticating to ECR Public because:
public.ecr.awsas the registry serversts:GetServiceBearerTokenwas not documented as a required separate permissionKey: EDU-159
Co-authored by Claude agent for Jira.