Apply Capacity Reservation tenancy to AWS instance launch#3992
Merged
Conversation
A Capacity Reservation created with non-default tenancy (e.g. `dedicated`) only accepts instances launched with a matching `Placement.Tenancy`. Previously dstack always launched with the implicit `default` tenancy, so runs targeting a dedicated-tenancy reservation failed to match it. Read `Tenancy` from the reservation dstack already queries in `create_instance` and pass it through to `create_instances_struct`, which sets `Placement.Tenancy` when it is non-default. No user-facing config; it is detected automatically from the reservation and merges cleanly with the placement-group `Placement` entry. Assisted-by: Claude
jvstme
approved these changes
Jun 25, 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
2 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.
A Capacity Reservation created with non-default tenancy (e.g.
dedicated) only accepts instances launched with a matchingPlacement.Tenancy. Previously dstack always launched with the implicitdefaulttenancy, so runs targeting a dedicated-tenancy reservation failed to match it.Read
Tenancyfrom the reservation dstack already queries increate_instanceand pass it through tocreate_instances_struct, which setsPlacement.Tenancywhen it is non-default. No user-facing config; it is detected automatically from the reservation and merges cleanly with the placement-groupPlacemententry.