ListTagsOfResource on a stream ARN after its table is deleted answers ResourceNotFoundException; DynamoDB serves the stream's tags #607

Summary

After a table is deleted, Amazon DynamoDB still answers ListTagsOfResource on the table's stream ARN with 200 and the stream's tags. ExtendDB answers 400 ResourceNotFoundException, because the tag path requires the table to exist.

Measured (us-east-1, 2026-10-26, 3 of 3)

Table with a stream; TagResource on LatestStreamArn with sk and sk2; DeleteTable; after DescribeTable answers ResourceNotFoundException: ListTagsOfResource {ResourceArn: <stream ARN>} answers 200 {Tags: [sk2]} (an UntagResource of sk sent during the delete had been applied).

ExtendDB on PostgreSQL at the head of #599: ResourceNotFoundException Requested resource not found: ResourceArn: <stream ARN> not found. validate_resource_arn reads the table on all four backends.

Notes

The stream-ARN tag rows themselves are kept across the table's delete on every backend (no delete path removes them), which matches the service; only the read refuses. Related: #452 (a stream ARN for a stream that does not exist) and #518 (streams stay describable after the table is gone).