Resolving TypeError: Expected parameter accessToken in Next.js with AWS Amplify and Contentful

---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

The Problem: Why Is This Happening?

You're likely using a code snippet similar to the following in your getStaticProps:

[[See Video to Reveal this Text or Code Snippet]]

Despite configuring your environment variables (CONTENTFUL_SPACE and CONTENTFUL_API_KEY) correctly in the AWS Amplify dashboard, the error still persists when running your application. You might be puzzled, especially since no issues arise when using other hosting solutions like Vercel.

The root of the problem is that, on AWS Amplify, environment variables are not directly accessible within Lambda functions, where the getStaticProps function executes. This results in the API keys not being available, ultimately leading to the error.

The Solution: Making Environment Variables Accessible

To resolve this issue, you need to ensure that your environment variables are correctly passed to the Lambda function during its runtime. Here’s how to do that:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Deploy Changes

After making these changes, you will need to redeploy your application on AWS Amplify. This ensures that the updated configuration is used during the building and deployment phases.

Step 3: Verify Configuration

Make sure to check the following:

The environment variables are set correctly in the AWS Amplify dashboard.

Wrapping Up