Hi @Nuranto. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

Hello @Nuranto,

Thanks for the report and collaboration!

We have tried to reproduce this issue in Magento 2.4.7 and in the latest development branch but the issue is not reproducible for us.

We used MINIO, for issue reproduction as it has a default set use path-style. After setting up the MINIO in the Magento instance tried to upload an image in Product by editing it and the image is successfully uploaded on MINIO. We have verified it from the Web UI.

Please have a look into the below env.php entry for remote storage:

'remote_storage' => [
        'driver' => 'aws-s3',
        'config' => [
            'endpoint' => 'http://127.0.0.1:9000',
            'bucket' => 'magento247',
            'region' => 'us-east-1',
            'path_style' => true,
            'use_path_style_endpoint' => true,
            'credentials' => [
                'key' => 'KEY',
                'secret' => 'SECRET'
            ]
        ]
    ],

Let us know if we missed anything.

Thanks

Hello @engcom-Hotel,

The configuration you used would result with command line option : --remote-storage-path_style=1 which does not match what's expected :

Note : The documentation (https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/storage/remote-storage/remote-storage) has not been updated with new options.

Hello @Nuranto,
Thanks for the reply!

Does adding the below configuration in env.php resolve your issues:

'remote_storage' => [
        'driver' => 'aws-s3',
        'config' => [
            'xxx' => 'xxx',
            'xxx' => 'xxx',
            'endpoint' => 'END-POINT',
            'use_path_style_endpoint' => true,
            'path_style' => true,
            'credentials' => [
                'key' => 'xxx',
                'secret' => 'xxx'
            ]
        ]
    ],