No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

locally it runs fine, and all the aws credentials are also correct in the git actions

does your cluster have a public API endpoint?

not public, its behind the aws load balancer

but I am providing the id and access tokens for it to connect to the aws account-- in the previous step in the github actions, I read from ECR and that works completely fine

```- name: Run pulumi up for stack
        uses: pulumi/actions@v3
        with:          
          command: up
          stack-name: layup/dev
          work-dir: ./pulumi-services-infra        env:
          PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
          #PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}
          APP_VERSION: ${{ steps.build-image.outputs.APP_VERSION}}
          #AWD_PROFILE: dev-admin
          AWS_ACCESS_KEY: ${{ secrets.AWS_ACCESS_KEY_ID_DEV_ADMIN }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY_DEV_ADMIN }}
          AWS_REGION: us-east-1```

if I add  `args: --skip-preview` it then completes as it doesn't try to connect to cluster, but I still wonder why