Accessing Network Volume via S3 Returns "error"
Hi.
I've been running a serverless service for months without a problem, which connects to a network storage using the S3 interface.
However, I started getting error responses from the S3 client since a few hours ago, which reads:
Caused by: aws.smithy.kotlin.runtime.serde.DeserializationException: Unexpected character 'e' while looking for the start of a tag At offset 1 (showing range 0-4): errorApparently, the server responds with text "error" instead of an expected XML document. I can see no other error messages anywhere else. And I can reproduce the error locally, by attempting to upload to the S3 from a local server. The id of the volume is
aqiajufyn9, and it's hosted in the EU-RO-1 region.
Could you look into this problem?
Thanks in advance!2 Replies
I have a similar problem, using S3 on a network volumne on EU-RO-1. I get a lot of these errors
botocore.exceptions.ClientError: An error occurred (502) when calling the GetObject operation (reached max retries: 4): Bad Gateway
botocore.exceptions.ClientError: An error occurred (502) when calling the HeadObject operation (reached max retries: 15): Bad Gateway
I also see the "missing XML" error, but this seems to be only a side-effect, at least in our case
JanE -- what's your network volume ID?