This message was deleted.

This is my Github action yaml

jobs:
    dev:
        name: Deploy Staging Changes
        runs-on: self-hosted
        steps:
            - name: Checkout
              uses: actions/checkout@v4
            - name: Volta
              run: volta install pnpm
            - name: Setup Node
              uses: actions/setup-node@v3.5.0
              with:
                node-version: "20"
                cache: "pnpm"
            - name: Install dependencies
              run: pnpm install
            - name: Configure AWS Credentials
              uses: aws-actions/configure-aws-credentials@v2
              with:
                aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
                aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
                aws-region: ${{ env.AWS_REGION }}
            - name: Pulumi Update
              uses: pulumi/actions@v3
              with:
                command: up
                stack-name: staging
                comment-on-pr: true
                work-dir: ${{ env.WORKDIR }}
                upsert: true
              env:
                PULUMI_ACCESS_TOKEN: ${{ secrets.ACCESS_TOKEN }}

Have you checked the values in your deployment secrets? That error message is saying the problem is in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCES_KEY.

I have checked them yes, tested the values locally and then updated the secrets with the working values

I see this in the error log:

dial tcp: lookup sts.us-west-2.amazonaws.com: no such host

Any ideas why that might be there? Are you running on a firewalled local runner?

It is running on a self hosted runner so I'll check that that isn't blocking Pulumi

It's access to AWS that needs to be enabled. The problem was when trying to connect to amazonaws.com

The runner can access AWS ECR and CLI

Are you still getting the same error? Could it have been a temporary issue?

There's been a few people having the same timeout error for STS this week. Unfortunately, aws doesn't provide health status for the sts service 🙄

@little-cartoon-10569 still seeing it, I've run into a similar issue running pulumi locally when it was working yesterday

That's what

aws-actions/configure-aws-credentials

is for though. If you're setting the access and secret keys manually, then you don't need that action.

I've tried one and the other and without

aws-actions/configure-aws-credentials

I get a

Error: No valid credential sources found for AWS Provider.

and without setting the secret manually I get the above error... I'm looking into our AWS IAM config to see if something is stopping it there