# S3 SignatureDoesNotMatch locally: fix the host in kong.yml
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.
## Context from the issue
gh:supabase/storage#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.