Michael Warkentin
Michael Warkentin
@danthegoodman1 you can configure the minimum "provisioned" containers which stay active (paying for mem only, not CPU) - except you can only set that to `>= 1`. It would be...
@stojanovic thanks for looking into it! A couple of thoughts: 1. This seems like the only way that would work today, but seems like it might be quite complicated -...
@pavneeta any updates on where this is at?
Here's an old article covering how to do this manually (before tagging and usage were available): https://aws.amazon.com/blogs/compute/measuring-service-chargeback-in-amazon-ecs/ You can see how it might be a bit overwhelming to try to...
Having an “unused” dollar cost like Corey mentioned would be ideal (similar to the catch all “no tag key” category when grouping spend by tag). It would be a really...
There's a new repo with some automation for this: https://github.com/aws-samples/ecs-chargeback-cloudformation
It seems like the build environment could be CodeBuild behind the scenes - it would be nice if some of these other instance types were available: 
@kevcam4891 yes, we'd also be happy to pay more for more CPU (ARM could be really interesting too..) to throw at our big webpack builds.
How do you do that?
@swaminator We have a similar (but not directly related issue) where we would like to replace an email-validated ACM certificate with a DNS-validated certificate, however our Amplify Console applications are...