opensite-ai/opensite-skills / aws-sdk-js-v3-usage
aws-sdk-js-v3-usage
UnverifiedAWS SDK for JavaScript v3 development patterns. Use when writing JavaScript or TypeScript code that uses AWS services via @aws-sdk/* packages (aws-sdk-js-v3), or when asked about schemas, runtime validation, serialization, or code generation in the context of the JS/TS AWS SDK.
| File | Kind | Size |
|---|---|---|
| .aws-skill-metadata | other | 18 B |
| SKILL.md | skill md | 8.5 KB |
| references/clients.md | markdown | 3.6 KB |
| references/credentials.md | markdown | 3.4 KB |
| references/dynamodb.md | markdown | 2.8 KB |
| references/effective-practices.md | markdown | 2.3 KB |
| references/error-handling.md | markdown | 1.6 KB |
| references/lambda.md | markdown | 1.7 KB |
| references/performance.md | markdown | 1.9 KB |
| references/s3.md | markdown | 2.7 KB |
| references/schemas.md | markdown | 1.7 KB |
| references/sigv4a.md | markdown | 1.5 KB |
| references/typescript.md | markdown | 1.1 KB |
references/lambda.md
View on GitHub# Lambda Reference
## SDK Version in Lambda Runtimes
Lambda bundles a specific SDK version — not the latest. To control the version, bundle the SDK with your function or use a Lambda layer.
Check the installed version:
```js
const pkg = require("@aws-sdk/client-s3/package.json");
exports.handler = () => JSON.stringify(pkg);
```
## Creating a Lambda Layer
```json
// package.json for layer content
{
"dependencies": {
"@aws-sdk/client-s3": "<=3.750.0",
"@aws-sdk/client-dynamodb": "<=3.750.0"
}
}
```
Run `npm install`, then zip as:
```text
layer_content.zip
└ nodejs/node_modules/@aws-sdk/...
```
Deploy:
```js
import { Lambda } from "@aws-sdk/client-lambda";
import fs from "node:fs";
const lambda = new Lambda();
await lambda.publishLayerVersion({
LayerName: "my-sdk-layer",
Content: { ZipFile: fs.readFileSync("./layer_content.zip") },
CompatibleRuntimes: ["nodejs20.x", "nodejs22.x"],
CompatibleArchitectures: ["x86_64", "arm64"],
});
```
## One-Time Async Initialization
Don't call async setup outside the handler — signed requests may expire during provisioned concurrency pre-warming. Use a lazy flag inside the handler instead:
```js
// WRONG: risky — network requests may be frozen pre-flight
const ready = prepare();
export const handler = async (event) => { await ready; ... };
// OK: lazy init inside handler
let client = null;
export const handler = async (event) => {
if (!client) client = await prepare();
return client.getItem({ ... });
};
```
SDK clients themselves (no async setup) are safe to initialize outside the handler:
```js
const s3 = new S3Client({}); // OK: outside handler — reused across invocations
export const handler = async (event) => {
return s3.send(new GetObjectCommand({ ... }));
};
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |