Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): swap to new aws account for rke/eks tests #1339

Merged
merged 4 commits into from
Mar 5, 2025

Conversation

joelmccoy
Copy link
Contributor

@joelmccoy joelmccoy commented Mar 5, 2025

Description

Swaps over the eks/rke2 tests to the new AWS commercial account. Points the CI to use the new vpc, state bucket, state lock table provisioned in that account. The base infra is defined in this repo and managed with our spacelift integration.

Additionally for the rke2 workflow, the terraform data filter needs to provide the new owning aws account id (since the AMIs are published in a different account than which the CI runs in). The following secrets will need to be updated/created before this will work (I can provide these out of band and then rerun the test CI):

  • PERMISSIONS_BOUNDARY_ARN
  • PERMISSIONS_BOUNDARY_NAME
  • AWS_COMMERCIAL_ROLE_TO_ASSUME
  • UDS_IMAGES_AWS_ACCOUNT_ID

Related Issue

Fixes #1287

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Other (security config, docs update, etc)

Steps to Validate

  • N/A

Checklist before merging

@joelmccoy joelmccoy requested a review from a team as a code owner March 5, 2025 20:36
@joelmccoy joelmccoy changed the title chore(ci): swap to new aws accounts for rke/eks tests chore(ci): swap to new aws account for rke/eks tests Mar 5, 2025
@mjnagel mjnagel merged commit 3b6fb50 into main Mar 5, 2025
20 checks passed
@mjnagel mjnagel deleted the use-new-aws-accounts branch March 5, 2025 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate AWS CI to new AWS account
2 participants