Predictions - InvalidS3ObjectException

Env : React-native “aws-amplify”: “^3.0.8”, “aws-amplify-react-native”: “^4.0.4”, “react”: “16.11.0”, “react-native”: “0.62.2”,

Predictions configuration for Amplify.configure() : predictions: { identify: { identifyText: { proxy: false, region: “us-east-1”, defaults: { format: “ALL” } } }

Issue : When I user Predictions with S3 object, it returns an InvalidS3ObjectException. “Unable to get object metadata from S3” However when I use Storage on the same file, everything works fine.

My code - pretty simple :

 await Predictions.identify({
      text: {
        source: {
          key: "myFile.jpeg",
          level: "public"
        },
        format: "PLAIN"
      }
    })
      .then((res) => setPrediction(JSON.stringify(res, null, 2)))
      .catch((err) =>
        setPrediction("Predictions error : " + JSON.stringify(err, null, 2))
      );
  }

My succeeded Storage code :

 Storage.get("myFile.jpeg")
     .then((res) => setPrediction(JSON.stringify(res, null, 2)))
     .catch((err) => "Storage error : " + JSON.stringify(err, null, 2));

[mlafo]

@cedricgrothues - I gave a try in eu-west-1 region. It’s fixed. Predictions works with private and protected Storage. Thank a lot.

[cedricgrothues]

Ok, I just had a look, and it seems like @mlafo and @onlybakam are right, this issue describes two different “problems” that both cause an InvalidS3ObjectException:

1. Rekognition / Textract and S3 have to be in the same region.
2. The S3Object name, extracted from the object URL, is still percent-encoded.

While the first “problem” seems to be by design, the second one describes a bug that should be an easy fix by decoding parsedURL[2]:

res({ S3Object: { Bucket: parsedURL[1], Name: decodeURIComponent(parsedURL[2]) } });

decodeURIComponent replaces the %3A with the corresponding character (:), while the rest of the object name will stay as-is.