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: src/pages/docs/packaging-applications/package-repositories/guides/container-registries/amazon-ec2-container-services.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
layout: src/layouts/Default.astro
3
3
pubDate: 2023-01-01
4
-
modDate: 2025-03-28
4
+
modDate: 2025-05-08
5
5
title: AWS Elastic Container Registry (ECR)
6
6
description: How to add an AWS Elastic Container Registry as an Octopus feed
7
7
navOrder: 30
@@ -37,6 +37,14 @@ Create a new Octopus Feed (**Library ➜ External Feeds**) and select the `AWS E
37
37
38
38
Save and test your registry to ensure that the connection is authorized successfully.
39
39
40
+
## Using worker configured credentials
41
+
From Octopus Server `2025.2`, you can now use worker configured credentials by setting `Execute using the credentials configured on the worker` to `Yes` when creating your AWS ECR feed.
42
+
43
+
:::div{.warning}
44
+
If your AWS credentials are not set up on server, package search and package version resolution will not find any results. You can still enter your full package name and version for package acquisition on your worker.
45
+
:::
46
+
47
+
40
48
## Adding an AWS OpenID Connect ECR External feed
41
49
Octopus Server `2025.2` adds support for OpenID Connect to ECR feeds. To use OpenID Connect authentication you have to follow the [required minimum configuration](/docs/infrastructure/accounts/openid-connect#configuration). The configuration of
0 commit comments