InstanceLookupTable throws errors when not running inside AWS about graylog-plugin-aws HOT 5 CLOSED

@bernd Also see Graylog2/graylog-plugin-threatintel#55.

Looks like we should fix this in the lookup table/adapter interface in Graylog core.

from graylog-plugin-aws.

@joschi The InstanceLookupTable is not using the lookup table infrastructure yet.

But can you elaborate on how to fix this in the interface? Adding a method to indicate if the lookup table should run/refresh?

from graylog-plugin-aws.

Adding a method to indicate if the lookup table should run/refresh?

Yes, for example by adding lifecycle methods similar to Service which allow starting/stopping lookup tables (or their cache).

from graylog-plugin-aws.

Yes, for example by adding lifecycle methods similar to Service which allow starting/stopping lookup tables (or their cache).

The data adapters and caches are AbstractIdleService subclasses already. The problem is that they are currently started unconditionally. (and the refresh as well)

from graylog-plugin-aws.

@bernd I'm unable to reproduce the issue if the "AWS Instance Name Lookup" processor is disabled or if "AWS Plugin Configuration" ➡️ "Instance detail lookups" is disabled.

from graylog-plugin-aws.