1. Update IMDS settings for Ocean and Elastigroup

You can define metadata options in your AWS Auto Scaling groups. When you import those groups into the Flexera console, the metadata configuration is also imported. You can then adjust the settings to enforce IMDSv2.

Add the following configuration to your Ocean cluster or Elastigroup API request:

"compute": {
  "launchSpecification": {
    "instanceMetadataOptions": {
      "httpTokens": "required",
      "httpPutResponseHopLimit": 12,
      "httpEndpoint": "enabled"
    }
  }
}

After you update the configuration, apply it to your running instances by doing one of these actions:

• Deploy a new Elastigroup

• Roll an Ocean cluster

This restarts the instances so they apply the new IMDSv2 settings.

2. Update IMDS settings for Stateful Nodes

When you import a stateful managed node into Flexera, an image is created from the snapshot. When the node recycles, IMDS settings may revert to IMDSv1. To ensure IMDSv2 persists, use a custom AMI and enable IMDSv2 on it.

Create a new AMI with IMDSv2

aws ec2 register-image \
--name my-image \
--root-device-name /dev/xvda \
--block-device-mappings DeviceName=/dev/xvda,Ebs={SnapshotId=snap-0123456789example} \
--imds-support v2.0

Modify an existing AMI to use IMDSv2

aws ec2 modify-image-attribute \
--image-id ami-0123456789example \
--imds-support v2.0

After you configure the AMI, create a stateful node in the Flexera console using that custom AMI. All recycled instances will launch with IMDSv2 enabled.