From 07d7ee0dc6b8a97a6926e2582cd1551434e83780 Mon Sep 17 00:00:00 2001 From: Grayson Pike Date: Sat, 18 Jan 2025 21:52:44 -0800 Subject: [PATCH] Fix link to AWS ECR PowerUser IAM documentation Signed-off-by: Grayson Pike --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5f113a5..c00061b 100644 --- a/README.md +++ b/README.md @@ -301,7 +301,7 @@ jobs: ### AWS Elastic Container Registry (ECR) -Use an IAM user with the ability to [push to ECR with `AmazonEC2ContainerRegistryPowerUser` managed policy for example](https://docs.aws.amazon.com/AmazonECR/latest/userguide/ecr_managed_policies.html#AmazonEC2ContainerRegistryPowerUser). +Use an IAM user with the ability to [push to ECR with `AmazonEC2ContainerRegistryPowerUser` managed policy for example](https://docs.aws.amazon.com/AmazonECR/latest/userguide/security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonEC2ContainerRegistryPowerUser). Download the access keys and save them as `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` [as secrets](https://docs.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) in your GitHub repo.