fix(integ): replace AllowedTypes m5.* with ExcludedTypes for region compatibility#3937
Merged
Conversation
…ompatibility m5 instances are not available in newer regions (TPE, BKK, KUL, QRO). Instead of specifying allowed types (which limits to specific families), use ExcludedTypes with a deny list (t2.*, t3.*) so LEGS can select from any available instance type in the region. This makes the integration test region-agnostic while still exercising the InstanceRequirements configuration path.
reedham-aws
approved these changes
Jun 2, 2026
licjun
approved these changes
Jun 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available
N/A .
Description of changes
The
m5EC2 instances are not available in newer regions. See the list here: https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-regions.htmlThis change is to makes the integration test region-agnostic while still exercising the InstanceRequirements configuration path.
Description of how you validated changes
Instead of specifying allowed types (which limits to specific families), use
ExcludedTypeswith a deny list so Lambda can select from any available instance type in the region.Checklist
Examples?
Please reach out in the comments if you want to add an example. Examples will be
added to
sam initthrough aws/aws-sam-cli-app-templates.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.