vlaaaaaaad/terraform-aws-fargate-samproxy

A Terraform module for running Honeycomb.io's Samproxy on AWS in Fargate

Hey there 👋

I'm Vlad (he/him), a "Professional mistake avoider", more commonly known as Consultant or Strategic Advisor.

---

💼 Work

I'm focused on getting companies to the high-performing levels. I do most of my work on AWS, with Serverless and Containers. I have an intense focus on observability and developer velocity, and I spend most of my time lifting people up.

Think I can help your company? Feel free to reach out!

📤 Featured content

• My "Scaling containers on AWS" blog series: started in 2020 with a blog post, continued with a 2021 re:Invent talk available on YouTube, and ended with a huge blog post for 2022
• My surprisingly popular flowchart: "How should I run containers on AWS"? that tries to compress a bunch of knowledge into an easily understandable way
• My "Fixing EKS DNS" blog post shined a light on NodeLocalDNS, making running Kubernetes clusters at scale way easier. Due to the incredible k8s community, most of this was merged in the upstream documentation 💕
• If you want a glimpse into how much of a golden retriever I am, check out my "Accidentally a hacker" blog post which tells the story of how my passion and energy was combined with alcohol and led to accidentally hacking GitHub
• ... and a bunch of random, unfinished thoughts posted on Twitter that you can more easily read on Typefully

📬 Socials

If you want to stay up to date with what I'm doing, follow me on Twitter at @iamvlaaaaaaad, on Mastodon at @[email protected], or on Polywork at @vlaaaaaaad. You can message me on Twitter or you can send me an email at [email protected].

terraform-aws-fargate-samproxy's Issues

Support config files larger than 8Kb

Description

Due to AWS Fargate not supporting config files, this module uses AWS SSM Parameter store as a "hack" to get around that.

AWS SSM Parameter store has a 8Kb limit so any config files larger than that will fail.

Desired solution

A better way to handle config files.

Notes

We're blocked by aws/containers-roadmap#56. When that's out we'll see what options we have

Use the official Honeycomb Docker image

Description

Due to #1, when the container starts we are using a shell( bash or sh both work) and base64 to decode and create the configuration files for Samproxy.

The upstream image uses FROM scratch which does not have sh or base64. This module is using a secondary image based on the upstream image.

Desired solution

The official upstream image for Samproxy should be used instead of @Vlaaaaaaad's hacky image.

Notes

Blocked by #1

Upgrade to Samproxy 0.10.0

Description

This module should be upgraded to support Samproxy 0.10.0

Desired solution

The module needs to be upgraded to support Samproxy 0.10.0( IIRC there are some breaking changes in the config file format) and needs testing to confirm that 0.10.0 works.

Alternatives and workarounds

N/A

Notes

Creating this issue as I am a bit busy and I don't know when I'll have the time to get to it.

References:

• PR to bump the image version: Vlaaaaaaad/samproxy-fargate-image#4
• Release notes for Samproxy: https://github.com/honeycombio/samproxy/releases/tag/v0.10.0

FieldList rendered as string instead of list

Expected Behavior

FieldList = ["request.method","response.status_code"]

Current Behavior

FieldList = "['request.method','response.status_code']"

Steps to Reproduce

set a FieldList option in samproxy_sampler_configs as suggested in the README:

        {
          "name"  = "FieldList"
          "value" = "['request.method','response.status_code']"
        }