clients/client-pipes/README.md
AWS SDK for JavaScript Pipes Client for Node.js, Browser and React Native.
<p>Amazon EventBridge Pipes connects event sources to targets. Pipes reduces the need for specialized knowledge and integration code when developing event driven architectures. This helps ensures consistency across your company’s applications. With Pipes, the target can be any available EventBridge target. To set up a pipe, you select the event source, add optional event filtering, define optional enrichment, and select the target for the event data. </p>To install this package, use the CLI of your favorite package manager:
npm install @aws-sdk/client-pipesyarn add @aws-sdk/client-pipespnpm add @aws-sdk/client-pipesThe AWS SDK is modulized by clients and commands.
To send a request, you only need to import the PipesClient and
the commands you need, for example ListPipesCommand:
// ES5 example
const { PipesClient, ListPipesCommand } = require("@aws-sdk/client-pipes");
// ES6+ example
import { PipesClient, ListPipesCommand } from "@aws-sdk/client-pipes";
To send a request:
send operation on the client, providing the command object as input.const client = new PipesClient({ region: "REGION" });
const params = { /** input parameters */ };
const command = new ListPipesCommand(params);
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.
}
You can also use Promise chaining.
client
.send(command)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
})
.finally(() => {
// finally.
});
The aggregated client class is exported from the same package, but without the "Client" suffix.
Pipes extends PipesClient 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 (PipesClient).
More details are in the blog post on
modular packages in AWS SDK for JavaScript.
import { Pipes } from "@aws-sdk/client-pipes";
const client = new Pipes({ region: "REGION" });
// async/await.
try {
const data = await client.listPipes(params);
// process data.
} catch (error) {
// error handling.
}
// Promises.
client
.listPipes(params)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
});
// callbacks (not recommended).
client.listPipes(params, (err, data) => {
// process err and data.
});
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.
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.
aws-sdk-js
on AWS Developer Blog.aws-sdk-js.To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-pipes package is updated.
To contribute to client you can check our generate clients scripts.
This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.
Command API Reference / Input / Output
</details> <details> <summary> DeletePipe </summary>Command API Reference / Input / Output
</details> <details> <summary> DescribePipe </summary>Command API Reference / Input / Output
</details> <details> <summary> ListPipes </summary>Command API Reference / Input / Output
</details> <details> <summary> ListTagsForResource </summary>Command API Reference / Input / Output
</details> <details> <summary> StartPipe </summary>Command API Reference / Input / Output
</details> <details> <summary> StopPipe </summary>Command API Reference / Input / Output
</details> <details> <summary> TagResource </summary>Command API Reference / Input / Output
</details> <details> <summary> UntagResource </summary> </details> <details> <summary> UpdatePipe </summary> </details>