Accoding to this document, each Account in each AWS Region has a limit of 50 tasks and 50 public IP addresses.
With the new architecture, each environment in PASS takes 10 tasks with, currently, 10 public IPs. This means we will be using 30 of the 50 tasks and Public IPs for PASS alone! This account is shared with other services in the Library.
AWS has been known to give more resources with justification. I believe the task limit is fungible, but not public IPV4 addresses are scarce and precious.
I propose two steps:
1) A research period of a week to see if we can get away with running ECS containers behind a NAT Gateway. This should not be an issue with how it works, the containers aren't accessible from the Internet as is. We're just changing their route out to the Internet.
Accoding to this document, each Account in each AWS Region has a limit of 50 tasks and 50 public IP addresses.
With the new architecture, each environment in PASS takes 10 tasks with, currently, 10 public IPs. This means we will be using 30 of the 50 tasks and Public IPs for PASS alone! This account is shared with other services in the Library.
AWS has been known to give more resources with justification. I believe the task limit is fungible, but not public IPV4 addresses are scarce and precious.
I propose two steps:
1) A research period of a week to see if we can get away with running ECS containers behind a NAT Gateway. This should not be an issue with how it works, the containers aren't accessible from the Internet as is. We're just changing their route out to the Internet.