Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jedi4ever/ecs-watch
Simple Service Discovery for use in an AWS ECS cluster
https://github.com/jedi4ever/ecs-watch
Last synced: about 1 month ago
JSON representation
Simple Service Discovery for use in an AWS ECS cluster
- Host: GitHub
- URL: https://github.com/jedi4ever/ecs-watch
- Owner: jedi4ever
- Created: 2016-08-02T18:16:23.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2016-08-11T11:44:20.000Z (over 8 years ago)
- Last Synced: 2024-06-20T17:48:57.365Z (6 months ago)
- Language: Go
- Homepage:
- Size: 59.6 KB
- Stars: 29
- Watchers: 2
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Description
**CAVEAT!** this is WIP for now - soon to be released
When you want to run microservices inside of an ECS cluster , the easiest/standard/recommended way is to register Services with ELBs.
You can register the ELBs in DNS and each service is instanly available. No need for a service discovery.
As the number of microservices grow , so increases the cost of the ELBs. Especially in Test/Staging environment this can get quite costly where multiple environment are running on the same cluster.
The alternative is to use a discovery service and a reverse proxy like (Nginx, HaProxy, Traefik, Kong, Fabio).
Most tools/examples I found used Consul. But then I thought, why duplicate the ECS state in consul? That way you can avoid running a consul cluster.
## Report
```
NAME:
ecs-watch report - reports all containers and ports
USAGE:
ecs-watch report [command options] [arguments...]
OPTIONS:
--ecs-cluster value (default: "default") [$ECSWATCH_ECS_CLUSTER]
--aws-region value (default: "eu-west-1") [$ECSWATCH_AWS_REGION]
```
```
+-----------+----------+---------------+----------------+-----------+---------------------+-----------+-------------------------+---------+--------+----------+--------------------+
| NAME | HOSTPORT | CONTAINERPORT | PUBLICIP | PRIVATEIP | INSTANCEID | IMAGE | VIRTUALHOST | STATUS | FAMILY | REVISION | CLUSTER |
+-----------+----------+---------------+----------------+-----------+---------------------+-----------+-------------------------+---------+--------+----------+--------------------+
| jenkins-a | 32778 | 80 | 52.209.248.211 | 10.0.4.42 | i-08d46a56b977b8a62 | httpd:2.4 | www.smalltownheroes.be | RUNNING | apache | 12 | staging-asg |
| jenkins-b | 32779 | 80 | 52.209.248.211 | 10.0.4.42 | i-08d46a56b977b8a62 | httpd:2.4 | www3.smalltownheroes.be | RUNNING | apache | 12 | staging-asg |
+-----------+----------+---------------+----------------+-----------+---------------------+-----------+-------------------------+---------+--------+----------+--------------------+
```
## Generate file using Template
The use of *elb-watch* to have a command similar to docker-gen/nginx-proxy where a template is populated and a signal is send to a container.
instead of reading the state from Consul, it reads the state from ECS.
```
NAME:
ecs-watch track - tracks changes inside an ecs cluster
USAGE:
ecs-watch track [command options] [arguments...]
OPTIONS:
--track-interval value (default: 5s) [$ECSWATCH_TRACK_INTERVAL]
--only-once [$ECSWATCH_ONLY_ONCE]
--ecs-cluster value (default: "default") [$ECSWATCH_ECS_CLUSTER]
--aws-region value (default: "eu-west-1") [$ECSWATCH_AWS_REGION]
--template-generate [$ECSWATCH_TEMPLATE_FILE]
--template-input-file value [$ECSWATCH_TEMPLATE_INPUT_FILE]
--template-output-file value [$ECSWATCH_TEMPLATE_OUTPUT_FILE]
--docker-notify [$ECSWATCH_NOTIFY_CONTAINER]
--docker-signal value (default: "SIGHUP") [$ECSWATCH_DOCKER_SIGNAL]
--docker-container value [$ECSWATCH_DOCKER_CONTAINER]
--docker-endpoint value (default: "unix:///var/run/docker.sock") [$ECSWATCH_DOCKER_ENDPOINT]
```
## Route53 sidekick
The use of *elb-watch* to find the connection details of container (ip/port) and update a record in route53.
This is useful as a side-kick for services that are not http based (for example your redis server)
# Related projects
-
-
-
-
-
-
-
-
# Reading
-
-
-
-
-
-
-
-
-