Skip to content
Back

Executor with custom S3 doesn't work in appwrite 1.9.5 (executor 0.25.1)

  • 0
  • 3
  • Self Hosted
  • Functions
  • Sites
2 Jul, 2026, 13:25

Was testing to upgrade appwrite to 1.9.5 and when testing the S3 part i saw the executor didn't work anymore. When looking closly i saw the StorageFactory doesn't provide the bucket anymore.

I opened an issue in the executor project : https://github.com/open-runtimes/executor/issues/239

TL;DR
Issue with custom S3 executor in Appwrite 1.9.5 and executor 0.25.1, new pull request submitted at https://github.com/appwrite/appwrite/pull/13064.
2 Jul, 2026, 13:25

Executor with custom S3 doesn't work in appwrite 1.9.5 (0.25.1)

2 Jul, 2026, 13:25

Executor with custom S3 doesn't work in appwrite 1.9.5 (executor 0.25.1)

2 Jul, 2026, 14:13

same issue

2 Jul, 2026, 14:33

since the issue include everything i made an override compose for that part so using the yaml file and using docker compose -f docker-compose.yml -f docker-compose.executor-s3-hotfix.override.yml up -d it should fix the openruntimes-executor (check the comment there is an env to add/change)

2 Jul, 2026, 14:33

<@224940926861049857> if you want to test it

11 Jul, 2026, 12:46
29 Jul, 2026, 16:41

I still have this issue in 1.9.6

29 Jul, 2026, 17:44

do you confirm your executor have the S3 URL like this ? :

TypeScript
s3://<key>:<secret>@localhost/appwrite?region=<region>&url=<url-encoded-s3-endpoint>

where :

  • key is your Access Key
  • secret is your Secret Key
  • region is the S3 region
  • url-encoded-s3-endpoint is your s3 url but encoded like https%3A%2F%2Fs3.example.com
29 Jul, 2026, 17:46

also 1.9.6 uses openruntimes/executor:0.25.4 is it that one that your using with 1.9.6 and not 0.25.1 ?

29 Jul, 2026, 18:12

yes the version is openruntimes/executor:0.25.4. How do I check the executor url?

29 Jul, 2026, 19:23

docker ps | grep executor then docker inspect <container_name> | grep OPR_EXECUTOR_CONNECTION_STORAGE

31 Jul, 2026, 08:22

I don’t have the OPR_EXECUTOR_CONNECTION_STORAGE env variable set anywhere. Is this now required to make it work with S3? I downloaded the compose and .env files from the installation page and they do not contain that variable

31 Jul, 2026, 08:26

iirc, they don't document S3 setups for SH but it's there : https://github.com/open-runtimes/executor/blob/main/src/Executor/Runner/Docker.php#L293

31 Jul, 2026, 08:26

and yes required, it replace the old OPR_EXECUTOR_STORAGE.... for the S3 connection

31 Jul, 2026, 08:35

Thank you. I finally got it working

1
31 Jul, 2026, 08:43

<@743532656767270934> would it be possible to document that env somewhere ? (like adding an executor s3 connection in the .env and pass it to the compose, and maybe on the website as well)

31 Jul, 2026, 08:46

might be, up for a challenge? i can review ur pr

31 Jul, 2026, 08:50

why not, tho for the website i don't really know svelte so i prefer letting someone do that part.

31 Jul, 2026, 08:58

its just docs, shouldnt be hard

31 Jul, 2026, 08:58

ye but if i start the website part i will also want to make a complete S3 doc for SH ..

31 Jul, 2026, 09:45

merge conflict

31 Jul, 2026, 09:51

bruh i pulled everything before xdd will check what the backend is, tho i think i will do "accept both"

31 Jul, 2026, 09:51

also do check greptile, might be valid?

Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more