search

taskforcesh / issues

Taskforce.sh issues
6 stars 0 forks source link

Support for Configurable Parameter Store Keys #103

Open sjrumsby opened 2 years ago

sjrumsby commented 2 years ago

Hello,

We're running Taskforce on-prem, and we would like to be able to host a staging and production version of Taskforce. However, both of these versions of our queue live in the same AWS account, which means that both the staging and production deployments of Taskforce point to the same keys in the Parameter Store.

Is there any way to configure the AMI to be able to namespace the key names so the two versions can run in the same account?

Thanks!

manast commented 2 years ago

Hello,

unfortunatelly the "prefix" for storing Taskforce settings on the parameter store is currently hardcoded, not sure how it could be parametrized though, AFAIK AMIs in AWS do not allow for external arguments :/. So the only workaround would be to either use different regions or different accounts. Incidentally, AWS recommends using different accounts for staging and production for increased security, so that may be something you should also consider. https://docs.aws.amazon.com/controltower/latest/userguide/aws-multi-account-landing-zone.html

manast commented 2 years ago

For the record, there seems to exist a way to read an EC2 instance name, the name could be used as a prefix and so it could be possible to have settings for different instances. However this would be a breaking change for existing installations: https://stackoverflow.com/questions/18338585/how-to-get-the-instance-name-from-the-instance-in-aws

sjrumsby commented 2 years ago

Thank you for the info. We’re planning on separating out our staging / production environments, hopefully I can use this to get it prioritized sooner : ).

I see you added the enhancement label so I won’t close it but feel free to close if you want.

Cheers