Ingestion from S3 fails with a message similar to below:
<Message>The specified key does not exist</Message>
Ingestion spec has ioConfig block similar to the following:
The cause of this issue is a bug in the jetS3t library when using AWS S3 Signature V4.
The workaround is to revert to using Signature V2 for AWS S3. This can be enabled in the Experimental Features section of the cluster settings as illustrated below.
Beginning with Imply 2.8.0, jetS3t is no longer used. Instead the native AWS S3 API is leveraged, thus resolving this issue.