start

This guide shows you how to start a stopped Datafye Trading Environment in AWS.

Prerequisites

Before you begin, ensure:

• You have previously provisioned an AWS Trading Environment (see Provision an AWS Trading Environment)

• The deployment is currently stopped

• AWS credentials are configured (see AWS Setup)

Start Command

Use the following command to start your AWS Trading Environment:

datafye trading aws start --name <deployment-name> --profile <aws-profile>

Parameters

Required Parameters

Parameter	Description
--name <name>	Name of the deployment to start
--profile <profile>	AWS CLI profile to use

Run datafye help trading aws start to see the complete parameter list and usage.

Example

Start a Trading Environment named my-paper-trading:

datafye trading aws start \
  --name my-paper-trading \
  --profile datafye

Start Process

When you start the deployment, the CLI will:

1. Verify credentials - Check AWS authentication

2. Locate deployment - Find the deployment by name

3. Start EC2 instances - Power on all stopped virtual machines

4. Wait for boot - Monitor instance startup

5. Start services - Bring up all Datafye services

6. Reconnect to broker - Re-establish broker connections

7. Run health checks - Verify all services are healthy

8. Display endpoints - Show deployment URLs

Starting a deployment typically takes 2-5 minutes as EC2 instances boot and services initialize. This is much faster than provisioning.

After Starting

Once the start process completes, you'll see:

• Deployment status confirmation

• API base URLs for accessing Datafye services

• WebSocket endpoints for real-time data and execution updates

• Broker Connector endpoints

• MCP server endpoint (Full Stack only)

Your deployment will be accessible via the URLs provided.

Validate Connectivity

Test your deployment with:

# Check Data Cloud health (replace with your deployment endpoint)
curl http://<deployment-endpoint>/datafye-api/v1/health

# Check Broker Connector health
curl http://<broker-endpoint>/broker-api/v1/health

Your AWS Trading Environment is now running!

Troubleshooting

AWS Credential Errors

If you see authentication errors:

1. Verify your AWS profile: aws sts get-caller-identity --profile datafye

2. Ensure credentials have necessary permissions

3. Check you're using the correct profile name

Deployment Not Found

If you see an error that the deployment doesn't exist:

1. Verify the deployment name: datafye trading aws list --profile datafye

2. Ensure you're using the correct AWS profile

3. Check the deployment wasn't deprovisioned

Instance Start Failures

If EC2 instances fail to start:

1. Check AWS service status in the region

2. Verify instance states in EC2 console

3. Ensure AWS account has no billing issues

4. Contact Datafye support if issues persist

Broker Connection Issues

If broker connections fail on start:

1. Verify broker credentials haven't expired or been revoked

2. Check broker service status

3. Ensure environment variables with credentials are still set

4. Review Broker Connector logs for specific errors

5. Verify broker account is still active

Service Health Check Failures

If services fail health checks after starting:

1. Wait a few more minutes for full initialization

2. Check instance system logs in EC2 console

3. Verify security group rules allow traffic

4. Contact Datafye support if services don't become healthy

Related Commands

• Provision an AWS Trading Environment - Create a new deployment

• Stop an AWS Trading Environment - Stop the running deployment

• Deprovision an AWS Trading Environment - Remove the deployment

---

Last updated: 2025-10-22