Octopus: unable to retrieve AWS auth token on acquire package with ECR

TL;DR

Upgrade Octopus Server to 2024.4.3812 or any 2025.1+ release. A maintainer confirms the fix shipped in 2024.4.3812 and all 2025.1+ releases.

Steps

1. Upgrade Octopus Server to 2024.4.3812 or any 2025.1+ release. The failure happens at package acquisition time against the ECR feed, so no amount of credential rotation on the AWS side fixes it; it is a server-side bug. After upgrading, re-run the failed deployment and confirm the acquire-package step retrieves the token.

When to use

Use this skill when you run into "Octopus: unable to retrieve AWS auth token on acquire package with ECR".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 2024.4.3812. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: GitHub issue OctopusDeploy/Issues#9044 (closed): deployments with a package step fail with Unable to retrieve AWS Authorization token when an ECR feed is configured as an external feed. A maintainer confirms the fix shipped in 2024.4.3812 and all 2025.1+ releases.

Verified resolution: Upgrade Octopus Server to 2024.4.3812 or any 2025.1+ release. The failure happens at package acquisition time against the ECR feed, so no amount of credential rotation on the AWS side fixes it; it is a server-side bug. After upgrading, re-run the failed deployment and confirm the acquire-package step retrieves the token.

Source URL: https://github.com/OctopusDeploy/Issues/issues/9044