@aws-sdk/client-mediaconnect

中文文档
3.1164.0发布于 2026/11/07Apache-2.0TypeScriptESM + CJS近 30 天下载 13.3万

AWS SDK for JavaScript Mediaconnect Client for Node.js, Browser and React Native

原始使用文档
文档目录10 节
  1. Description
  2. Installing
  3. Getting Started
  4. Import
  5. Usage
  6. Troubleshooting
  7. Getting Help
  8. Contributing
  9. License
  10. Client Commands (Operations List)

@aws-sdk/client-mediaconnect

Description

AWS SDK for JavaScript MediaConnect Client for Node.js, Browser and React Native.

Welcome to the Elemental MediaConnect API reference.

MediaConnect is a service that lets you ingest live video content into the cloud and distribute it to destinations all over the world, both inside and outside the Amazon Web Services cloud. This API reference provides descriptions, syntax, and usage examples for each of the actions and data types that are supported by MediaConnect.

Use the following links to get started with the MediaConnect API:

  • Actions: An alphabetical list of all MediaConnect API operations.

  • Data types: An alphabetical list of all MediaConnect data types.

  • Common parameters: Parameters that all operations can use.

  • Common errors: Client and server errors that all operations can return.

Installing

To install this package, use the CLI of your favorite package manager:

  • npm install @aws-sdk/client-mediaconnect
  • yarn add @aws-sdk/client-mediaconnect
  • pnpm add @aws-sdk/client-mediaconnect

Getting Started

Import

The AWS SDK is modulized by clients and commands. To send a request, you only need to import the MediaConnectClient and the commands you need, for example ListBridgesCommand:

// ES5 example
const { MediaConnectClient, ListBridgesCommand } = require("@aws-sdk/client-mediaconnect");
// ES6+ example
import { MediaConnectClient, ListBridgesCommand } from "@aws-sdk/client-mediaconnect";

Usage

To send a request:

  • Instantiate a client with configuration (e.g. credentials, region).
  • Instantiate a command with input parameters.
  • Call the send operation on the client, providing the command object as input.
const client = new MediaConnectClient({ region: "REGION" });

const params = { /** input parameters */ };
const command = new ListBridgesCommand(params);

Async/await

We recommend using the await operator to wait for the promise returned by send operation as follows:

// async/await.
try {
  const data = await client.send(command);
  // process data.
} catch (error) {
  // error handling.
} finally {
  // finally.
}

Promises

You can also use Promise chaining.

client
  .send(command)
  .then((data) => {
    // process data.
  })
  .catch((error) => {
    // error handling.
  })
  .finally(() => {
    // finally.
  });

Aggregated client

The aggregated client class is exported from the same package, but without the "Client" suffix.

MediaConnect extends MediaConnectClient and additionally supports all operations, waiters, and paginators as methods. This style may be familiar to you from the AWS SDK for JavaScript v2.

If you are bundling the AWS SDK, we recommend using only the bare-bones client (MediaConnectClient). More details are in the blog post on modular packages in AWS SDK for JavaScript.

import { MediaConnect } from "@aws-sdk/client-mediaconnect";

const client = new MediaConnect({ region: "REGION" });

// async/await.
try {
  const data = await client.listBridges(params);
  // process data.
} catch (error) {
  // error handling.
}

// Promises.
client
  .listBridges(params)
  .then((data) => {
    // process data.
  })
  .catch((error) => {
    // error handling.
  });

// callbacks (not recommended).
client.listBridges(params, (err, data) => {
  // process err and data.
});

Troubleshooting

When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).

try {
  const data = await client.send(command);
  // process data.
} catch (error) {
  const { requestId, cfId, extendedRequestId } = error.$metadata;
  console.log({ requestId, cfId, extendedRequestId });
  /**
   * The keys within exceptions are also parsed.
   * You can access them by specifying exception names:
   * if (error.name === 'SomeServiceException') {
   *     const value = error.specialKeyInException;
   * }
   */
}

