support single type EC2 Dedicated Hosts from MGN integration #29
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
When using certain EC2 Dedicated Hosts (e.g. r5d.large), they are restricted to a single Instance Type. The side effect from this is that the ec2:DescribeHosts response for these hosts will not include
InstanceFamily
in the HostProperties.Currently, the MGN lambda function assumes it will be able to resolve the InstanceFamily from the response, and will unfortunately fail when it is not present.
Description of changes:
This change includes logic to identify whether the ec2:DescribeHosts response contains the
InstanceFamily
, and if not, will instead use theInstanceType
value to glean the instance family.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.