Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@aws-sdk/client-ssm-incidents

Package Overview
Dependencies
Maintainers
0
Versions
348
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@aws-sdk/client-ssm-incidents

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

  • 3.712.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
38K
increased by51.38%
Maintainers
0
Weekly downloads
 
Created
Source

@aws-sdk/client-ssm-incidents

Description

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

Systems Manager Incident Manager is an incident management console designed to help users mitigate and recover from incidents affecting their Amazon Web Services-hosted applications. An incident is any unplanned interruption or reduction in quality of services.

Incident Manager increases incident resolution by notifying responders of impact, highlighting relevant troubleshooting data, and providing collaboration tools to get services back up and running. To achieve the primary goal of reducing the time-to-resolution of critical incidents, Incident Manager automates response plans and enables responder team escalation.

Installing

To install this package, simply type add or install @aws-sdk/client-ssm-incidents using your favorite package manager:

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

Getting Started

Import

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

// ES5 example
const { SSMIncidentsClient, ListResponsePlansCommand } = require("@aws-sdk/client-ssm-incidents");
// ES6+ example
import { SSMIncidentsClient, ListResponsePlansCommand } from "@aws-sdk/client-ssm-incidents";

Usage

To send a request, you:

  • Initiate client with configuration (e.g. credentials, region).
  • Initiate command with input parameters.
  • Call send operation on client with command object as input.
  • If you are using a custom http handler, you may call destroy() to close open connections.
// a client can be shared by different commands.
const client = new SSMIncidentsClient({ region: "REGION" });

const params = {
  /** input parameters */
};
const command = new ListResponsePlansCommand(params);
Async/await

We recommend using 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.
}

Async-await is clean, concise, intuitive, easy to debug and has better error handling as compared to using Promise chains or callbacks.

Promises

You can also use Promise chaining to execute send operation.

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

Promises can also be called using .catch() and .finally() as follows:

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

We do not recommend using callbacks because of callback hell, but they are supported by the send operation.

// callbacks.
client.send(command, (err, data) => {
  // process err and data.
});
v2 compatible style

The client can also send requests using v2 compatible style. However, it results in a bigger bundle size and may be dropped in next major version. More details in the blog post on modular packages in AWS SDK for JavaScript

import * as AWS from "@aws-sdk/client-ssm-incidents";
const client = new AWS.SSMIncidents({ region: "REGION" });

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

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

// callbacks.
client.listResponsePlans(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;
   * }
   */
}

Getting Help

Please use these community resources for getting help. We use the 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-ssm-incidents 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)

BatchGetIncidentFindings

Command API Reference / Input / Output

CreateReplicationSet

Command API Reference / Input / Output

CreateResponsePlan

Command API Reference / Input / Output

CreateTimelineEvent

Command API Reference / Input / Output

DeleteIncidentRecord

Command API Reference / Input / Output

DeleteReplicationSet

Command API Reference / Input / Output

DeleteResourcePolicy

Command API Reference / Input / Output

DeleteResponsePlan

Command API Reference / Input / Output

DeleteTimelineEvent

Command API Reference / Input / Output

GetIncidentRecord

Command API Reference / Input / Output

GetReplicationSet

Command API Reference / Input / Output

GetResourcePolicies

Command API Reference / Input / Output

GetResponsePlan

Command API Reference / Input / Output

GetTimelineEvent

Command API Reference / Input / Output

ListIncidentFindings

Command API Reference / Input / Output

ListIncidentRecords

Command API Reference / Input / Output

ListRelatedItems

Command API Reference / Input / Output

ListReplicationSets

Command API Reference / Input / Output

ListResponsePlans

Command API Reference / Input / Output

ListTagsForResource

Command API Reference / Input / Output

ListTimelineEvents

Command API Reference / Input / Output

PutResourcePolicy

Command API Reference / Input / Output

StartIncident

Command API Reference / Input / Output

TagResource

Command API Reference / Input / Output

UntagResource

Command API Reference / Input / Output

UpdateDeletionProtection

Command API Reference / Input / Output

UpdateIncidentRecord

Command API Reference / Input / Output

UpdateRelatedItems

Command API Reference / Input / Output

UpdateReplicationSet

Command API Reference / Input / Output

UpdateResponsePlan

Command API Reference / Input / Output

UpdateTimelineEvent

Command API Reference / Input / Output

FAQs

Package last updated on 13 Dec 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc