proof-nicholas

I was able to workaround this by adding an override to each environment to remove the `LogResourcePolicy` resource: ``` - op: remove path: /Resources/LogResourcePolicy ``` Then use the following AWS...

> @proof-nicholas how do you specify the manually created resource-policy in copilot? For us, we only have one application but with multiple environments because we use it to deploy preview...

I am encountering the same issue. Building the ent package takes 8GB+ memory and one minute to build which ends up locking up developer machines. There is a collective shudder...

Can the maintainers please comment? Even if it is something that is not going to be fixed, please let us know so we can explore other options. This issue is...

I tried 1.23.0 and it did not have a noticeable impact.

Please let me know if there's additional data I can collect or anything I can provide to help diagnose root cause. This has become a priority issue for my team....

Our build system isn't limiting the memory allocated to the compile process. We are building on EC2 instances without swap space configured that have 32 GB memory. What is happening...

Any ETA on this?

Yes, I used the [override](https://aws.github.io/copilot-cli/docs/developing/overrides/yamlpatch/) capability (`cfn.patches.yml`) for my service to set it to 0 as in the following: ``` - op: add path: /Resources/TargetGroup/Properties/Matcher value: GrpcCode: 0 ```

Agreed, I don't see any reason why the default policy should be 1.0. We got dinged in a security scan because I assumed the tool would configure reasonable security defaults.