Securely store API keys and sensitive configuration
Neptune Secrets provide secure storage for API keys, tokens, and other sensitive configuration. Secrets are stored in AWS Secrets Manager and accessed at runtime using the AWS SDK.
Creates an AWS Secrets Manager secret with a physical name (e.g., neptune-abc123-STRIPE_API_KEY) for global uniqueness
Configures all necessary IAM permissions so your running service can access it
Returns the physical secret name to your AI assistant
The physical secret name is different from the logical name you define in neptune.json. For example, if you name your secret STRIPE_API_KEY, the actual AWS secret might be called neptune-abc123-STRIPE_API_KEY.
All permissions are pre-configured, so you can use boto3 (or other AWS SDKs) to retrieve secrets without any credential configuration.
Python
Node.js
Rust
Copy
Ask AI
import boto3 import json # Your AI assistant will provide this physical secret name SECRET_NAME = "neptune-abc123-STRIPE_API_KEY" sm = boto3.client("secretsmanager") response = sm.get_secret_value(SecretId=SECRET_NAME) secret_value = response['SecretString'] # Use the secret import stripe stripe.api_key = secret_value
Your AI assistant knows the physical secret name after provisioning and can write the code for you with the correct secret name already filled in.
When you ask your AI assistant to set a secret, it will prompt you to enter the value securely. The value is never displayed or logged.
“Set my STRIPE_API_KEY secret”
AI Assistant: I’ll set the STRIPE_API_KEY secret. Please provide the value when prompted.You enter the value securelyAI Assistant: Secret ‘STRIPE_API_KEY’ has been set. Redeploy your application to use the new value.
After setting or updating a secret, you need to redeploy your application for the changes to take effect.