[Bug]: WorkSpace deployment failure for Graphics.g4dn or GraphicsPro.g4dn instance types #39553
Labels
bug
Addresses a defect in current functionality.
service/workspaces
Issues and PRs that pertain to the workspaces service.
Terraform Core Version
1.9.6
AWS Provider Version
5.68.0
Affected Resource(s)
aws_workspaces_workspace
Expected Behavior
Successful deployment of an AWS WorkSpace instance using the Graphics.g4dn or GraphicsPro.g4dn instance type. The minimum volume size for these instance types is
100
GB, but Terraform only allows80
or175 - 2000
.Actual Behavior
Terraform fails to apply and throws an error if
root_volume_size_gib = 100
is included in config. If this line is excluded to allow Terraform to use its default value, then AWS throws an error.Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Attempt deployment of a WorkSpace that uses the Graphics.g4dn or GraphicsPro.g4dn instance type with
root_volume_size_gib = 100
set inaws_workspaces_workspace
config. Terraform will error out indicating it is looking for a value of80
or within the range of175 - 2000
.If this line is commented out and
apply
is attempted using the default supplied by Terraform (80
in this case), AWS will throw an error indicating that100
is the minimum acceptable value for this instance type.Debug Output
No response
Panic Output
No response
Important Factoids
I'm not sure that Microsoft AD is required for this configuration; Simple AD or another directory type may be acceptable, but GovCloud, where I'm testing this deployment, does not offer any managed options other than Microsoft AD. The user I'm testing with in this case is called
wstest
.To work around this bug and manage an imported WorkSpace that was manually created in the AWS console,
workspace_properties.0.root_volume_size_gib
must be configured within the WorkSpace resource'slifecycle.ignore_changes
section.References
https://aws.amazon.com/about-aws/whats-new/2022/04/amazon-workspaces-graphics-g4dn-bundles/
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: