Comment 14 for bug 1660385

We are in the same situation as quite a few others have mentioned here in the bug report already. To echo Nick (n6ck)'s comment above, we are also running a EC2 compatible metadata server here as well. Although we fully expect to add our own cloud-init datasource provider, it would be nice to know if the EC2 "strict_id: false" work-around will be here to stay for a while.