Weird. Others are also reporting this. Just took a look and wasn’t able reproduce it Unsure what’s the missing factor Again, others are also reporting so it’s definitely happening. Going to cross link this https://github.com/tongueroo/jets/issues/445
Yes they’re might be correlated. I have restarted a fresh build (new api gateway, domain, etc) for a staging environment and I’m getting the same Authorization error on every warm up requests reported on the github issue ( Aws::CloudFormation::Errors::AccessDenied )
PS: Great work on this platform @tung, it’s very impressive
I’m getting this too - “Either StackName or PhysicalResourceId must be specified”.
We’ve had almost 7,000 errors in Sentry over the last 30 days. It would be great if we can get this sorted, otherwise we’ll have to look at moving away from Jets.