https://github.com/leosunmo/tagd

AWS ASG Tagging Daemon
https://github.com/leosunmo/tagd

Last synced: about 1 month ago
JSON representation

AWS ASG Tagging Daemon

• Host: GitHub
• URL: https://github.com/leosunmo/tagd
• Owner: leosunmo
• Created: 2020-07-04T07:01:19.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-07-10T01:06:51.000Z (over 4 years ago)
• Last Synced: 2025-01-04T04:42:06.019Z (about 1 month ago)
• Language: Go
• Size: 54.7 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Tagd

Tagd is a simple service make sure your AWS Autoscaling group (ASG) instance's disks are tagged correctly.

Instances created by ASGs can inherit the tags from the ASG, but it does not travel down to the instances' disks (unless you use Launch Templates).

The usual solution is to set up notifications on your ASGs and have something like a Lambda that tags the disks upon ECS_INSTANCE_LAUNCH events. This works fine most of the time.

If you don't want to use Lambdas or you can't easily set up SNS/SQS notifications on the ASGs, Tagd will do all of it for you.

An example is if you use [Kops](https://github.com/kubernetes/kops/). It currently doesn't support creating notificaions on the auto-generated ASGs for the Kubernetes masters and node groups. Tagd will add them for you.

## Usage

Config file example:

```yaml

tagConfig:

  - asgName: "my-asg"

    tags:

      KubernetesCluster: the-test-cluster

      "corp:department": development

      cool-tags: "yes"

  - asgName: "my-other-asg"

    tags:

      elasticsearch: "website-search"

      "corp:department": sales

```

Compile and run:

```

make build

bin/tagd -l info --sqs-queue-name asg-scaling-events --sns-topic-arn 'arn:aws:sns:us-west-2:1234567890:asg-scaling-events'

```

## TODO

- [ ] Add other handlers, for example tagging Kubernetes PVCs

- [ ] Make sns/sqs per-asg in config file

- [ ] tests using mocks