Created log groups need a default policy.

[avirtual]

The created log groups do not have a default policy and that causes AWS to add more content to the regional resource policy, eventually reaching the limit of 5120 bytes.

10:40:31 AM | CREATE_FAILED        | AWS::ApiGatewayV2::Stage                        | apiApiDefaultStageA626ED4D
Cannot enable logging. Policy document length breaking Cloudwatch Logs Constraints, either < 1 or > 5120 (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: f34c406a-e69a-48de-b1a8-a68acd9cc0
70; Proxy: null)

In apibuilder.ts

const accessLogs = new logs.LogGroup(scope, "VAMS-API-AccessLogs");

In order to prevent that from happening (when deploying multiple stacks on the same region) something like this needs to be added

    const policyStatement = new iam.PolicyStatement({
        sid: "AWSLogDeliveryWrite20150319",
        effect: iam.Effect.ALLOW,
        principals: [new iam.ServicePrincipal("delivery.logs.amazonaws.com")],
        actions: ["logs:CreateLogStream", "logs:PutLogEvents"],
        resources: [`${accessLogs.logGroupArn}:log-stream:*`],
        conditions: {
            StringEquals: {
                "aws:SourceAccount": cdk.Stack.of(scope).account
            },
            ArnLike: {
                "aws:SourceArn": `arn:aws:logs:${cdk.Stack.of(scope).region}:${cdk.Stack.of(scope).account}:*`
            }
        }
    });

    accessLogs.addToResourcePolicy(policyStatement);

Same story in uploadAssetWorkflowBuilder.ts and potentially elsewhere.

[avirtual]

https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html