I already have a Dockerfile and a homeserver.yaml for Matrix-Synapse, and everything runs—except the S3 storage provider plugin that should point media to my Google Cloud Storage bucket. Synapse starts without errors, but it never loads the plugin, so nothing is actually written to the bucket. The problem is clearly on the S3 storage provider plugin side; Docker execution and the core Synapse configuration are otherwise fine. All declared Python dependencies are present in the container, so it’s not a missing-library issue. I need you to pinpoint why Synapse is ignoring the plugin, update whatever paths, entry-points, or environment variables are required, and hand back a working setup. Deliverables • Corrected Dockerfile (or supplemental docker-compose override) that loads the S3 storage provider plugin at startup • Updated homeserver.yaml with the right module reference and any mandatory S3/GCS parameters • A brief README or comment block explaining what you changed and why, so I can apply the same pattern in other environments Acceptance is simple: start the container, watch Synapse boot logs show the plugin initialising, then upload media through a room and confirm it lands in the designated Google Cloud Storage bucket.