Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Recipe 5.9 Accessing VPN Resources with Lambda #1

Open
jtelleriar opened this issue Aug 2, 2022 · 0 comments
Open

Recipe 5.9 Accessing VPN Resources with Lambda #1

jtelleriar opened this issue Aug 2, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@jtelleriar
Copy link

jtelleriar commented Aug 2, 2022 •
edited
Loading

ISSUE
Lambda Function cannot access redis cluster endpoint, appears to be no reachable and lambda timeout is reached. Eg.:

aws lambda invoke \
    --cli-binary-format raw-in-base64-out \
    --function-name $LAMBDA_ARN \
    --payload '{ "hostname": "awscookbook509cachecluster.cw1vzu.0001.euw1.cache.amazonaws.com" }' \
    response.json && cat response.json

CONTEXT
Recipe Steps seems to be right for creating the aws elasticache cluster, but the cache security group created (CACHE_SECURITY_GROUP) in the CDK code appears unused.

aws elasticache create-cache-cluster \
    --cache-cluster-id "AWSCookbook509CacheCluster" \
    --cache-subnet-group-name AWSCookbook509CacheSG \
    --engine redis \
    --cache-node-type cache.t3.micro \
    --num-cache-nodes 1

REGION

eu-west-1

SOLUTION
Shall we associate a security group to the Elastic Cache Cluster (The one created in the CDK code), and configure an ingress rule for the Redis endpoint?

Thanks!
@jtelleriar jtelleriar added the bug Something isn't working label Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jtelleriar