Solutions:

ARTIFACTORY: The S3 doesn’t create the nonexistent dir when copying uploaded artifacts to the specified dir in the S3 is another cause for the "AmazonS3Exception (Status Code: 404; Error Code: NoSuchKey)" error

AuthorFullName__c
Sun Jinlong
articleNumber
000005989
ft:sourceType
Salesforce
FirstPublishedDate
2024-01-18T10:02:32Z
lastModifiedDate
2024-01-18
VersionNumber
1
The S3 needs support to create the nonexistent dir when copying the file to the nonexistent dir and the role needs to have sufficient permissions.
  1. Modify the upload logic in JuiceFS code to automatically create a nonexistent directory when copying files to a nonexistent directory in S3
  2. The IAM role for the S3 config needs to have the following permission:
s3:ListBucket, s3:ListBucketVersions, s3:ListBucketMultipartUploads, s3:GetBucketLocation, s3:GetObject, s3:GetObjectVersion, s3:PutObject, s3:DeleteObject, s3:ListMultipartUploadParts, s3:AbortMultipartUpload, s3:ListAllMyBuckets, s3:HeadBucket, s3:CreateBucket.