See also docs/ERROR_HANDLING.

Getting Help

Please use these community resources for getting help. We use GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.

To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.

Contributing

This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-mediaconnect package is updated. To contribute to client you can check our generate clients scripts.

License

This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.

Client Commands (Operations List)

AddBridgeOutputs

Command API Reference / Input / Output

AddBridgeSources

Command API Reference / Input / Output

AddFlowMediaStreams

Command API Reference / Input / Output

AddFlowOutputs

Command API Reference / Input / Output

AddFlowSources

Command API Reference / Input / Output

AddFlowVpcInterfaces

Command API Reference / Input / Output

BatchGetDestinationEndpoint

Command API Reference / Input / Output

BatchGetRouterInput

Command API Reference / Input / Output

BatchGetRouterNetworkInterface

Command API Reference / Input / Output

BatchGetRouterOutput

Command API Reference / Input / Output

BatchGetSourceEndpoint

Command API Reference / Input / Output

ConnectEndpoints

Command API Reference / Input / Output

CreateBridge

Command API Reference / Input / Output

CreateFlow

Command API Reference / Input / Output

CreateGateway

Command API Reference / Input / Output

CreateRouterInput

Command API Reference / Input / Output

CreateRouterNetworkInterface

Command API Reference / Input / Output

CreateRouterOutput

Command API Reference / Input / Output

DeleteBridge

Command API Reference / Input / Output

DeleteFlow

Command API Reference / Input / Output

DeleteGateway

Command API Reference / Input / Output

DeleteRouterInput

Command API Reference / Input / Output

DeleteRouterNetworkInterface

Command API Reference / Input / Output

DeleteRouterOutput

Command API Reference / Input / Output

DeregisterDestinationEndpoint

Command API Reference / Input / Output

DeregisterGatewayInstance

Command API Reference / Input / Output

DeregisterSourceEndpoint

Command API Reference / Input / Output

DescribeBridge

Command API Reference / Input / Output

DescribeFlow

Command API Reference / Input / Output

DescribeFlowSourceMetadata

Command API Reference / Input / Output

DescribeFlowSourceThumbnail

Command API Reference / Input / Output

DescribeGateway

Command API Reference / Input / Output

DescribeGatewayInstance

Command API Reference / Input / Output

DescribeOffering

Command API Reference / Input / Output

DescribeReservation

Command API Reference / Input / Output

DisconnectEndpoints

Command API Reference / Input / Output

GetDestinationEndpoint

Command API Reference / Input / Output

GetRouterInput

Command API Reference / Input / Output

GetRouterInputSourceMetadata

Command API Reference / Input / Output

GetRouterInputThumbnail

Command API Reference / Input / Output

GetRouterNetworkInterface

Command API Reference / Input / Output

GetRouterOutput

Command API Reference / Input / Output

GetSourceEndpoint

Command API Reference / Input / Output

GrantFlowEntitlements

Command API Reference / Input / Output

ListBridges

Command API Reference / Input / Output

ListDestinationEndpoints

Command API Reference / Input / Output

ListEntitlements

Command API Reference / Input / Output

ListFlows

Command API Reference / Input / Output

ListGatewayInstances

Command API Reference / Input / Output

ListGateways

Command API Reference / Input / Output

ListOfferings

Command API Reference / Input / Output

ListReservations

Command API Reference / Input / Output

ListRouterInputs

Command API Reference / Input / Output

ListRouterNetworkInterfaces

Command API Reference / Input / Output

ListRouterOutputs

Command API Reference / Input / Output

ListSourceEndpoints

Command API Reference / Input / Output

ListTagsForGlobalResource

Command API Reference / Input / Output

ListTagsForResource

Command API Reference / Input / Output

PurchaseOffering

Command API Reference / Input / Output

RegisterDestinationEndpoint

Command API Reference / Input / Output

