When uploading artifacts failed to Artifactory, we get the error "Status Code: 404; Error Code: NoSuchKey" in the Artifactory log. The Artifactory uses the JuiceFS S3 as the filestore and the S3 Binary Storage Configuration uses the S3 Direct Upload Template.
We can find a cause for the error from KB, "How to resolve “AmazonS3Exception (Status Code: 404; Error Code: NoSuchKey)” error during Artifactory initialization?", but the KMS key Id used in the Binary store configuration already exists in the AWS account, which isn’t the cause for this case.
We can find a cause for the error from KB, "How to resolve “AmazonS3Exception (Status Code: 404; Error Code: NoSuchKey)” error during Artifactory initialization?", but the KMS key Id used in the Binary store configuration already exists in the AWS account, which isn’t the cause for this case.