BDOT Collector Architecture
Both Fargate and EC2 deployment options include:
VPC with Public Subnets - Network isolation with internet access
Security Groups - Controlled access to collector ports (
4317
and4318
)CloudWatch Logging - Centralized logging and monitoring
Auto Scaling - Automatic scaling based on demand
Key Features
Container Configuration
BDOT Collector Image:
ghcr.io/observiq/bindplane-agent
OpAMP Protocol: Connects to Bindplane Server via OpAMP
Automatic Configuration: Receives configurations from Bindplane Server
Persistent Storage: Maintains manager.yaml configuration
Ports and Services
4317
: OTLP gRPC receiver4318
: OTLP HTTP receiver
Environment Variables
OPAMP_ENDPOINT
: Bindplane Server OpAMP endpointOPAMP_SECRET_KEY
: Collector authentication keyOPAMP_LABELS
: Collector labels for identification
Prerequisites
Before deploying, ensure you have:
AWS CLI v2.x installed and configured
Valid AWS account with appropriate permissions
Bindplane Server running (self-hosted or cloud)
Collector secret key from your Bindplane Server
Getting Your Secret Key
Navigate to your Bindplane Server UI
Go to Agents → Install Agent
Choose Linux platform
Copy the
secret-key
from the installation instructions
Configuration
OpAMP Endpoint URLs
Bindplane Cloud:
wss://app.bindplane.com/v1/opamp
Self-hosted (HTTP):
ws://your-server:3001/v1/opamp
Self-hosted (HTTPS):
wss://your-server:443/v1/opamp
Monitoring and Troubleshooting
CloudWatch Logs
# View collector logs
aws logs tail /ecs/collector --follow
Common Issues
Collector not appearing: Check OpAMP endpoint and secret key
Connection failures: Verify network connectivity and security groups
High resource usage: Scale up resources or add more instances
Scaling
Manual Scaling
# Update desired count
aws ecs update-service \
--cluster your-cluster \
--service collector-service \
--desired-count 3
Auto Scaling
Both deployment options support Application Auto Scaling for automatic scaling based on CPU/memory utilization.
Last updated
Was this helpful?