This message was deleted.
# generals
sparse-intern-71089
01/22/2021, 9:04 PMThis message was deleted.
b
brainy-ocean-92780
01/22/2021, 9:18 PMAre your ECS Services all stored within a single stack? Would it be possible to break them out into smaller stacks?
brainy-ocean-92780
01/22/2021, 9:18 PMDisclaimer: I don't have experience with this, just curiousity.
c
chilly-hairdresser-56259
01/22/2021, 9:23 PMIt might also be the way the devs are architecting it too. Which is a take away I still need to have a conversation with them about. But anyways, the way its currently setup is that for each client we onboard for this service, it creates a unique service, using a single dockerfile (We only build this docker file once and deploy to multiple TaskDefinitions & Container Definitions). Which kinda brings us to the 200+ services. For easy onboarding we provided our Team-Leads access to update a nested configuration structure, and we simply loop through them.
chilly-hairdresser-56259
01/22/2021, 9:27 PMSince its a single dockerfile for all the services, if you update that docker file each service needs to update or say they make a code change I now have 200+ services to update. C# Automation API might be able to solve once GA.
chilly-hairdresser-56259
01/22/2021, 9:28 PMGranted still better than doing it by hand!
chilly-hairdresser-56259
01/22/2021, 9:31 PMIts also creating over 1600 resources.
b
billowy-army-68599
01/22/2021, 10:27 PM
ultimately the more resources there are in your stack, the longer it'll take - you're doing a lot of API calls
c
chilly-hairdresser-56259
01/23/2021, 5:14 AMyea figured as much, didn't know if there was anything I could set 🙂
2 Views