deepfence / deepfence/ThreatMapper

central console via AWS ECS

Open
#1,309 0 comments 0 reactions 0 assignees View on GitHub
enhancement needs-triage
Dominant language
TypeScript
Stars
5.3k
Forks
631
PR merge metrics
No merged PRs in 30d

Description

**Additional context**
It looks like there's a docker-compose already, https://github.com/deepfence/ThreatMapper/blob/master/deployment-scripts/docker-compose.yml

**Is your feature request related to a problem? Please describe.**
It would be nice to have a deployment option for the console that uses ECS instead of EKS.

**Describe the solution you'd like**
a list of containers that need to be persistent vs booted just once (e.g., deepfence_init_ce), possibly a list of gotchas, documented.

**Describe alternatives you've considered**
EKS would be more complicated than necessary, EC2 would be more manual than warranted.

**Components/Services**

- [x] UI/Frontend
- [x] API/Backend
- [ ] Agent
- [x] Deployment/YAMLs
- [ ] CI/CD Integration
- [ ] Other (specify)

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.