# AWS Parameter Store path format

**URL:** <https://community.doppler.com/t/aws-parameter-store-path-format/1209>\
**Category:** Need Help\
**Tags:** integration\
**Created:** [June 24, 2023, 11:20pm UTC](https://community.doppler.com/t/aws-parameter-store-path-format/1209 "2023-06-24T23:20:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablogq](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/pablogq/32/816_2.png) [@pablogq](https://community.doppler.com/u/pablogq)\
**Post date:** [June 24, 2023, 11:20pm UTC](https://community.doppler.com/t/aws-parameter-store-path-format/1209/1 "2023-06-24T23:20:55Z")

</div>

Hello! I’m working on an application using [SST](https://sst.dev/). They provide a way to keep secrets in AWS Parameter Store. You can add them by using the sst cli and access them in your application using a library they provide too.

I would like to use Doppler as a single source of truth for the application secrets, so I was thinking in using the Doppler integration to add the secrets to the store and access them using the SST library, removing the need to add the secrets manually using the SST cli.

SST adds the secrets to the store in a path with the following format:

```auto
/sst/<app-name>/<stage>/Secret/<secret-key>/value

```

An example would be:

```auto
/sst/app/production/Secret/MY_SECRET_KEY/value

```

As you can see, they add a `/value` at the end of the path. I was wondering if there is a way I can replicate that path using the Doppler integration, like some kind of interpolation were I can provide a token that represents the secret name and it will be replaced by said name in the store path.

For example, if I use `/sst/app/production/Secret/{secret-name}/value` as path in the integration setup and I have a secret named `MY_SECRET` in my Doppler configuration, it will be saved under the path `/sst/app/production/Secret/MY_SECRET/value` in the AWS Parameter Store. Is that possible?

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [July 5, 2023, 9:15pm UTC](https://community.doppler.com/t/aws-parameter-store-path-format/1209/2 "2023-07-05T21:15:51Z")

</div>

Hi @pablogq!

Welcome to the Doppler Community!

Unfortunately, there’s not currently a way to use custom paths like this. I’ll go ahead and pass this idea along to our team for consideration though!

One potential alternative would be to just use Doppler directly. We have a library called [gitops-secrets-nodejs](https://github.com/DopplerHQ/gitops-secrets-nodejs) that might help you out here. Might be worth giving it a look to see if it will work for you. If you need help or have questions after taking a look, let me know and I’ll see how I can help!

Regards,  
-Joel

---

<div class="post-metadata">

**Author:** ![pablogq](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/pablogq/32/816_2.png) [@pablogq](https://community.doppler.com/u/pablogq)\
**Post date:** [July 5, 2023, 10:32pm UTC](https://community.doppler.com/t/aws-parameter-store-path-format/1209/3 "2023-07-05T22:32:20Z")

</div>

hey @watsonian!

I see, I would love to have that option, thank you for passing the idea along.

I will check out the library you pointed out and see if it fits our needs, thanks for sharing it!

---

<div class="post-metadata">

**Author:** ![nahtnamhq](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/nahtnamhq/32/915_2.png) [@nahtnamhq](https://community.doppler.com/u/nahtnamhq)\
**Post date:** [October 3, 2023, 6:20am UTC](https://community.doppler.com/t/aws-parameter-store-path-format/1209/4 "2023-10-03T06:20:25Z")

</div>

Hello! I’d also like to add my vote to this issue. I just wanted to say that SST (specifically open-next) is gaining in popularity as an alternative in Vercel and they require that `/value` suffix
