-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ElastiCache #1249
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello everyone!
I encountered an issue while trying to interact between a Lambda and Elasticache, which I see repeatedly commented on in some localstack issues that took me a while to resolve. I think it's a good idea to add a clarification within the Elasticache section or somewhere else to comment on the following:
aws/aws-sam-cli#318 (comment)
Even if you have configured a Lambda with the correct VPC, subnets, and security groups, it cannot internally communicate with this service (and perhaps more cases that I haven't tested yet). To resolve this, you need to assign the internal Docker host: host.docker.internal (in addition to the port explained 4510).
I don't see this in the documentation, and it would save a lot of time for anyone who wants to use a more complex network within localstack.
The text was updated successfully, but these errors were encountered: