steffyP

Hi @gdsgj! The `latest` image of localstack now includes SQS metrics. Please run `docker pull localstack/localstack:latest`. I tested your sample with this version, and the CloudWatch Alarm will change to...

Hi @bamajap, can you please confirm you are using the latest `samlocal`? `$ pip list | grep aws-sam-cli-local`

Hi @comppaz, thanks for reporting! The issue should be fixed in the `latest` version. Please run `docker pull localstack/localstack:latest` and let us know if your use case is working now!

Hi @nmofonseca, we would really appreciate if you could provide the terraform-file that is creating that issue. I tried to run this with a simple configuration and using `tflocal`. However,...

Hi @nmofonseca, this is another friendly reminder that we are still waiting for a terraform example/configuration that will help us to reproduce your issue. Unfortunately you did not provide any...

closing the ticket because we have been waiting for a response for over a month, and were not able to reproduce the issue with the information provided.

Hi @nmofonseca, I'm sorry but we will have to close this issue as it doesn't seem to be related to LocalStack, but to a missing configuration setting in terragrunt.

Hi @leszko, we have recently added a [new and improved provider for S3](https://discuss.localstack.cloud/t/localstack-release-v1-3-0/170#migration-of-s3-and-lambda-to-asf-provider-4), that should fix your reported issue. Could you please use either image version `1.3.0` or `latest` and...

Hi @leszko, great to hear that it works now! > Just wonder, why isn't it enabled by default, but one has to specify PROVIDER_OVERRIDE_S3=asf As stated in our [release notes](https://discuss.localstack.cloud/t/localstack-release-v1-3-0/170#migration-of-s3-and-lambda-to-asf-provider-4),...

Hi @philipholtseeland, the issue should be resolved now, a fix is available in the `latest` image for pro. The database instance is now using the information provided by the cluster...