[BUG] DynamoDB tables without tags are not discovered

[rassvetalov]

Is there an existing issue for this?

• I have searched the existing issues

YACE version

v0.61.2

Config file

discovery:
  jobs:
    - type: AWS/DynamoDB
      regions:
        - us-east-1
      nilToZero: true
      metrics:
        - name: ConsumedReadCapacityUnits
          statistics: [Sum]
          period: 60
          length: 60
        - name: ConsumedWriteCapacityUnits
          statistics: [Sum]
          period: 60
          length: 60

Current Behavior

DynamoDB tables without any AWS tags are not discovered by YACE, even though no searchTags filter is specified in the configuration.

Evidence:

• CloudWatch ListMetrics returns 276 unique DynamoDB tables
• YACE only reports metrics for 216 tables
• All 60 missing tables have 0 tags in AWS
• All tables present in YACE have at least 1 tag

After adding a Name tag to the untagged tables, they appeared in YACE output.

Expected Behavior

When no searchTags filter is specified, YACE should discover all resources that have CloudWatch metrics, regardless of whether they have AWS tags or not.

Steps To Reproduce

1. Create a DynamoDB table without any tags
2. Wait for CloudWatch metrics to appear (verify with aws cloudwatch list-metrics)
3. Configure YACE with a simple AWS/DynamoDB job (no searchTags)
4. Observe that the untagged table is not in YACE output
5. Add any tag to the table (e.g., Name=<table_name>)
6. Wait for next YACE scrape cycle
7. Observe that the table now appears in YACE output

Anything else?

This appears to be related to issue #1169 which reported similar behavior for Lambda functions.

The root cause seems to be in the associator logic that requires resources to have at least one tag to be matched, even when no tag filtering is configured.