Joel Scheuner

Hi @slee106, I can share good New Year news: ## Lambda permissions Lambda permissions were updated last week (PR #7336) and are available in our new Lambda provider through a...

Both issues should be fixed now. @slee106 Can you pull the latest Docker image and try again? To start the latest version of [LocalStack with Docker-Compose](https://docs.localstack.cloud/getting-started/installation/#starting-localstack-with-docker-compose), you can use the...

@HarshCasper It would be good to fix the 404s related to the LocalStack CLI soon 🙏 : 📆 IMHO, having at least some advertising page for the LocalStack CLI up...

Hi @joshbalfour We strive for high [parity with AWS](https://web.archive.org/web/20240210010958/https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html) and therefore restrain from unnecessarily modifying the [official Lambda runtime images](https://github.com/aws/aws-lambda-base-images) from AWS, including the specific SDK version used for a...

Thank you for raising this clear feature request @davecardwell 👍 Let's hope the issue in the upstream AWS RIE repository gets resolved quickly ⬆️ : https://github.com/aws/aws-lambda-runtime-interface-emulator/issues/94 Otherwise, we would need...

Marking this feature request as accepted such that it does not get closed by the stale bot anymore. It's a reasonable feature request for the reasons discussed in this [Discuss...

Hi @akefirad and @joshorr 👋 An alternative solution for forwarding certain requests to real AWS is our [LocalStack Extension](https://docs.localstack.cloud/user-guide/extensions/) called [AWS replicator](https://pypi.org/project/localstack-extension-aws-replicator/). You can check out a demo of the...

Thank you for the quick and helpful response @akefirad 🙏 1. I agree that the AWS Replicator Extension does not solve your WireMock forwarding scenario because the proxy mechanism has...

@whummer the problem still requires workarounds for newer Nodejs versions because v17 changed a default behavior such that IPv6 is favored over IPv4. This breaks the defaults for LocalStack running...

@whummer yes, I fixed the Javascript bug in [getConnectHostname](https://github.com/localstack/serverless-localstack/commit/f03272c7f18b3302fb962dd1cf41a6a2d6b8e675#diff-bfe9874d239014961b1ae4e89875a6155667db834a410aaaa2ebe3cf89820556R657) and created PRs for: * serverless-localstack: https://github.com/localstack/serverless-localstack/pull/210 * cdklocal: https://github.com/localstack/aws-cdk-local/pull/80