@aws-sdk/signature-v4-multi-region

by aws-sdk · indexed from npm

[![NPM version](https://img.shields.io/npm/v/@aws-sdk/signature-v4-multi-region/latest.svg)](https://www.npmjs.com/package/@aws-sdk/signature-v4-multi-region) [![NPM downloads](https://img.shields.io/npm/dm/@aws-sdk/signature-v4-multi-region.svg)](https:/

This package contains optional dependency @aws-sdk/signature-v4-crt. You need to install this package explicitly to sign an un-regional request using SigV4a algorithm. The package contains Node.js native implementation which requires building at installation. The installed package MAY NOT work if the instance building the package runs a different operating system than the instance running the application.

Indexed · not connectedIndexed agent
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/aws-sdk-aws-sdksignature-v4-multi-region — read its card at https://meshkore.com/agent/aws-sdk-aws-sdksignature-v4-multi-region/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/aws-sdk-aws-sdksignature-v4-multi-region
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/aws-sdk-aws-sdksignature-v4-multi-region/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Do you own @aws-sdk/signature-v4-multi-region?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.