You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add AWS S3 bucket as an option for the destination path of the rendered file by Infisical Agent.
It would require extra environment variables for authenticating the Agent to AWS and then upload the rendered file to the specified S3 bucket.
Why would it be useful?
Using AWS S3 buckets as the storage location of .env files is quite common, especially for applications deployed on AWS ECS.
The method of feeding secrets to applications on ECS described in the docs requires changes to the existing task definitions that use S3 as the source of the .env file, which is supported by ECS and easily adopted. It also avoids any issues with EFS and ECS tasks regarding regions.
Additional context
Currently, I am using a custom script to achieve the same result.
The Agent renders the file, executes the script, the script uploads the rendered file to my S3 bucket.
It would be nice if this functionality was built-in.
The text was updated successfully, but these errors were encountered:
Feature description
Add AWS S3 bucket as an option for the destination path of the rendered file by Infisical Agent.
It would require extra environment variables for authenticating the Agent to AWS and then upload the rendered file to the specified S3 bucket.
Why would it be useful?
Using AWS S3 buckets as the storage location of
.env
files is quite common, especially for applications deployed on AWS ECS.The method of feeding secrets to applications on ECS described in the docs requires changes to the existing task definitions that use S3 as the source of the
.env
file, which is supported by ECS and easily adopted. It also avoids any issues with EFS and ECS tasks regarding regions.Additional context
Currently, I am using a custom script to achieve the same result.
The Agent renders the file, executes the script, the script uploads the rendered file to my S3 bucket.
It would be nice if this functionality was built-in.
The text was updated successfully, but these errors were encountered: