Skip to content

Add NestedVirtualizationEnabled launch-template parameter#1769

Open
iangmaia wants to merge 2 commits into
buildkite:mainfrom
iangmaia:iangmaia/add-nested-virtualization-param
Open

Add NestedVirtualizationEnabled launch-template parameter#1769
iangmaia wants to merge 2 commits into
buildkite:mainfrom
iangmaia:iangmaia/add-nested-virtualization-param

Conversation

@iangmaia
Copy link
Copy Markdown

@iangmaia iangmaia commented Apr 24, 2026

Description

Adds a NestedVirtualizationEnabled stack parameter and sets CpuOptions.NestedVirtualization=enabled on the agent launch template.

Note - local validation is blocked:

Checklist

  • Tests pass locally
  • Added tests for new features/fixes
  • Updated documentation (if applicable)
  • Linting checks pass

Release Notes

  • Public API: add NestedVirtualizationEnabled stack parameter for c8i, m8i, r8i, and their flex variants
  • My changes affect the public API (variable renames, new stack parameters, etc)
    • I have added a note at the top of the release notes highlighting the API changes
  • Any changes to external libraries (agent, scaler function, etc) have been flagged in release notes

@iangmaia iangmaia force-pushed the iangmaia/add-nested-virtualization-param branch from 59ea6f1 to 26d1038 Compare April 29, 2026 18:31
@iangmaia iangmaia marked this pull request as ready for review April 29, 2026 18:31
@iangmaia iangmaia requested a review from a team as a code owner April 29, 2026 18:31
@iangmaia
Copy link
Copy Markdown
Author

cc: @petetomasik (not sure who to tag for a review but just wanted to bring this to someone's attention, as it would be nice to allow for nested virtualization in certain EC2 instance types)

Copilot AI review requested due to automatic review settings May 18, 2026 14:17
@JoeColeman95
Copy link
Copy Markdown
Contributor

Hey @iangmaia

Thanks for the contribution! 🎉

Can see that this is indeed a valid option, but not for CloudFormation, unfortunately. We could theoretically avoid this by adding an ignore check for E3002 here, but, the problem is that this'll just be rejected as the CFN schema explicitly rejects additional options:

    "CpuOptions" : {
      "description" : "Specifies the CPU options for an instance. For more information, see [Optimize CPU options](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-optimize-cpu.html) in the *User Guide*.\n ``CpuOptions`` is a property of [AWS::EC2::LaunchTemplate LaunchTemplateData](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-launchtemplate-launchtemplatedata.html).",
      "additionalProperties" : false,
      "type" : "object",
      "properties" : {
        "ThreadsPerCore" : {
          "description" : "The number of threads per CPU core. To disable multithreading for the instance, specify a value of ``1``. Otherwise, specify the default value of ``2``.",
          "type" : "integer"
        },
        "AmdSevSnp" : {
          "description" : "Indicates whether to enable the instance for AMD SEV-SNP. AMD SEV-SNP is supported with M6a, R6a, and C6a instance types only. For more information, see [AMD SEV-SNP for Amazon EC2 instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html).",
          "type" : "string",
          "enum" : [ "enabled", "disabled" ]
        },
        "CoreCount" : {
          "description" : "The number of CPU cores for the instance.",
          "type" : "integer"
        }
      }
    },

I'd say we're best to wait on AWS here for this to be supported before proceeding further with a review?

@JoeColeman95
Copy link
Copy Markdown
Contributor

As a side note @iangmaia, I will check on the status of this periodically and will update once this is available.

@iangmaia
Copy link
Copy Markdown
Author

I'd say we're best to wait on AWS here for this to be supported before proceeding further with a review?

Agreed 👍 I'm not sure how that usually goes but hopefully it won't take long?

As a side note @iangmaia, I will check on the status of this periodically and will update once this is available.

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants