ohai doesn't recognize cloud metadata in aws ap-southeast about ohai HOT 5 CLOSED

The problem occurs if you start an instance in a vpc. Funny enough everything is working fine using ec2metadata tool.

from ohai.

Does using the hinting system for ohai fix this? I seem to recall if you're using VPC that you have to use hints.

from ohai.

@btm isn't this problem with VPC nodes unable to determine if they're in EC2 which drove creating the hinting system in the first place? This has nothing specific to do with ap-southeast, and there's really nothing to fix here?

from ohai.

This should get closed out. EC2 detection is pretty basic and relies on a specific Xen like MAC address being seen. I'm fairly confident that will not work with modern VPC AWS setups. In order to reliably detect a node as being in EC2 you need the hint file to tip Ohai off that it should make a metadata call. It's not possible for Ohai to make metadata calls for every possible cloud provider with the hopes that one might return data.

from ohai.

Closing this out based on my previous comment. As much as we'd like to magically detect clouds we rely on the hints to limit the time it takes to detect all attributes.

from ohai.