Hacker GitHub

← All repos

segmentio/chamber

View on GitHub ↗ ★ 2,614 Go

CLI for managing secrets

13 mentions on Hacker News by 13 people: 1 story, 12 comments · first 2017-09-25 · latest 2024-07-12

Mentions per year 13 mentions · busiest year 2020 (4)
20082026
AllStoriesComments NewestTopOldest
  1. …separate agent situation isn’t something secure enough to satisfy most companies these days. [0] https://github.com/segmentio/chamber [1] https://www.doppler.com/
    comment by slaughtr · 2024-07-12 · in AWS Secrets Manager Agent
  2. Building on this I’ve found https://github.com/segmentio/chamber to be super useful
    comment by thenipper · 2023-03-05 · in Ask HN: Secure and simple way for secret/credential management in a startup?
  3. …and can values can be rendered in Cloudformation templates natively. Too hard? Maybe try Chamber https://github.com/segmentio/chamber It has support for multiple backends and can render secrets in lots of different formats.
    comment by Spivak · 2021-12-15 · in Using Route53 as a Key Value Store in GitHub Actions
  4. Would love to test it out! Have been evaluating Chamber ( https://github.com/segmentio/chamber ) to solve same/similar problem. But Leapp has UI(cool looking!), so it's an obvious advantage. Would be keen to hear what other differences…
    comment by toinbis · 2021-06-30 · in Show HN: Leapp – Multi-cloud credentials tool for developers
  5. I agree that AWS Parameter store isn't great... that's why we use Chamber: https://github.com/segmentio/chamber Chamber is an open source wrapper for AWS Parameter Store. You add a secret by doing: `chamber write ENV_NAME SECRET_NAME…
    comment by temuze · 2020-10-08 · in Launch HN: Doppler (YC W19) – Easily manage your env vars and secrets
  6. The web UI is bad, but tools like chamber ( https://github.com/segmentio/chamber ) are excellent, so there's no need to deal with the web UI.
    comment by Lazare · 2020-07-14 · in Don't use ENV variables for secret data (2017)
  7. …happy with it so far. We store all configuration (including secrets) using it. We started by using https://github.com/segmentio/chamber/ , but because of the way we decided to structure our secrets we decided to write a clone of it…
    comment by katnegermis · 2020-07-13 · in Don't use ENV variables for secret data (2017)
  8. …PASSWORD hunter2` to write a new secret or `chamber list serviceA` to list set secrets. [1] https://github.com/segmentio/chamber
    comment by dmlittle · 2019-02-08 · in Ask HN: How is your company storing secrets in EC2?
  9. …not on AWS, EnvKey looks like a reasonable solution with ease of use. Just don't misplace the key! https://github.com/segmentio/chamber/blob/master/README.md
    comment by jeffnappi · 2018-03-13 · in Launch HN: EnvKey (YC W18) – Smart Configuration and Secrets Management
  10. Or chamber. https://github.com/segmentio/chamber
    comment by caust1c · 2018-03-12 · in Secret management design decisions: theory plus an example
  11. …to set up, use, and not think about it. It's great for integrating with AWS IAM and whatnot. [1]: https://github.com/segmentio/chamber [2]: https://aws.amazon.com/blogs/mt/the-right-way-to-store-secre...
    comment by jamesmishra · 2018-02-06 · in Ask HN: How does your company manage secrets like API keys?
  12. a tool which pairs well with parameter store is https://github.com/segmentio/chamber/ . it's a nice interface over the awscli commands that save you a lot of typing. definitely worth looking at as it also saves you the hassle of dealing…
    comment by nsfmc · 2017-09-25 · in Show HN: EnvKey – securely manage API keys, credentials, and config