Commit 80fe2ec
authored
fix(ci): revert ci-compat-e2e to AWS access keys (#23211)
## Summary
- Drop OIDC auth from `ci-compat-e2e` and run with
`AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` instead.
- The OIDC role
(`pipeline-exec-aztecprotocol-aztec-packages-heads-next`) has no
`ec2:RunInstances` policy attached, so spot requests time out and the
on-demand fallback fails with `UnauthorizedOperation`. The job has been
failing on every v4 nightly since #22930; `continue-on-error` for
`-nightly.` tags has masked it.
- Mirrors c3c1371 (#23167), which applied the same workaround to
`ci-release-publish` on this branch.
Example of the failure being patched:
https://github.com/AztecProtocol/aztec-packages/actions/runs/25737242295/job/75580441745
## Test plan
- [ ] CI3 on this PR runs to green (regular `ci` job is unaffected — it
already uses static keys).
- [ ] Apply the `ci-compat-e2e` label here to exercise the compat-e2e
job end-to-end and confirm the EC2 spot/on-demand request succeeds with
the static credentials.
🤖 Generated with [Claude Code](https://claude.com/claude-code)1 file changed
Lines changed: 2 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
298 | 298 | | |
299 | 299 | | |
300 | 300 | | |
301 | | - | |
302 | | - | |
303 | | - | |
304 | 301 | | |
305 | 302 | | |
306 | 303 | | |
| |||
320 | 317 | | |
321 | 318 | | |
322 | 319 | | |
323 | | - | |
324 | | - | |
325 | | - | |
326 | | - | |
327 | | - | |
328 | | - | |
329 | | - | |
330 | | - | |
331 | 320 | | |
332 | 321 | | |
333 | 322 | | |
| 323 | + | |
| 324 | + | |
334 | 325 | | |
335 | 326 | | |
336 | 327 | | |
| |||
0 commit comments