Core

The core interface provides access to underlying invocation meta data on every request. This information can be used for debugging, correlating requests, etc.

Using the core interface #

The core interface can be imported from the @ampt/sdk and returns three getters:

• requestId: The AWS reqId that can be correlated with log entries.
• event: The raw AWS event object passed from the event source mapping.
• context: The AWS context object of the invocation.

The getter must be accessed from within a handler (e.g. task, events.on(), data.on()) or an HTTP framework's route/middleware.

Accessing core meta data
import { core, events } from "@ampt/sdk";

events.on("user.created", async (evt) => {
  console.log("Event Details:", evt);
  console.log({
    reqId: core.requestId,
    event: core.event,
    context: core.context,
  });
});

Setting Timeouts #

The context getter will return a setTimeout function that lets you dynamically override the current handler's timeout.

Ampt interfaces that define handlers like tasks, events, and storage, provide a context object as part of the handler signature (e.g. task("my-task", async (event, context) => { })). Other handlers, such as those defined by Fetch-based frameworks and Ampt Data listeners, don't provide a native way to adjust the timeout.

Instead, you can use core.context.setTimeout() (e.g. core.context.setTimeout(10000)) to dynamically set the timeout of any handler. Timeouts are in milliseconds and cannot exceed 5 minutes.