Apr 10, 2025 · Apr 10, 2025 · Apr 10, 2025
diff --git a/_docs/administration/account-user-management/service-accounts.md b/_docs/administration/account-user-management/service-accounts.md
 | **Status**               | Indicates if the service account is currently active (**Enabled**) or inactive (**Disabled**). You may want to disable a service account to invalidate its API keys without having to remove the service account, and simply reenable when needed. |
 | **Actions**               | The options available to manage the service account through its context menu: {::nomarkdown}<ul><li><b>Edit</b>: Modify the settings of the service account, including adding/removing teams, enabling/disabling admin role.</li><li><b>Delete</b>: Delete the service account, including all the API keys defined for the account. This means that actions through the Codefresh API or CLI that require these keys will fail.</li></ul>{:/} |

 {% if page.collection != site.gitops_collection %}
 ## Authenticating to Amazon ECR with service account

 Authenticate to Amazon ECR registries with credentials from the service account instead of the Access Key ID and Secret Access Key.
 This allows pipelines to seamlessly authenticate to Amazon ECR via service account credentials, enhancing security and simplifying access management.

 There are two requirements:
 1. Set the option to authenticate via service accounts at the account level for pipelines. See [Advanced options for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#advanced-options-for-pipelines).
 1. Configure Amazon ECR integration to use service account credentials. See [Amazon ECR Container Registry pipeline integration]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/).
 {% endif %}

 ## Related articles
 {% if page.collection != site.gitops_collection %}
Original file line number	Diff line number	Diff line change
Expand Up		@@ -100,16 +100,6 @@ max-width="90%"
		\| Status \| Indicates if the service account is currently active (Enabled) or inactive (Disabled). You may want to disable a service account to invalidate its API keys without having to remove the service account, and simply reenable when needed. \|
		\| Actions \| The options available to manage the service account through its context menu: {::nomarkdown}<ul><li><b>Edit</b>: Modify the settings of the service account, including adding/removing teams, enabling/disabling admin role.</li><li><b>Delete</b>: Delete the service account, including all the API keys defined for the account. This means that actions through the Codefresh API or CLI that require these keys will fail.</li></ul>{:/} \|

		{% if page.collection != site.gitops_collection %}
		## Authenticating to Amazon ECR with service account

		Authenticate to Amazon ECR registries with credentials from the service account instead of the Access Key ID and Secret Access Key.
		This allows pipelines to seamlessly authenticate to Amazon ECR via service account credentials, enhancing security and simplifying access management.

		There are two requirements:
		1. Set the option to authenticate via service accounts at the account level for pipelines. See [Advanced options for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#advanced-options-for-pipelines).
		1. Configure Amazon ECR integration to use service account credentials. See [Amazon ECR Container Registry pipeline integration]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/).
		{% endif %}

		## Related articles
		{% if page.collection != site.gitops_collection %}
Expand Down