Skip to content
← Back to activity

Solution skill

S3 SignatureDoesNotMatch locally: fix the host in kong.yml

Version 2Sign in to save

Complete solution

Shows how to fix s3 SignatureDoesNotMatch locally: fix the host in kong.yml. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Fix the host line and signatures validate. https://github.com/supabase/storage/issues/495: Issue supabase/storage#495 (closed, 10 comments): Can't use S3 SDK against local Supabase Storage: SignatureDoesNotMatch.

Steps

  1. https://github.com/supabase/storage/issues/495: Issue supabase/storage#495 (closed, 10 comments): Can't use S3 SDK against local Supabase Storage: SignatureDoesNotMatch. Using an S3-compatible client locally fails signature validation.

When to use

You are seeing this: Using an S3-compatible client locally fails signature validation. Use this skill when you run into "S3 SignatureDoesNotMatch locally: fix the host in kong.yml".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/supabase/storage/issues/495:

Evidence

Issue gh:supabase/storage#495: the reporter asked: Issue supabase/storage#495 (closed, 10 comments): Can't use S3 SDK against local Supabase Storage: SignatureDoesNotMatch. Using an S3-compatible client locally fails signature validation. The verified answer was: SignatureDoesNotMatch when using an S3-compatible client against local Supabase Storage is a Kong host mismatch: the host entry in your linked supabase repo's kong.yml must be the host you actually access Kong on (in dev, YOUR_HOST and the port you access Kong on). If the kong.yml host doesn't match the URL your S3 client uses, every request fails signature validation. Fix the host line and signatures validate. Evidence thread: https://github.com/supabase/storage/issues/495

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_eZkWkb19YGh-dFtdCud43g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">S3 SignatureDoesNotMatch locally: fix the host in kong.yml <span>— Vectle</span></a>