ARTIFACTORY: How to resolve “AmazonS3Exception (Status Code: 404; Error Code: NoSuchKey)” error during Artifactory initialisation?

Error example:

com.amazonaws.services.s3.model.AmazonS3Exception: The specified key does not exist. (Service: Amazon S3; Status Code: 404; Error Code: NoSuchKey; Request ID: null; S3 Extended Request ID: null; Proxy: null)
    at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1879)
    at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1418)

Description:

From the error, It indicates that the KMS key Id used in the Binary store configuration does not exist in the AWS account.

Hence, as a next step, it is required to check whether the key that is configured in the binarystore.xml is indeed present in the AWS KMS Customer managed keys section, and that it's available under the correct region.

Steps to view the keys in AWS account:

The AWS KMS keys in each account and Region are displayed in tables. There are separate tables for the KMS keys that you create and the KMS keys that AWS services create for you.

1. Sign in to the AWS Management Console and open the AWS Key Management Service (AWS KMS) console at https://console.aws.amazon.com/kms.
2. To change the AWS Region, use the Region selector in the upper-right corner of the page.
3. To view the keys in your account that you create and manage, in the navigation pane choose Customer managed keys. To view the keys in your account that AWS creates and manages for you, in the navigation pane, choose AWS managed keys. For information about the different types of KMS keys, see AWS KMS keys.

Reference:
Viewing KMS keys in the console