You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/gitops-integrations/container-registries/amazon-ecr.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,6 @@ toc: true
9
9
Codefresh has native support to interact with Amazon ECR (Elastic Container Registry), and push, pull, and deploy images.
10
10
For information on adding an Amazon ECR integration for GitOps in Codefresh, see[Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/).
11
11
12
-
>Amazon ECR integration is supported only for Hybrid GitOps.
13
12
14
13
##GitOps Amazon ECR integration options
15
14
@@ -20,6 +19,9 @@ You can set up the integration with Amazon ECR in one of two modes:
20
19
Access keys consist of an access key ID and a secret access key, which are used to authenticate and authorize API requests to AWS services for a specific user.
21
20
Unlike IAM roles, access keys are long-term credentials, and don't have a default expiration date.
22
21
22
+
>Amazon ECR integration with IAM Role is supported only for Hybrid GitOps. Access Key integration is supported for both Hosted and Hybrid GitOps.
23
+
24
+
23
25
Both modes use AWS Identity and Access Management (IAM) to create the integration with Amazon ECR.
24
26
For detailed information, see[How Amazon Elastic Container Registry Works with IAM](https://docs.aws.amazon.com/AmazonECR/latest/userguide/security_iam_service-with-iam.html){:target="\_blank"} and the[AWS security blog](https://aws.amazon.com/blogs/security/how-to-use-trust-policies-with-iam-roles/){:target="\_blank"}.