Waiting for Deployment
After deploying, you need to wait for your app to start before it’s accessible. Ask your AI assistant:“Wait for my deployment to complete”
Viewing Logs
Ask your AI assistant:“Show me the logs for my app”
- Application stdout/stderr
- Startup messages
- Error traces
- Request logs (if your app logs them)
Checking Deployment Status
Ask your AI assistant:“What’s the status of my deployment?”
- Infrastructure provisioning status: Ready or provisioning
- Service running status: Running, Pending, Stopped, or Error
- Public IP: Your application’s public IP address
- Resource details: Status of each storage bucket and secret, including bucket IDs
Example status response
Example status response
Infrastructure: Ready
Service Status: Running
Deployment Revision: 3
Public IP: 52.xxx.xxx.xxxResources:
Service Status: Running
Deployment Revision: 3
Public IP: 52.xxx.xxx.xxxResources:
- StorageBucket “uploads” - Available (aws_id: bucket-abc123)
- Secret “STRIPE_API_KEY” - Available
Debugging Failed Deployments
If your deployment isn’t working, ask:“My app isn’t starting. Can you help debug?”
- Check status - Identify if the service is in Error, Stopped, or stuck in Pending
- Get logs - Retrieve recent logs to find error messages
- Analyze - Identify the likely cause
- Suggest fixes - Provide actionable solutions
Common Issues
Service in 'Stopped' or 'Error' state
Service in 'Stopped' or 'Error' state
Your application crashed. Check the logs for:
- Unhandled exceptions
- Missing configuration or secrets
- Failed connections to external services
Service stuck in 'Pending'
Service stuck in 'Pending'
The container is starting but not becoming healthy. Common causes:
- App not listening on the expected port (default: 8080)
- App taking too long to start
- Health check failing
port_mappings in neptune.json.Container exits immediately
Container exits immediately
The process exits right after starting. Check for:
- Missing dependencies
- Configuration errors
- Startup script issues
Missing configuration or secrets
Missing configuration or secrets
Your app expects configuration that isn’t available.Fix: Add secrets to your neptune.json and update your code to fetch them from AWS Secrets Manager:Then ask your AI assistant to set the secret value and update your code.
Best Practices
Add structured logging
Add structured logging
Use structured logging (JSON) for easier debugging:
Log startup information
Log startup information
Log important information when your app starts:
Handle errors gracefully
Handle errors gracefully
Log errors with stack traces: