Cloud formation expects it to exists, so maybe not so much sst but I was able to deploy by setting

accessLog

to false. I might have missed something, but accessLogs were not being created by default before. This is an easy work around because I was already managing the access log for the Api outside of the SST's construct.

What version did you have before?

Frank helped me get around this. We had to create the missing log group, redeployed with accessLog: false. I then got an error about the log existing. I manually deleted the log group and redeployed and it was fine from that point onwards

I was on 0.53.0

Hey @Mike McCall, I was digging into this issue a bit more

I was already managing the access log for the Api outside of the SST’s construct

A few questions: • Is this the

Api

or

ApiGatewayV1Api

construct? • Did you remove the log group created by the

Api

construct and created ur own? • Was there any any request made to the api prior to the update? (in the other word, was the log group be empty)