chore(batch): init base EC2 class for ECS and EKS

[phuhung273]

Issue # (if applicable)

Close #35859

Reason for this change

• Keep codebase clean
• Prevent the case when adding a new feature to ECS but forgot to do the same for EKS
• Streamline future change, eg: (aws-batch): AWS Batch Compute Environment For AL2023 #35839
• A foundation to also reduce duplication for defaultInstanceClasses, useOptimalInstanceClasses, allocationStrategy, spotBidPercentage, instanceRole, launchTemplate, minvCpus, placementGroup and their related functions. I don't want to submit a huge refactor PR directly.

Description of changes

Init base EC2 class for ECS and EKS, start with only minimal things:

• property instanceTypes
• property instanceClasses
• method addInstanceType
• method addInstanceClass

Description of how you validated changes

Unit + Integ

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[abidhasan-aws]

Hi @phuhung273 ,
Thanks for the contribution.

I just have a small nit comment.

[abidhasan-aws]

I think the this should be instance classes instead of instance types

[phuhung273]

Thanks for your review. I've corrected this comment

Pull request has been modified.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-07 15:23 UTC · Rule: default-squash
• 🚫 Left the queue — 2026-04-07 15:23 UTC · at 64dd2ceacf0fb0a1e90c0b9520dc26b6f439f175

This pull request spent 7 seconds in the queue, with no time running CI.

Reason

The pull request can't be updated

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/pr-linter.yml without workflows permission

Hint

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

Pull request has been modified.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-08 07:27 UTC · Rule: default-squash
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-04-08 07:27 UTC · at 9b54dccc30bbdc0d1aeee86b6e0d6aa882f58946

This pull request spent 11 seconds in the queue, including 1 second running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore(batch): init base EC2 class for ECS and EKS #35868
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • chore(batch): init base EC2 class for ECS and EKS #35868
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.