Skip to main content
Neptune can provision and manage cloud resources alongside your application deployments. Resources are defined in your neptune.json configuration and automatically wired to your application.

Available Resources

Storage Buckets

S3-compatible object storage for files and assets

Secrets

Secure storage for API keys and sensitive configuration

Databases

Managed Postgres databases

Adding Resources

The easiest way to add resources is to ask your AI assistant:
“Add an S3 bucket for user uploads to my project”
Or you can define them directly in your neptune.json:
neptune.json

Resource Lifecycle

1

Define

Add resources to your neptune.json configuration (or ask your AI assistant to add them)
2

Provision

Neptune provisions the cloud resources and returns the physical resource names to your AI assistant.
3

Code

Write your application code using the physical resource names, or let your AI assistant write it for you.
4

Deploy

Your app is deployed with all IAM permissions pre-configured to access its resources.
Your AI assistant handles this flow automatically - it provisions resources, knows the physical names, and can write code that accesses them correctly.

How Resources Work

When Neptune provisions a resource, it creates:
  1. A unique physical name - e.g., neptune-abc123-uploads for global uniqueness
  2. IAM permissions - Your service automatically has access to its own resources
  3. No manual credential setup - Just use standard AWS SDKs like boto3
Your AI assistant receives the physical resource names after provisioning and can use them when writing code for you.

Example: Web App with Storage and Secrets

Here’s a complete configuration for a typical web application:
neptune.json
Your application can then access these resources using standard AWS SDKs:

Managing Resources

Ask your AI assistant to help with common resource operations: