Firecracker Metadata Service + NoCloud source - API TOKEN required with MMDS v2 (v1 deprecated)

This bug was originally filed in Launchpad as [LP: #1972819](https://bugs.launchpad.net/cloud-init/+bug/1972819)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2022-05-10T10:34:41.283722+00:00

date_fix_committed = None

date_fix_released = None

id = 1972819

importance = undecided

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1972819

milestone = None

owner = jaroslav-pulchart-4

owner_name = Jaroslav Pulchart

private = False

status = confirmed

submitter = jaroslav-pulchart-4

submitter_name = Jaroslav Pulchart

tags = []

duplicates = []

_Launchpad user **Jaroslav Pulchart(jaroslav-pulchart-4)** wrote on 2022-05-10T10:34:41.283722+00:00_

Hello,

I noticed the Firecracker 1.1.0 hypervisor announced MMDS v1 deprecation in favor of MMDS v2 (https://github.com/firecracker-microvm/firecracker/releases/tag/v1.1.0).

The MMDS v2 is a a session-oriented and request to get and use API_TOKEN like EC2 Metadata service IMDSv2.

Cloud-init can be used with firecracker medatada service using NoCloud data source as is described in https://ongres.com/blog/automation-to-run-vms-based-on-vanilla-cloud-images-on-firecracker/. However this is going to stop to work with MMDS v2 where the guest cannot get any user-data/meta-data by cloud-init any more due to missing API_TOKEN in request.

Can you please implement API_TOKEN feature into NoCloud data source?

Many thanks,

Start with the NoCloud data source and the linked Firecracker MMDS v2 release details, then review the original Launchpad report for the request requirements. Done means cloud-init can obtain user-data and meta-data from Firecracker's MMDS v2 by using the required API_TOKEN.

Written by the indexing model from the issue text.