[export feature] S3 bucket 403 Forbidden while running exports

[sheepfy]

Preconditions and environment

Magento latest

Steps to reproduce

1. setup S3 remote storage in app/etc/env.php (or whereever this can be set)

    'remote_storage' => [
        'driver' => 'aws-s3',
        'config' => [
            'bucket' => 'my-bucket',
            'region' => 'my-region',
            'credentials' => [
                'key' => 'my-key',
                'secret' => 'my-secret'
            ]
        ],
    ],

2. Go to admin panel ->System -> Data Transfer -> Export
3. Select Products & CSV (probably replicable with anything in here)
4. Setup the crons or manually run the queue bin/magento queue:consumers:start exportProcessor

Expected result

No error logs

Actual result

Error logs

[2025-11-17T10:42:30.700718+00:00] report.ERROR: Unable to write file at location: import_export/./. Error executing "PutObject" on "https://my-bucket.amazonaws.com/import_export/./"; AWS HTTP error: Client error: `PUT https://my-bucket.amazonaws.com/import_export/./` resulted in a `403 Forbidden` response

Additional information

Stack trace
vendor/magento/module-import-export/Model/Export.php :: _getWriter
- this calls $this->_writer = $this->_exportAdapterFac->create($fileFormats[$this->getFileFormat()]['model']);
vendor/magento/module-import-export/Model/Export/Adapter/AbstractAdapter.php :: __construct
- this calls $this->_init()
vendor/magento/module-import-export/Model/Export/Adapter/Csv.php :: _init()
- this calls $this->_fileHandler = $this->_directoryHandle->openFile($this->_destination, 'w');
vendor/magento/framework/Filesystem/Directory/Write.php :: openFile
- this has $path as a filename something like "importexport_691af13f4e84b" therefore the dirname('...') returns dot . and S3 doesn't like dots.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @sheepfy. 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.

• 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.

[m2-assistant]

Hi @engcom-Bravo. 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

  - 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.

[engcom-Bravo]

Hi @sheepfy,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.

Error logs

#6 {main} {"exception":"[object] (League\\Flysystem\\UnableToWriteFile(code: 0): Unable to write file at location: import_export/importexport_691d911ca16df. Error executing \"PutObject\" on \"https://my-bucket.s3.my-region.amazonaws.com/import_export/importexport_691d911ca16df\"; AWS HTTP error: cURL error 6: Could not resolve host: my-bucket.s3.my-region.amazonaws.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://my-bucket.s3.my-region.amazonaws.com/import_export/importexport_691d911ca16df at /usr/local/var/www/magentok/magento2/vendor/league/flysystem/src/UnableToWriteFile.php:24)

Hence Confirming the issue.

Thanks.