chore(codeguruprofiler): add region constraints to integ tests

[aemada-aws]

Issue # (if applicable)

Closes #.

Reason for this change

The aws-codeguruprofiler integration tests fail when deployed to regions where the AWS::CodeGuruProfiler::ProfilingGroup CloudFormation resource type is not available (e.g. eu-west-3, sa-east-1, ap-northeast-2, ap-south-1, ca-central-1). The error is:

ValidationError: Template format error: Unrecognized resource types: [AWS::CodeGuruProfiler::ProfilingGroup]

Description of changes

Added regions constraint to the IntegTest props in both CodeGuruProfiler integ tests, restricting deployment to regions where the CFN resource type is confirmed available:

• us-east-1, us-west-2, eu-west-1, eu-central-1, ap-northeast-1, ap-southeast-1, ap-southeast-2

No other code changes. Test logic and assertions are unchanged.

Files modified:

• test/aws-codeguruprofiler/test/integ.profiler-group-import-functions.ts
• test/aws-codeguruprofiler/test/integ.profiler-group.ts

Describe any new or updated permissions being added

N/A

Description of how you validated changes

yarn integ \
  test/aws-codeguruprofiler/test/integ.profiler-group-import-functions.js \
  test/aws-codeguruprofiler/test/integ.profiler-group.js \
  --disable-update-workflow --update-on-failed --force \
  --parallel-regions us-east-1 \
  --parallel-regions us-west-2 \
  --parallel-regions eu-west-1 \
  --parallel-regions eu-central-1 \
  --parallel-regions ap-northeast-1 \
  --parallel-regions ap-southeast-1 \
  --verbose

Result: Tests: 2 passed, 2 total

• integ.profiler-group — SUCCESS (us-east-1, 83.6s)
• integ.profiler-group-import-functions — SUCCESS (us-west-2, 163.9s)

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

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results	24 ran	24 passed

Test	Result
No test annotations available

• View Security Guardian Results

[github-actions]

⚠️ Experimental Feature: This security report is currently in experimental phase. Results may include false positives and the rules are being actively refined.
Please try merge from main to avoid findings unrelated to the PR.

---

	Tests	Passed ✅	Skipped	Failed
Security Guardian Results with resolved templates	24 ran	24 passed

Test	Result
No test annotations available

• View Security Guardian Results with resolved templates

[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-03-12 13:09 UTC · Rule: default-squash
• 🚫 Left the queue — 2026-03-12 13:09 UTC · at ad6f7906919383f36309018618d30e24e57d2a0a

This pull request spent 5 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/integration-test-deployment-auto.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).

[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-03-12 14:04 UTC · Rule: default-squash
• ✅ Checks passed · in-place
• ✅ Merged — 2026-03-12 14:05 UTC · at 706b86ffa9a38d41d93245aa76f290855e16f894

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

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore(codeguruprofiler): add region constraints to integ tests #37172
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • chore(codeguruprofiler): add region constraints to integ tests #37172
• 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.