neon-object-storage

Provision S3-compatible object storage buckets that branch with Neon Postgres projects.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/akira777777/vladfsBET --skill neon-object-storage-akira777777
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: neon-object-storage
Source: https://github.com/akira777777/vladfsBET/tree/main/.grok/skills/neon-object-storage
Command: npx skills add https://github.com/akira777777/vladfsBET --skill neon-object-storage-akira777777

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires files-sdk, @aws-sdk/client-s3, @aws-sdk/s3-presigned-post, @aws-sdk/s3-request-presigner.

What problem does it solve? Applications need a place to store uploads, avatars, documents, and generated files, but adding a separate storage provider like AWS S3 or Cloudflare R2 creates extra accounts, credentials, and drift between file state and database state across environments. This Skill sets up S3-compatible object storage that branches together with your Neon Postgres project, so files and database rows stay in sync across dev, preview, staging, and production. ## Core Features & Use Cases - Branch-aware buckets: Declare buckets in a neon.ts infrastructure-as-code file and provision them with neon deploy; every branch gets isolated copy-on-write storage state. - Standard S3 tooling: Works with AWS SDKs, boto3, the AWS CLI, and presigned URLs using injected AWS-standard env vars (AWS_ACCESS_KEY_ID, AWS_ENDPOINT_URL_S3, and more). - Files SDK integration: Use the files-sdk Neon adapter for a unified upload, download, list, copy, delete, and presigned URL API. - Use Case: An agent generates an image, uploads it to an images bucket, stores the object key in a Postgres row on the same branch, and returns a presigned URL on read — a preview branch then inherits both the rows and the files consistently. ## Quick Start Ask the AI to set up Neon Object Storage by declaring an images bucket in neon.ts, running neon deploy, and writing an upload and presigned-download flow using the files-sdk Neon adapter.

Frequently Asked Questions about neon-object-storage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up object storage with Neon Postgres?▼

Declare buckets under the `buckets` key in a `neon.ts` config file, then run `neon deploy` to provision them on the linked branch. Neon injects AWS-standard S3 env vars, so AWS SDKs work from the environment with no extra configuration.

How to upload files to Neon Object Storage from Node.js?▼

Install files-sdk with the AWS S3 peer dependencies and create a Files instance using the neon adapter with your bucket name. Call `files.upload(key, body, { contentType })` with a Buffer, Blob, stream, or string, and use `files.url()` for presigned GET links.

Does Neon Object Storage work with the AWS S3 SDK?▼

Yes, Neon speaks the S3 API directly and supports AWS SDKs, boto3, the AWS CLI, and presigned URLs. The S3 client must set `forcePathStyle: true` because Neon requires path-style addressing and SigV4 signing.

Can I use Neon Object Storage instead of AWS S3 or Cloudflare R2?▼

Yes, if your app already uses Neon Postgres and you want one provider where storage branches with your database. It is S3-compatible, but it is only available in aws-us-east-2, aws-us-east-1, aws-eu-central-1, and aws-ap-southeast-1.

What are the limitations of Neon Object Storage?▼

It is limited to four AWS regions and does not support static website hosting — `PutBucketWebsite` returns 501 Not Implemented. Public assets served to browsers should sit behind a CDN like Cloudflare or Vercel using the bucket endpoint as origin.

How does branching work with Neon Object Storage buckets?▼

Every Neon branch gets its own isolated, copy-on-write storage state. Forking a branch instantly inherits the parent's buckets and objects without duplicating data, and writes on the child branch never affect the parent.