Describe the bug
Queries against the aws_s3_bucket table sometimes produce NoSuchBucket errors. While the exact circumstances of this bug are not clear to me, I assumed, that S3 is following an eventually-consistent data model. However, I learned that this is not the case (see here), leaving me with no explanation for this bug at the moment. Right now I fixed the issue for me, by ignoring this error type in my plugin config file for all my connection. However, it would be better if this error could be caught and ignored by default, to make the AWS plugin more robust.

Steampipe version (steampipe -v)
Example: v1.0.1

Plugin version (steampipe plugin list)
Example: v1.4.0

To reproduce
This is hard to reproduce since the circumstances on when this issue appears are not 100% clear to me. My best guess on how to reproduce it would be to have a query running against an AWS account in which a lot of S3 bucket activity (creation / deletion of buckets) is going on.

Expected behavior
No error occurs and the bucket is just ignored.

Additional context
This problem was briefly discussed in this Slack thread with @cbruno10.