It's just a JSON file that you can get from any existing dashboard and then could update with the correct app names and spot fleet info. My only hesitation to not do it is that you presumably wouldn't want to clean them up at the end of a run, though I suppose you could make that a switch with default as True and then set to False and delete yourself (manually or with a Lambda or something). You could imagine IE a Lambda that runs once a week on a cron job that lists all the dashboards with boto3 or aws cloudwatch list-dashboards, gets the "last date modified" from each one via that command, and then if it hasn't been touched in > (14 days?), runs aws cloudwatch delete-dashboards on it
It's just a JSON file that you can get from any existing dashboard and then could update with the correct app names and spot fleet info. My only hesitation to not do it is that you presumably wouldn't want to clean them up at the end of a run, though I suppose you could make that a switch with default as True and then set to False and delete yourself (manually or with a Lambda or something). You could imagine IE a Lambda that runs once a week on a cron job that lists all the dashboards with boto3 or
aws cloudwatch list-dashboards
, gets the "last date modified" from each one via that command, and then if it hasn't been touched in > (14 days?), runsaws cloudwatch delete-dashboards
on it