First, besides using NGINX, for local development if you want to work a UI let’s say on localhost:3000 (some React App) and the lakeFS server on localhost:8000. You can use NGINX but this is exactly what happens in lakeFS when develop our own UI, we use a reverse proxy so here’s a reference: Run npm run dev and the UI will start with a reverse-proxy on localhost:3000 which will speak with lakeFS on localhost:8000 - check the reverse proxy config. Using that same logic you can achieve with your own ui for local development. In production they would sit on the same domain of course. Second, regarding pre-sign URL: both put and get is available (for S3, GCS, Azure - not for local storage or anything else). Check this doc reference: To use this functionality in the lakeFS UI: you would have to allow CORS on your bucket policy and in lakeFS config enable in the UI. To use this functionality in lakectl: check lakectl fs upload and lakectl fs cat example. To write your own API either use a generated SDK or based on our HTTP OAPI spec then for pre-sign URL best would be to look at what

lakectl

does, for example to upload an object with a pre-sign feature look at clientUploadPreSignHelper API calls to lakeFS: First it calls getPhysicalAddress to get a presigned URL to upload (without the need for AWS credentials, just lakeFS) and then LinkPhysicalAddressWithResponse.