@aws-sdk/core

@aws-sdk/core

This package provides common or core functionality to the AWS SDK for JavaScript (v3).

You do not need to explicitly install this package, since it will be transitively installed by AWS SDK clients.

@aws-sdk/core submodules

Core submodules are organized for distribution via the package.json exports field.

exports is supported by default by the latest Node.js, webpack, and esbuild. For react-native, it can be enabled via instructions found at reactnative.dev/blog.

Think of @aws-sdk/core as a mono-package within the monorepo. It preserves the benefits of modularization, for example to optimize Node.js initialization speed, while making it easier to have a consistent version of core dependencies, reducing package sprawl when installing an SDK client.

Guide for submodules

• Each index.ts file corresponding to the pattern ./src/submodules/<MODULE_NAME>/index.ts will be published as a separate dist-cjs bundled submodule index using the Inliner.js build script.
• create a folder as ./src/submodules/<SUBMODULE> including an index.ts file and a README.md file.
  • The linter will throw an error on missing submodule metadata in package.json and the various tsconfig.json files, but it will automatically fix them if possible.
• a submodule is equivalent to a standalone @aws-sdk/<pkg> package in that importing it in Node.js will resolve a separate bundle.
• submodules may not relatively import files from other submodules. Instead, directly use the @scope/pkg/submodule name as the import.
  • The linter will check for this and throw an error.
• To the extent possible, correctly declaring submodule metadata is validated by the linter in @aws-sdk/core. The linter runs during yarn build and also as yarn lint.

When should I create an @aws-sdk/core/submodule vs. @aws-sdk/new-package?

Keep in mind that the core package is installed by all AWS SDK clients.

If the component functionality is upstream of multiple clients, it is a good candidate for a core submodule. For example, XML serialization.

If the component's functionality is downstream of a client, for example S3 pre-signing, it should be a standalone package with potentially a peer or runtime dependency on an AWS SDK client.

Changelog

3.587.0 (2024-05-30)

Bug Fixes

• credentials-provider-ini: include general http provider when sourcing EcsContainer credentials (#6132) (8cdaf0a)

Features

• client-acm: add v2 smoke tests and smithy smokeTests trait for SDK testing. (c87de6a)
• client-bedrock-agent: With this release, Knowledge bases for Bedrock adds support for Titan Text Embedding v2. (c2f93e1)
• client-bedrock-runtime: This release adds Converse and ConverseStream APIs to Bedrock Runtime (512d901)
• client-cloudtrail: CloudTrail Lake returns PartitionKeys in the GetEventDataStore API response. Events are grouped into partitions based on these keys for better query performance. For example, the calendarday key groups events by day, while combining the calendarday key with the hour key groups them by day and hour. (88273ba)
• client-connect: Adding associatedQueueIds as a SearchCriteria and response field to the SearchRoutingProfiles API (b46048a)
• client-emr-serverless: The release adds support for spark structured streaming. (572bc93)
• client-sagemaker: Adds Model Card information as a new component to Model Package. Autopilot launches algorithm selection for TimeSeries modality to generate AutoML candidates per algorithm. (393afc7)
• clients: update client endpoints as of 2024-05-30 (d131ac0)