Resolved -
This incident has been resolved.
Apr 8, 04:11 UTC
Update -
We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments.
Our team is actively investigating and working to resolve the issue.
Workaround: If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue:
export AWS_REGION=[REGION] for Bash $env:AWS_REGION = "[REGION]" for Powershell
We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at support@octopus.com
Apr 1, 08:36 UTC
Investigating -
We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments.
Our team is actively investigating and working to resolve the issue.
Workaround: If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue:
export AWS_REGION= for Bash $env:AWS_REGION = "" for Powershell
We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at support@octopus.com
Apr 1, 08:06 UTC
Resolved -
We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email support@octopus.com if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.
Mar 30, 12:43 UTC