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
Hi,
Is there a current functionality to tag separate deployments of this tool/POC in order to track all/each resource costs associated with one deployment individually, under the same account?
I tried to use the CloudFormation default tagging options by activating them in my account. Not sure how to connect them to my existing deployment. I think I have to add it in the Cloud Formation template and make a new deployment with that change, as per the AWS best practices? Could this be a feature addition to the base repo? A tagging question under the step 5, 'npm run config' step?
One work around would be to have different deployments in different regions and filter the cost with that, from what I understand? Though not really scalable.
Thank you
The text was updated successfully, but these errors were encountered:
I was able to separate out the CF deployment in billing using the prefix option at deployment.
Thanks for the suggestions. I will try them out as I get into further weeds.
For my use cases, I would want to keep them in the same account, for now at least.
Hi,
Is there a current functionality to tag separate deployments of this tool/POC in order to track all/each resource costs associated with one deployment individually, under the same account?
I tried to use the CloudFormation default tagging options by activating them in my account. Not sure how to connect them to my existing deployment. I think I have to add it in the Cloud Formation template and make a new deployment with that change, as per the AWS best practices? Could this be a feature addition to the base repo? A tagging question under the step 5, 'npm run config' step?
One work around would be to have different deployments in different regions and filter the cost with that, from what I understand? Though not really scalable.
Thank you
The text was updated successfully, but these errors were encountered: