Skip to content
OutageDeck

Incident detail

AWS Deployment Failures for Cloud Customers

Resolved incidentMajor1 affected service

Timeline window

to

Get alerted the next time Octopus Deploy breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Octopus Deploy alerts work

Timeline

Incident updates

Every update Octopus Deploy posted, oldest to newest, exactly as it appeared on their official status page.

  1. 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=<REGION> for Bash

    $env:AWS_REGION = "<REGION_>" for Powershell

    E.g

    export AWS_REGION=ap-southeast-2

    $env:AWS_REGION = "ap-southeast-2"

    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

  2. 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=[REGION] for Bash

    $env:AWS_REGION = "[REGION]" for Powershell

    E.g

    export AWS_REGION=ap-southeast-2

    $env:AWS_REGION = "ap-southeast-2"

    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

  3. Resolved

    This incident has been resolved.

Keep exploring

More from Octopus Deploy

Neighboring incidents on Octopus Deploy's timeline and the rest of their record on OutageDeck.

← Older incident

Deployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”

Newer incident →

Dynamic Worker issues in West US 2

All Octopus Deploy incidentsOctopus Deploy live status