The AWS Copilot CLI is a tool for developers to build, release and operate production ready containerized applications on AWS App Runner or Amazon ECS on AWS Fargate.
I'm not sure if this is a bug, hence why it's a feature request.
Basically we have four existing Copilot managed applications in our account with two environments each. I went to make another one and ran into a "Resource limit exceeded" error on the "LogResourcePolicy" when I tried to make one of the environments.
Looking into this, it seems like there's a hard limit of 10 LogResourcePolicy's per region per account (https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/cloudwatch_limits_cwl.html). According to the docs this limit can't be raised, meaning you won't ever be able to make more than 10 Copilot environments in a region per account if each environment requires a LogResourcePolicy.
Proposal
I have no idea how or if this could be fixed because I honestly don't know what the LogResourcePolicy is for, I'm just flagging it as a potential issue or something to document maybe.
huanjani
commented
5 months ago
Describe your idea/feature/enhancement
I'm not sure if this is a bug, hence why it's a feature request.
Basically we have four existing Copilot managed applications in our account with two environments each. I went to make another one and ran into a "Resource limit exceeded" error on the "LogResourcePolicy" when I tried to make one of the environments.
Looking into this, it seems like there's a hard limit of 10 LogResourcePolicy's per region per account (https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/cloudwatch_limits_cwl.html). According to the docs this limit can't be raised, meaning you won't ever be able to make more than 10 Copilot environments in a region per account if each environment requires a LogResourcePolicy.
Proposal
I have no idea how or if this could be fixed because I honestly don't know what the LogResourcePolicy is for, I'm just flagging it as a potential issue or something to document maybe.