Pablo Colazurdo

Setting KeepAlive to -1 didn't make any difference. Adding some pprof information: mem.prof -raw ``` PeriodType: space bytes Period: 524288 Time: 2022-04-14 15:33:00.631651 +0100 IST Samples: alloc_objects/count alloc_space/bytes[dflt] inuse_objects/count inuse_space/bytes...

I've done a few additional tests with some interesting results: * Running this against a local dynamodb doesn't panic at all. Goroutines are kept under 200 and it always finishes...

Ok, additional tests show that forcing the SDK client to use the HTTP endpoint avoids the crashes I kept seeing. This allows me to enable KeepAlives again and regain performance,...

I've just ran into this problem. I have two front ends on the same environment and they both need to respond on the root (/) path so the only way...

Thanks for the feedback. I thought about those workarounds but in my case the backend application needs a different security group attached to it

In my case, a second LB will be the preferred option. As one of the targets is a management app, I'd like to be able to have separate logs, waf...

I need to think about that. They share common resources (database, sqs, sns) and lifecycle and have the same operation model, so I thought this would make sense to have...

Reviewing the documentation, it makes sense to have both pieces of the application in the same Copilot Application and Environment. They are two microservices endpoints of the same core application,...

Updated to match latest commit on main. Some comments: * go.mod and go.sum are different because I had to include ```awsprometheuswriter```. This is because the current collector doesn't seem to...

@erichsueh3 I've tried initialising the extension and I just get an extension crash on Lambda. As soon as I add: ```yaml extensions: sigv4auth: region: "us-west-2" ... service: extensions: [sigv4auth] ```...