Hello Team! Still new to Atmos, so please excuse me if the question is basic. Having made a bunch of changes to our EKS addon placement, I'm hitting some issues executing

apply

using the official Atmos GitHub Actions:

plan files have differences

My workflow was straight forward - I made a PR with changes to EKS addon versions and configuration, which generated a matrix of successful plans across all my regions in

prod

. Then, I merged the PR, with

auto-apply

label on it. Still, the

apply

to my stacks fail - but it does not fail reliably. Some matrix jobs pass, and changes are applied, but others fail with this error. Something I considered was to delete the old planfiles from the S3 bucket manually and retry, but I wanted to check here if there's something I am missing. Component:

<http://github.com/cloudposse-terraform-components/aws-eks-cluster.git//src?ref=v1.535.0|github.com/cloudposse-terraform-components/aws-eks-cluster.git//src?ref=v1.535.0>

(found no related changes in the EKS module between mine and latest component versions).

Are you using self hosted GitHub runners?

Yes.

uri: "<http://github.com/cloudposse/terraform-aws-components.git//modules/philips-labs-github-runners?ref={{.Version}}|github.com/cloudposse/terraform-aws-components.git//modules/philips-labs-github-runners?ref={{.Version}}>"
    version: "1.520.0"

The most likely reason it's failing, without seeing more log output, since network related