Sync Data Between Stacks Using Contentstack Webhooks and AWS Lambda

AWS Lambda is a cloud computing platform, which is serverless, offered as part of Amazon Web Services. It is event-driven which means that it runs your code in response to events.

Its flexibility allows you to integrate AWS Lambda with other services to automate certain tasks. We will use AWS Lambda with Contentstack Webhooks to create an automated system that will help us to keep our stacks in sync.

This means if we have multiple stacks and when we make changes in one of the stacks, the other stacks get updated automatically through a lambda function. And In this guide, we will discuss the steps that will help us achieve that.

Process Overview: For this exercise, we will create three separate stacks. One will be a parent or a global stack. Whereas, the other two will be child/sub stacks A and B. We will then create a webhook in our global stack to trigger an event for the lambda function. This lambda function will update the child stacks with the content from the global stack.


Steps for Execution

  1. Download the Sample App Code
  2. Import Entries and Assets in Stacks
  3. Create an AWS Lambda function
  4. Create a trigger in Lambda
  5. Setup a webhook in the Parent Stack
  6. Run the sample app
  1. Download the Sample App Code

    Download the sample app code that we have built for this exercise from our GitHub repository. In the code bundle, you’ll find several folders and should resemble somewhere close to the following image:


    Replicate the code into two more copies and name them something like “Global Stack,” “Stack A,” and “Stack B.” Here, the Global stack will be the parent Stack whereas Stack A and Stack B will be child stacks. Once done, install the dependencies in all three folders using the command npm install.

  2. Import Entries and Assets in Stacks

    The next step is to create the stacks and import entries and assets from the downloaded code bundle. For this exercise we need three stacks, a Global Stack and two child stacks Stack A and Stack B. Log in to your Contentstack account and follow the steps mentioned in the create a stack guide.

    After you create the stacks, use the Contentstack CLI to import entries and assets to the Global Stack as well as to the child stacks, Stack A and Stack B. Perform the following steps in order to do this:

    1. Navigate to the downloaded folder and access the folder named “stack-data.”
    2. Note: Before importing the data, make sure that you are authenticated and have added the stack management tokens for the parent Stack and the Child stacks A and B in CLI session.

    3. Fire up the command prompt and run the following command and hit enter.
    4. csdx cm:import -a <management_token_alias>
      Mention the token name in <management_token_alias>
    5. Enter the master locale and provide the complete path to the stored content as displayed in the image below:Cli_image.png

    Repeat the above steps again to import content types, Entries, and Assets in the Child stacks - Stack A, and Stack B.

    We have created the following content types for this exercise:

    • Header
    • Home
    • Footer
    • Privacy Policy

    After importing the content types and its subsequent entries and assets, to all the three stacks, your finished stacks should look something like what is displayed in the animation below:

  3. Create an AWS Lambda Function

    We will now create a lambda function that will execute our code and keep our stacks in sync. To do this, log in to your AWS account and perform the following steps:

    1. Log in to your AWS Management Console and select Lambda from the Service list.
    2. Click on the Create Function button and then the Author from Scratch option.
    3. Configure the lambda based on your requirements. Choose Node.js 16.x as your run-time language and click on the Create function button.
    4. AWS Lambda offers an inline code editor. You can write your lambda code here or alternatively upload the code.
    5. Once you get the code, upload the zip file of the “index” folder within the “lambda-function” folder on Lambda by selecting the Upload a .zip file option from the Actions drop-down. Keep Handler as index/index.handler and click on Save.
    6. Note: Make sure that you only upload the “” file included in the “lambda-function” folder. Do not zip the entire source code folder.

      This is how it will look when you upload the code in the editor:


    7. Once we have uploaded the code in the editor, let's now set up the Environment variables by adding the values to the keys as follows:
      • apiKeyStackA: API key of the stack A
      • apiKeyStackB: API key of the stack B
      • globalStackManagementToken: Management token of the Global Stack
      • regionUrl: the URL that you want to use
      • stackAManagementToken: Management token of stack A
      • stackAPublishEnv: Publishing Environment for Stack A
      • stackBManagementToken: Management token of stack B
      • stackBPublishEnv: Publishing Environment for Stack B
    8. This is depicted in the screenshot below:environment_variables.png
    9. Once you add the environment variables, click on Save.
  4. Create a Trigger in Lambda

    Let’s proceed to create a trigger in our Lambda function by performing the following steps:

    1. Click on the + Add Trigger buttonadd_trigger.png
    2. Select API Gateway from the Trigger Configuration drop-down menu.
    3. In the API sub-section, select the Create an API option from the dropdown, and set the options as shown in the image below:
      • API Type - Rest API
      • Security - Open
    4. Click on the Add button.
    5. Within the API Gateway section, expand the Details menu. Next, note down the API endpoint URL as we will need it to configure the webhook in Contentstack. 

    With this, we’ve completed the lambda setup.

  5. Set up a Webhook in the Parent Stack

    Now that you’re done with creating the stacks and importing its entries, let’s create a webhook in the Global stack which will sync the Header, Footer, and the Privacy page of the child stacks.

    To do this, in your Contentstack account, go to your Global stack and perform the following steps:

    1. Click on the “settings” icon on the left panel and click on Webhooks.
    2. Click on + New Webhook and enter the details in the name field.
    3. Create custom headers as shown below:Sync_Data_Between_Stacks_Using_Contentstack_Webhooks_and_AWS_Lambda_2_no_highlight.png
    4. Paste the API endpoint URL in the URL to notify field.Sync_Data_Between_Stacks_Using_Contentstack_Webhooks_and_AWS_Lambda_3_highlighted.png
    5. Next, add the conditions for triggering the webhook as shown below in the Conditional View section:Sync_Data_Between_Stacks_Using_Contentstack_Webhooks_and_AWS_Lambda_4_no_highlight.png Note that we’ve added four conditions. This is because we have four content types, we want both the child stacks to be updated whenever any or all of the entries within these content types are changed.
    6. Finally, click the Enable Webhook checkbox option and, Save the webhook.
  6. Run the Sample App

    Now, let us configure the Global Stack sample app by performing the following steps:

    1. In the root folder of the Global Stack sample app, open the config.js file with any code editor utility.
    2. Enter the values for port, apiKey, accessToken, and Environment as shown below: 
      Next, enter the details for the content type UIDs as shown in the previous image. Repeat this for the config.js files of Stack A and Stack B by using the port numbers 4000, and 5000 for Stack A and Stack B respectively.
    3. Run the sample app by entering the command npm start in the command prompt.

    You can try updating and publishing the header, footer, and the Privacy policy entries in the Global Stack. When you refresh Stack A and Stack B, the changes you’ve made in the Global stack will also reflect in Stacks A and B.

Was this article helpful?