---
title: "Discussion on \"Why Did We Start Using AWS Secrets Manager To Store Sensitive Data?\" | Hashnode"
description: "Discussion on \"Why Did We Start Using AWS Secrets Manager To Store Sensitive Data?\". 👋 Hi. I'm Sunil.\nI work at a startup during the day and as an indie developer at night.\nIn this article I'm going to talk about why we started using AWS Secrets Manager to manage sensitive data like passwords, keys, tokens etc used in our applicatio..."
url: "https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Did We Start Using AWS Secrets Manager To Store Sensitive Data?](https://sunilkumarc.in/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data?utm_source=hashnode&utm_medium=feed)

👋 Hi. I'm Sunil. I work at a startup during the day and as an indie developer at night. In this article I'm going to talk about why we started using AWS Secrets Manager to manage sensitive data like passwords, keys, tokens etc used in our applicatio...

Sep 18, 2020 · 4 min read · sunilkumarc.in  
Updated May 7, 2021  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#security](https://hashnode.com/tag/security)
-   [#startups](https://hashnode.com/tag/startups)

## Written by

[Sunil Kumar](https://hashnode.com/@sunilkumarc)

@sunilkumarc · Bangalore, India.

  
[View profile](https://hashnode.com/@sunilkumarc)

I am a lead backend developer at a unicorn startup in India. I freelance in my free time and teach people how to make passive income on the internet. You can also expect technical articles, how-to tutorials, system designing concepts and anything tech in general on my blog.

## Responses 3

Markdown supported · ⌘↵ to post

[Kimmy Kervel](https://hashnode.com/@kimmykervel)

[Oct 5, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f7afbb99c3b6e41012183bc)

Nice Information ! You have shared  
I am a [Web developer](https://www.geitpl.com/) and i like to read blog related to my industry like this

[Pete](https://hashnode.com/@PipelinePete)

[Sep 23, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f6aa9e91c935b2e4c61645d)

Curious as to why you're not using Parameter Store for all the other config values? These can be implemented as infra-as-code and if they aren't secrety they can be committed alongside the application (similar to how you're currently doing it)

[Sunil Kumar](https://hashnode.com/@sunilkumarc)

[Sep 23, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f6aa9e91c935b2e4c61645d#reply-5f6afddacbf0b22e6d444149)

There are multiple reasons why we're not doing this.

-   If we manage other config values as infra-as-code, then we will have to update our task definition every time there's a new configuration to be added or every time we want to modify existing values, which mean running our terraform code.
    
-   Having configuration in consul gives us the to modify config values on consul first just restart our service on AWS ECS to consider the new config values.
    
-   Also at this point we do not manage secrets in secrets manager (not sure if it's possible) through infra-as-code. We manually add, update values since secrets generally do not change frequently. So adding all the config values manually was not a viable option for us.
    

[Pete](https://hashnode.com/@PipelinePete)

[Sep 23, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f6aa9e91c935b2e4c61645d#reply-5f6b06961c935b2e4c616869)

[Sunil Kumar](https://hashnode.com/@sunilkumarc)

1.  Wouldn't you need to update code anyways when there are new values?
2.  Not sure I see the distinction between the two; if its in code and you manually change in consul, you could just do the same with Param Store. But even if a config value results in a restart, its still a fully automated and auditable change.
3.  Yes, you can define the secret, but manually add in the value as a side process. If the secret needed (or would benefit) regular rotation then you can enable it.

[Sunil Kumar](https://hashnode.com/@sunilkumarc)

[Sep 24, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f6aa9e91c935b2e4c61645d#reply-5f6c2dc7136a1642fa93afc4)

[Pete](https://hashnode.com/@PipelinePete) As I had mentioned earlier we currently manually add each of the secrets into SM. Adding all the configurations like this was not realistic since we generally have lot of config data for each service.

Also this can be error prone because of the interface AWS currently has to add secrets (my opinion)

[JonasW](https://hashnode.com/@jonasw)

[Sep 22, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f69a21935d6463d2b5fa358)

Thanks for sharing your experience with storing secrets. I have a question, what about configs (not secrets). Why do you store configuration data as files in repo and then syncing it to consul?

[Sunil Kumar](https://hashnode.com/@sunilkumarc)

[Sep 22, 2020](https://hashnode.com/posts/why-did-we-start-using-aws-secrets-manager-to-store-sensitive-data/5f64b8ab96b4a436fe136101/comment/5f69a21935d6463d2b5fa358#reply-5f69a9f56dfc523d0a89551a)

Well you don't need to. You just need to find a way to upload your configuration data to consul server before deploying your services.

In our case each team keeps this data in their own Github repositories and run a Jenkins job which in turn uploads the data to consul server.

This process works best for us considering there are multiple teams and each team doesn't need to have access to other team's configurations.
