Is it possible to use API Destination as Target in EventBridge Scheduler?

[angelhodar]

Hey! I am just testing if its possible to use a destination API as target for the EventBridge Scheduler, which would be amazing as it simplifies a lot the needed infra for one time tasks to be executed in custom backend. I have just created a destination api and connection configured to call my backend in an api endpoint with a POST request. Then I copied the arn of the destination api that AWS shows in the dashboard.

import {
  CreateScheduleCommand,
  FlexibleTimeWindowMode,
  GetScheduleCommand,
  SchedulerClient,
  ScheduleState,
  UpdateScheduleCommand,
} from "@aws-sdk/client-scheduler";

const client = new SchedulerClient({ region: "eu-west-3" });

const defaultArn =
  "arn:aws:events:eu-west-3:123456789:api-destination/backend-api/c0255f5b-7968-418d-a04d-e3d7a271db42"; // Data is anonymized
const roleArn = "arn:aws:iam::123456789:role/Amazon_EventBridge_Scheduler";

export interface ScheduleInfo<T> {
  name: string;
  scheduleExpression: string;
  handler: (params?: T) => Promise<void>;
  params?: T;
}

export const createSchedule = async <T>(scheduleInfo: ScheduleInfo<T>) => {
  const input = { jobName: scheduleInfo.handler.name, ...scheduleInfo.params };

  const scheduleParams = {
    Name: scheduleInfo.name,
    ScheduleExpression: scheduleInfo.scheduleExpression,
    State: ScheduleState.ENABLED,
    FlexibleTimeWindow: { Mode: FlexibleTimeWindowMode.OFF },
    Target: {
      Arn: defaultArn,
      RoleArn: roleArn,
      Input: JSON.stringify(input),
    },
  };

  try {
    const createCommand = new CreateScheduleCommand(scheduleParams);
    await client.send(createCommand);
    console.log(`Schedule created: ${scheduleInfo.name}`);
  } catch (error) {
    console.error(`Failed to create schedule: ${scheduleInfo.name}`, error);
  }
};

but when I try to execute it then it fails saying the ARN is not in the correct format:

Failed to create schedule: NetworksConnectionReminder ValidationException: Parameter arn:aws:events:eu-west-3:12345678:api-destination/fuel-backend/c0255f5b-7968-418d-a04d-e3d7a271db42 is not valid. Reason: Provided Arn is not in correct format.
    at de_ValidationExceptionRes (C:\Users\angel\Desktop\Proyectos\scheduler-demo\node_modules\@aws-sdk\client-scheduler\dist-cjs\index.js:843:21)
    at de_CommandError (C:\Users\angel\Desktop\Proyectos\scheduler-demo\node_modules\@aws-sdk\client-scheduler\dist-cjs\index.js:760:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async C:\Users\angel\Desktop\Proyectos\scheduler-demo\node_modules\@smithy\middleware-serde\dist-cjs\index.js:35:20
    at async C:\Users\angel\Desktop\Proyectos\scheduler-demo\node_modules\@smithy\core\dist-cjs\index.js:165:18
    at async C:\Users\angel\Desktop\Proyectos\scheduler-demo\node_modules\@smithy\middleware-retry\dist-cjs\index.js:320:38
    at async C:\Users\angel\Desktop\Proyectos\scheduler-demo\node_modules\@aws-sdk\middleware-logger\dist-cjs\index.js:34:22
    at createSchedule (c:\Users\angel\Desktop\Proyectos\scheduler-demo\scheduler.ts:51:5)
    at scheduleJobs (c:\Users\angel\Desktop\Proyectos\scheduler-demo\index.ts:36:7) {
  '$fault': 'client',
  '$metadata': {
    httpStatusCode: 400,
    requestId: 'e23d5818-7c92-4373-a202-acee7cedbf76',
    extendedRequestId: undefined,
    cfId: undefined,
    attempts: 1,
    totalRetryDelay: 0
  }
}

I have only found this as related, but it feels that solution is not correct because it would recreate a destination api for each call