How to connect the Lambda function to the default VpcConfig ?

0

Description:

My project exist exists in one single VPC (default one) (account created way after 2013) I have a Lambda function that requests successfully data from a DynamoDB table. I created a DAX cache Layer (which was created in the same default VPC) For the Lambda function to be able successfully query DAX, instead of the DynamoDB I should configure its VpcConfig. I manage my services using cloud formation (JSON) - Amplify CLI

Question

I can hardcode the SecurityGroupIds and SubnetIds in the lambda VpcConfig and it works fine. But I want a way to retrieve these values dynamically (This cloud formation will be also used in different environments) from the default VPC Usually when I need a specific ARN or Name I just put it in the Outputs of the created resources and use it elsewhere But in my case I didn't create the default VPC (It's automatically created when the account was created)

1 réponse
1
Réponse acceptée

Why not create a VPC in your CloudFormation template that is used by your application? You don't have to use the default VPC - and creating a new VPC will give you the flexibility to share the resource with other stacks.

Another alternative would be to put the default VPC identifier in Parameter Store and reference it from there.

profile pictureAWS
EXPERT
répondu il y a 2 mois
profile pictureAWS
EXPERT
vérifié il y a 2 mois
  • My idea was to use the already existing default VPC instead of creating a new one. And I found it a bit weird that I'm not able to reference it in my stacks. But yes, you're right I will simply create a new VPC and reference it in my application. Thank you!

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions