Skip to content

ci(aws): deploy blocked until the ci-cd-permissions policy is applied #1791

Closed

Description

@cristim

Problem

The platform AWS deploy has failed since 1cd4e8eb (#1090). Terraform Apply returns 403 UnauthorizedOperation on ec2:CreateNetworkInterface for module.networking.aws_network_interface.fck_nat. Failing runs: 42067955423, 42073138219 and 42074290067.

Cause

The grant is on main (terraform/environments/aws/ci-cd-permissions/policy_networking.tf:42, from #1090), but the deploy role's policies live in the human-applied bootstrap root terraform/environments/aws/ci-cd-permissions. That root hasn't been applied since #1090 merged, so the live cudly-deploy-networking policy lacks the action.

Fix (owner action, not CI)

Apply terraform/environments/aws/ci-cd-permissions from current main with IAM-write credentials.

Then re-run the failed dev deploy and close this issue, citing the green run.

Deploys are blocked until this is applied.

Activity

  1. added
    type/choreMaintenance / non-user-visible
    triagedItem has been triaged
    priority/p0Drop everything; same-day fix
    on Nov 5, 2026
  2. cristim commented on Nov 6, 2026

    @cristim
    MemberAuthor

    Applied the ci-cd-permissions root (2 added, 6 changed, 0 destroyed; ec2:CreateNetworkInterface now in cudly-deploy-networking). The dev deploy re-run 42225096772 succeeded (Build & Deploy, Test Deployment green).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority/p0Drop everything; same-day fixtriagedItem has been triagedtype/choreMaintenance / non-user-visibleurgency/nowDrop other things

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions