Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when Querying S3 Objects SSE Information in bucket with SSE-C Object #2381

Open
msi-bagusnurlistiyono opened this issue Jan 24, 2025 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@msi-bagusnurlistiyono
Copy link

Describe the bug
When querying a bucket object encryption information such as server_side_encryption or sse_customer_algorithm on a bucket that has object with SSE-C, it will fail producing error such as:

Error: aws: table 'aws_s3_object' column 'bucket_key_enabled' requires hydrate data from headS3Object, which failed with error operation error S3: HeadObject, https response error StatusCode: 400, RequestID: [REDACTED], HostID: [REDACTED], api error BadRequest: Bad Request.
 (SQLSTATE HV000)

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

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

To reproduce

  1. Create a bucket and put an object or two with SSE-C
  2. Try to query using steampipe using command `SELECT key,size,server_side_encryption,sse_customer_algorithm FROM aws_s3_object WHERE bucket_name = '[REDACTED]'``
  3. Observe output

Expected behavior
Outputs all the objects in the bucket and provides its encryption type for each object. While the error seems to come from the AWS itself (evidently the AWS console has the same error when trying to check the SSE-C object encryption type), can the query still proceeds when the error happens and maybe treat that column as "ERROR" value instead?

Image

Additional context
None at the moment

@msi-bagusnurlistiyono msi-bagusnurlistiyono added the bug Something isn't working label Jan 24, 2025
@ParthaI ParthaI self-assigned this Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants