---
title: Storing ENV Variables in Secrets Manager
url: https://www.tines.com/docs/self-hosted/deploying-tines/aws-fargate/storing-env-variables-in-secrets-manager/
updated: 2026-03-18T08:42:23+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt) › [Self-Hosted](https://www.tines.com/llm/docs/self-hosted.md) › [Deploying Tines](https://www.tines.com/llm/docs/self-hosted/deploying-tines.md) › [AWS Fargate](https://www.tines.com/llm/docs/self-hosted/deploying-tines/aws-fargate.md)*

# Storing ENV Variables in Secrets Manager

*[View on tines.com](https://www.tines.com/docs/self-hosted/deploying-tines/aws-fargate/storing-env-variables-in-secrets-manager/)*

If you'd like to, you can provide environment variables to your `tines-app` and `tines-sidekiq` task definitions through AWS Secrets Manager. This is not essential, but can be done for improved security. 

First, [create a new secret](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_secret.html) in AWS Secrets Manager for the environment variable using the name of the variable and its value as the key-value pair. Next, in ECS console, navigate to the task definition that will use the environment variable, and create a new revision. Under the `Environment variables` section, click `Add environment variable`. For consistency, use the same `Key` that you used for the secret. The `Value type` should be `ValueFrom` , and the `Value` is the `Secret ARN` from the Secrets Manager. 

You might also be interested in storing your database credentials in the Secrets Manager. See [here](https://docs.aws.amazon.com/secretsmanager/latest/userguide/create_database_secret.html) for information on how to do that.