Introduction

When the Alexa Skills Kit trigger is missing from the Lambda console, the problem is usually not the function code. It is almost always a configuration issue around region support, the account flow you are using, or the fact that Alexa skills are usually connected from the Alexa developer side rather than from a generic Lambda trigger menu alone.

Understand How Alexa and Lambda Are Connected

An Alexa custom skill invokes a Lambda function only when the function is in an Alexa-supported AWS region and the skill configuration points to that function ARN. The Lambda function itself also needs permission to be invoked by Alexa.

A minimal Node.js handler looks like this:

1exports.handler = async function (event) {
2  const intent = event.request && event.request.type;
3
4  return {
5    version: "1.0",
6    response: {
7      outputSpeech: {
8        type: "PlainText",
9        text: `Received request type ${intent}`
10      },
11      shouldEndSession: true
12    }
13  };
14};

The code is rarely the reason the trigger option is absent. The missing trigger is a deployment and platform integration issue.

Check the Lambda Region First

Alexa does not work with every Lambda region. If your function was created in a region that the Alexa integration does not support, the console will not offer the Alexa Skills Kit trigger for that function.

The practical fix is:

1. create the function in an Alexa-supported region
2. copy or redeploy the code there
3. point the skill configuration at that function ARN

This is the most common root cause. Developers often create a Lambda function in the region they use for unrelated AWS work, then wonder why the Alexa option is missing.

Configure the Skill From the Alexa Side Too

Another source of confusion is assuming the integration must start inside the Lambda trigger dropdown. In practice, Alexa skills are normally configured from the Alexa developer console, where you choose Lambda as the endpoint type and paste the function ARN.

So even if you are thinking in terms of "add trigger in Lambda," the end-to-end setup usually looks like this:

• create the Lambda function in a supported region
• add the correct resource-based permission for Alexa invocation
• configure the skill endpoint in the Alexa developer console
• test the skill from the developer console or simulator

That means the missing dropdown is not the only place to focus.

Verify the Lambda Permission Policy

Alexa must be allowed to invoke the function. AWS can add this permission for you in some flows, but it is worth knowing what it looks like.

1aws lambda add-permission \
2  --function-name my-alexa-skill \
3  --statement-id alexa-skill-kit \
4  --action lambda:InvokeFunction \
5  --principal alexa-appkit.amazon.com

If the function is otherwise correct but the invocation policy is missing, the skill still will not work even after you wire up the endpoint.

You can inspect the policy with:

aws lambda get-policy --function-name my-alexa-skill

Keep the Skill Type and Endpoint Type Aligned

The Alexa Skills Kit trigger is relevant to custom skills using Lambda as an endpoint. If you are working on a different integration path, such as hosting logic elsewhere over HTTPS, the Lambda trigger flow is not the correct target at all.

That sounds obvious, but it catches people who copy setup instructions from a different Alexa skill type or older tutorial.

Troubleshoot With the Smallest Possible Setup

A good debugging sequence is:

1. create a new Lambda in an Alexa-supported region
2. use a tiny handler that always returns speech
3. confirm the function policy allows Alexa invocation
4. configure the skill endpoint with that exact function ARN
5. test from the Alexa simulator

This separates region and permission problems from application logic problems. If the simulator invokes the simple function successfully, you can move back to your real skill code.

Common Pitfalls

• Creating the Lambda function in a region that Alexa does not support is the most common reason the trigger option is missing.
• Treating the Lambda trigger dropdown as the only place to configure the integration causes confusion because the Alexa developer console also drives the endpoint setup.
• Forgetting the Lambda resource policy means the function may exist and the skill may point to it, but invocation still fails.
• Copying instructions for a different Alexa skill type can send you down the wrong configuration path.
• Debugging request handlers before verifying region, endpoint ARN, and invocation permissions wastes time because those platform settings fail earlier than your code does.

Summary

• A missing Alexa Skills Kit trigger usually points to region or integration configuration, not handler code.
• Put the Lambda function in an Alexa-supported region.
• Configure the skill endpoint from the Alexa developer console and make sure it uses the correct function ARN.
• Verify the Lambda resource policy allows Alexa invocation.
• Troubleshoot the platform wiring first, then the skill logic.