AWSOverview
Launch templates should not allow a metadata hop count greater than 1 when source/destination check is disabled.
This ensures that containers or other VMs cannot access the metadata service of the instance.
Remediation guidance
- Open the Launch Template in the AWS Console using the dedicated button
- From the actions menu select
Modify template (Create new version) - Scroll down to and expand
Advanced details - Scroll down to
Metadata response hop limitand set it to1 - Click
Create template version - Use the new launch template version instead of the old one
- Delete the old template version
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
AWS
Use AWS Organizations guardrails, AWS Config rules or conformance packs where they fit, approved account baselines, and IaC modules so new resources inherit the secure setting.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
AWS Launch Templates with Hop Count Greater than 1
Connectors
AWS
Covered asset types
LaunchTemplateVersion
Expected check: eq []
{
launchTemplateVersions(
where: { metadataOptionHTTPPutResponseHopLimit_GT: 1 }
) {...AssetFragment}
}
