feat(ec2): instance support passing IAM instance profile

[phuhung273]

Issue # (if applicable)

Closes #8348

Reason for this change

• Use only 1 IAM instance profile for multiple instances
• Passing role create too many instance profile

Description of changes

• ec2.Instance support instanceProfile param

Description of how you validated changes

• unit test
• integ test

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

[GavinZZ]

Thank you! I can't believe we don't support instance profile until now.

[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).

[GavinZZ]

@mergify update

[mergify]

update

❌ Mergify doesn't have permission to update

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/codecov.yml without workflows permission

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).

[phuhung273]

@GavinZZ thanks for your review. I dont know why CodeQL stuck at this snippet now

part = `"${part.replace(/"/g, '\\"')}"`;

Can confirm this line exists in other generated integ test snapshot.

[phuhung273]

Found related PRs/issues

• chore: upgrade sdkv3 to the newest version used by lambda distributions #31658
• GHAS/CodeQL reporting missing input sanitization aws-sdk-js-v3#6623
• GHAS/CodeQL reporting missing input sanitization smithy-lang/smithy-typescript#1447

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).

[GavinZZ]

I'll reach out internally to see what the CodeCov issue is.

[GavinZZ]

@phuhung273 I synced with my team and there's some issue with a flaky test in the Code coverage test suite. We're working on a fix, please wait patiently and will update you soon.

[phuhung273]

Thanks so much @GavinZZ, please take your time

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).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.41%. Comparing base (559d676) to head (63721fa).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #32073      +/-   ##
==========================================
+ Coverage   78.36%   78.41%   +0.04%     
==========================================
  Files         105      106       +1     
  Lines        7170     7208      +38     
  Branches     1315     1323       +8     
==========================================
+ Hits         5619     5652      +33     
- Misses       1364     1369       +5     
  Partials      187      187              

Flag	Coverage Δ
suite.unit	78.41% <ø> (+0.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	78.41% <93.33%> (+0.04%)	⬆️

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 63721fa
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[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).

[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.