You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On upload to S3, PermanentRedirect error keeps happening as follows:
[ip-10-0-0-142.ap-southeast-1.compute.internal-0:ERROR] (hook=onItemCaptured) Error: operation error S3: PutObject, https response error StatusCode: 301, RequestID: 50...S, HostID: Cm...=, api error PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
[ip-10-0-0-75.ap-southeast-1.compute.internal-0:ERROR] (hook=onItemCaptured) Error: operation error S3: PutObject, https response error StatusCode: 301, RequestID: HH...E, HostID: tB...=, api error PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
[ip-10-0-0-142.ap-southeast-1.compute.internal-0:ERROR] (hook=onItemCaptured) Error: operation error S3: PutObject, https response error StatusCode: 301, RequestID: K8...X, HostID: Rd...=, api error PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
[ip-10-0-0-75.ap-southeast-1.compute.internal-0:ERROR] (hook=onItemCaptured) Error: operation error S3: PutObject, https response error StatusCode: 301, RequestID: PD...4, HostID: 1z...=, api error PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
[ip-10-0-0-142.ap-southeast-1.compute.internal-0:ERROR] (hook=onItemCaptured) Error: operation error S3: PutObject, https response error StatusCode: 301, RequestID: AY...G, HostID: 9C...=, api error PermanentRedirect: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.
Click on example Upload PCAP File of a Stream to an AWS S3 Bucket If HTTP Status Code is 500 or Upload a PCAP Snapshot to an AWS S3 Bucket If HTTP Status Code is 500
Generate a 500 error (or remove && data.response.status === 500 in line 4)
See errors
Expected behavior
Stuff should upload successfully to the bucket.
Desktop (please complete the following information):
Since I don't have access to the s3 endpoint that kubeshark is attempting to reach, I'm also suspecting that kubeshark is using the old S3 endpoint format: https://my-bucket-123.s3-us-west-2.amazonaws.com/test/123
Instead of the new one: https://my-bucket-123.s3.us-west-2.amazonaws.com/test/123
Take note of the "." after s3
The text was updated successfully, but these errors were encountered:
HI @kwongtn98. I was able to reproduce this error locally. Apparently we override the region with us-east-2. To bypass this issue, you can open a bucket on us-east-2 as opposed to ap-southeast-1.
Also, please use the new version of the script.
alongir
changed the title
AWS S3 Uploads keep failing with PermanentRedirect
AWS Region isn't read by S3 PUT helper (AWS S3 Uploads keep failing with PermanentRedirect)
Oct 31, 2023
Describe the bug
On upload to S3,
PermanentRedirect
error keeps happening as follows:Provide more information
AWS EKS, Istio
config.yaml
as followsTo Reproduce
Steps to reproduce the behavior:
kubeshark tap
Upload PCAP File of a Stream to an AWS S3 Bucket If HTTP Status Code is 500
orUpload a PCAP Snapshot to an AWS S3 Bucket If HTTP Status Code is 500
&& data.response.status === 500
in line 4)Expected behavior
Stuff should upload successfully to the bucket.
Desktop (please complete the following information):
Additional context
Logs
kubeshark_logs_2023_10_30__18_01_40.zip
S3 permissions
Since I don't have access to the s3 endpoint that kubeshark is attempting to reach, I'm also suspecting that kubeshark is using the old S3 endpoint format:
https://my-bucket-123.s3-us-west-2.amazonaws.com/test/123
Instead of the new one:
https://my-bucket-123.s3.us-west-2.amazonaws.com/test/123
Take note of the "." after
s3
The text was updated successfully, but these errors were encountered: