clients/client-s3files/README.md
AWS SDK for JavaScript S3Files Client for Node.js, Browser and React Native.
<p>S3 Files makes S3 buckets accessible as high-performance file systems powered by EFS. This service enables file system interface access to S3 data with sub-millisecond latencies through mount targets, supporting AI/ML workloads, media processing, and hybrid storage workflows that require both file system and object storage access to the same data.</p>To install this package, use the CLI of your favorite package manager:
npm install @aws-sdk/client-s3filesyarn add @aws-sdk/client-s3filespnpm add @aws-sdk/client-s3filesThe AWS SDK is modulized by clients and commands.
To send a request, you only need to import the S3FilesClient and
the commands you need, for example ListFileSystemsCommand:
// ES5 example
const { S3FilesClient, ListFileSystemsCommand } = require("@aws-sdk/client-s3files");
// ES6+ example
import { S3FilesClient, ListFileSystemsCommand } from "@aws-sdk/client-s3files";
To send a request:
send operation on the client, providing the command object as input.const client = new S3FilesClient({ region: "REGION" });
const params = { /** input parameters */ };
const command = new ListFileSystemsCommand(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.
S3Files extends S3FilesClient 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 (S3FilesClient).
More details are in the blog post on
modular packages in AWS SDK for JavaScript.
import { S3Files } from "@aws-sdk/client-s3files";
const client = new S3Files({ region: "REGION" });
// async/await.
try {
const data = await client.listFileSystems(params);
// process data.
} catch (error) {
// error handling.
}
// Promises.
client
.listFileSystems(params)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
});
// callbacks (not recommended).
client.listFileSystems(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-s3files 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> CreateFileSystem </summary>Command API Reference / Input / Output
</details> <details> <summary> CreateMountTarget </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteAccessPoint </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteFileSystem </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteFileSystemPolicy </summary>Command API Reference / Input / Output
</details> <details> <summary> DeleteMountTarget </summary>Command API Reference / Input / Output
</details> <details> <summary> GetAccessPoint </summary>Command API Reference / Input / Output
</details> <details> <summary> GetFileSystem </summary>Command API Reference / Input / Output
</details> <details> <summary> GetFileSystemPolicy </summary>Command API Reference / Input / Output
</details> <details> <summary> GetMountTarget </summary>Command API Reference / Input / Output
</details> <details> <summary> GetSynchronizationConfiguration </summary>Command API Reference / Input / Output
</details> <details> <summary> ListAccessPoints </summary>Command API Reference / Input / Output
</details> <details> <summary> ListFileSystems </summary>Command API Reference / Input / Output
</details> <details> <summary> ListMountTargets </summary>Command API Reference / Input / Output
</details> <details> <summary> ListTagsForResource </summary>Command API Reference / Input / Output
</details> <details> <summary> PutFileSystemPolicy </summary>Command API Reference / Input / Output
</details> <details> <summary> PutSynchronizationConfiguration </summary>Command API Reference / Input / Output
</details> <details> <summary> TagResource </summary>Command API Reference / Input / Output
</details> <details> <summary> UntagResource </summary> </details> <details> <summary> UpdateMountTarget </summary> </details>