Leia Renée

This helped me https://github.com/marketplace/actions/pull-request-comment-branch

**Modified from examples/complete removing all external modules and keeping 1 inline managed node group only.** nodegroup configuration ```terraform module "eks" { source = "terraform-aws-modules/eks/aws" version = "~> 18.20.5" . ....

This workaround solved it for me. (https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1810) (Repeating for brevity) Module 'eks' ```terraform node_security_group_tags = { "kubernetes.io/cluster/${local.name}" = null } ```

Same here. 😠 What a shame to aws cli, not giving appropriate error message, or not describing it in help to put `file://` as a prefix or just for requiring...

We are having the same issue. Suspense does not work with amplify under nextjs

> This is related to streaming which works with Suspense. When app deployed on Amplify, streaming does not work. It might buffered the request somewhere and then after that passes...

@costleya Amplify supports connection to lambda. Might there be a way for proxying partially to evaluate server-side part?

Infinitely waiting aws-nuke version 2.22.1 ```shell eu-west-1 - CloudWatchEventsRule - Rule: AutoScalingManagedRule - failed eu-west-1 - CloudWatchLogsLogGroup - /aws/eks/otomi/cluster - [CreatedTime: "168334--183", LastEvent: "2023-05-06T06:20:34+02:00", logGroupName: "/aws/eks/otomi/cluster", tag:created_by: "terragrunt", tag:k8s: "custom",...

> Hi @leiarenee , which helm chart are you using to deploy this operator ? Can you please provide more steps and information ? To me, it looks like an...