Was this helpful?

0 out of 0 people found this review to be helpful

@jamesrweaver @awscloud We ended up creating a new environment with a different AMI, and that environment doesn't get the error.