RegisterSourceEndpoint

Command API Reference / Input / Output

RemoveBridgeOutput

Command API Reference / Input / Output

RemoveBridgeSource

Command API Reference / Input / Output

RemoveFlowMediaStream

Command API Reference / Input / Output

RemoveFlowOutput

Command API Reference / Input / Output

RemoveFlowSource

Command API Reference / Input / Output

RemoveFlowVpcInterface

Command API Reference / Input / Output

RestartRouterInput

Command API Reference / Input / Output

RestartRouterOutput

Command API Reference / Input / Output

RevokeFlowEntitlement

Command API Reference / Input / Output

StartFlow

Command API Reference / Input / Output

StartRouterInput

Command API Reference / Input / Output

StartRouterOutput

Command API Reference / Input / Output

StopFlow

Command API Reference / Input / Output

StopRouterInput

Command API Reference / Input / Output

StopRouterOutput

Command API Reference / Input / Output

TagGlobalResource

Command API Reference / Input / Output

TagResource

Command API Reference / Input / Output

TakeRouterInput

Command API Reference / Input / Output

UntagGlobalResource

Command API Reference / Input / Output

UntagResource

Command API Reference / Input / Output

UpdateBridge

Command API Reference / Input / Output

UpdateBridgeOutput

Command API Reference / Input / Output

UpdateBridgeSource

Command API Reference / Input / Output

UpdateBridgeState

Command API Reference / Input / Output

UpdateDestinationEndpoint

Command API Reference / Input / Output

UpdateFlow

Command API Reference / Input / Output

UpdateFlowEntitlement

Command API Reference / Input / Output

UpdateFlowMediaStream

Command API Reference / Input / Output

UpdateFlowOutput

Command API Reference / Input / Output

UpdateFlowSource

Command API Reference / Input / Output

UpdateGatewayInstance

Command API Reference / Input / Output

UpdateRouterInput

Command API Reference / Input / Output

UpdateRouterNetworkInterface

Command API Reference / Input / Output

UpdateRouterOutput

Command API Reference / Input / Output

UpdateSourceEndpoint

Command API Reference / Input / Output

版本与发布记录

@aws-sdk/client-mediaconnect 共发布 732 个版本,首次发布于 2020/01/10;过去 12 个月发布了 220 个版本。

版本发布日期距今
3.1164.0latest2026/11/071 天前
3.1163.02026/11/062 天前
3.1162.02026/11/052 天前
3.1161.02026/10/318 天前
3.1160.02026/10/309 天前
3.1159.02026/10/2910 天前

其他发布通道:alpha → 1.0.0-alpha.22,beta → 1.0.0-beta.5,gamma → 1.0.0-gamma.11,rc → 3.5.1-rc.0。

关于 @aws-sdk/client-mediaconnect 的常见问题

@aws-sdk/client-mediaconnect 是什么?

AWS SDK for JavaScript Mediaconnect Client for Node.js, Browser and React Native

如何安装 @aws-sdk/client-mediaconnect?

在项目目录运行 npm install @aws-sdk/client-mediaconnect,或使用 pnpm add / yarn add / bun add。

@aws-sdk/client-mediaconnect 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@aws-sdk/client-mediaconnect 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@aws-sdk/client-mediaconnect 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=20.0.0。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@aws-sdk/client-mediaconnect 可以商用吗?

@aws-sdk/client-mediaconnect 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@aws-sdk/client-mediaconnect 的下载量有多少?

根据 npm 官方下载统计,@aws-sdk/client-mediaconnect 在 2026/10/08 – 2026/11/06 这 30 天内被下载 132,992 次,日均约 4,433 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@aws-sdk/client-mediaconnect 还在维护吗?

最新版本 3.1164.0 发布于 2026/11/07(1 天前);至今共发布 732 个版本,其中过去 12 个月发布了 220 个;首次发布于 2020/01/10。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。