Services Management
Manage individual ECS services for a linked AWS connection: inspect state, queue manual actions, and configure cost-saving schedules.
Overview
From the dashboard, select a linked AWS connection and cluster, then click a service name to open the Service Configuration Panel.
The panel includes:
- Service metadata (launch type, architecture, task and cost details)
- Service control (current status and manual start/stop actions)
- Configuration tab (cost-saving rule management)
- History tab (shutdown/startup records and savings)
Viewing Services
- Select AWS account connection
- Select cluster
- Find a service in the Services Table
- Click service name to open detailed controls
Services Table Columns
| Column | Description |
|---|---|
| Service Name | Service name with status dot; Manual badge indicates no active schedule |
| Tasks | Running versus expected task count with autoscaling range when available |
| Resources | vCPU, memory, and launch type |
| Cost Saving | Estimated savings badge when rule is enabled |
| Monthly Cost | Monthly cost estimate for current configuration |
| Actions | Start and Stop buttons based on status |
Service Configuration Panel
Service Details Card
| Field | Description |
|---|---|
| Launch Type | Fargate or EC2 |
| Operating System | Runtime OS from task definition |
| Architecture | CPU architecture such as X86_64 or ARM64 |
| Task Count | Desired task count with autoscaling min-max context |
| vCPU per Task | vCPU allocation per task |
| Memory per Task | Memory allocation per task |
| Cost per Hour | Estimated hourly runtime cost |
| Est. Monthly Cost | Estimated monthly runtime cost |
Service Control Card
Status colors:
- Green - Running
- Yellow - Starting
- Red - Stopped or stopping
- Gray - Unknown
A Manual badge means no active cost-saving rule is stored for this service.
Start Service
- Enabled when service is stopped or unknown
- Queues a manual startup action
- Restores service to configured expected task count
Starting a service can take several minutes depending on image pull and task startup time.
Stop Service
- Enabled when service is running or starting
- Queues a manual stop action
- Scales desired count to zero
Stop actions affect service availability immediately. Use carefully in shared clusters.
Configuration Tab
Enable Cost Saving
Turn on Enable Cost Saving to store and enforce a schedule for this service.
When disabled, the service remains manually managed and schedule automation is inactive.
Desired Task Count
Set the desired task count to restore at startup. Allowed values follow autoscaling constraints.
Schedule Fields
| Field | Description |
|---|---|
| Startup Time (UTC) | Daily time to start the service |
| Shutdown Time (UTC) | Daily time to stop the service |
| Days | Active weekdays for the schedule |
The UI validates and previews cron expressions behind the schedule.
Estimated Monthly Savings
Savings estimate updates as schedule values change, based on expected runtime reduction and task cost profile.
Save or Clear
- Click Save to persist enablement, desired task count, and schedule
- Click Clear rule to remove automation for this service
Only one schedule rule is stored per service. For broad consistency, use cluster-wide schedule application first.
History Tab
The History tab tracks shutdown/startup cycles.
| Column | Description |
|---|---|
| Shutdown | Stop timestamp and trigger type (scheduled or manual) |
| Startup | Start timestamp and trigger type |
| Saved Duration | Total downtime for the cycle |
| Amount Saved | Estimated savings for that downtime period |
Troubleshooting
Service will not start
- Check ECS capacity, networking, and task definition health
- Confirm the linked AWS connection remains verified
- Review runtime action errors in logs/history
Service stops unexpectedly
- Check active schedule rule
- Review manual action history
- Inspect autoscaling interactions
Next Steps
- Rules Configuration - Fine-tune schedule behavior
- Monitoring & Analytics - Track execution and savings trends