@kensio/yulin 1.21.3 → 1.21.5

package/dist/service/s3/serve/api/sim-s3-api-object-output.js

@@ -1,4 +1,4 @@
-import { xmlDocument, xmlValue } from "../../../../util/xml/xml-writer.js";
+import { xmlDocument, xmlElement, xmlValue, } from "../../../../util/xml/xml-writer.js";
 import { simS3ObjectResponseHeaders } from "../../object/s3-object-response-headers.js";
 import { simS3SystemMetadataHeadersFrom } from "../../object/s3-system-metadata-read.js";
 /**
@@ -12,25 +12,44 @@ export function simS3CopyObjectXml(output) {
     return xmlDocument("CopyObjectResult", xmlValue("ETag", result.ETag) +
         xmlValue("LastModified", result.LastModified));
 }
+/**
+ * Write the tags on an Object as the document real S3 answers them with.
+ *
+ * An Object nobody has tagged answers with an empty `TagSet` element rather
+ * than none at all, which is what tells a client the Object exists and carries
+ * no tags.
+ */
+export function simS3ObjectTaggingXml(output) {
+    return xmlDocument("Tagging", xmlElement("TagSet", (output.TagSet ?? [])
+        .map((tag) => xmlElement("Tag", xmlValue("Key", tag.Key) + xmlValue("Value", tag.Value)))
+        .join("")));
+}
 /**
  * Answer a read with the Object itself, headers and all.
  *
+ * The headers the read named in its `response-` parameters are served in place
+ * of the Object's own, leaving what the Object was written with alone.
+ *
  * A read that asked for part of the Object is answered `206 Partial Content`
  * and says which part it carries, because a client reading a large Object in
  * pieces at once writes each response at the offset it asked for, and a `200`
  * carrying the whole Object would be written over its neighbours.
  */
-export async function simS3GetObjectResponse(output) {
+export async function simS3GetObjectResponse(output, overrides) {
     const body = await objectBodyBytes(output["Body"]);
     const contentRange = output["ContentRange"];
     return new Response(body, {
         status: contentRange === undefined ? 200 : 206,
         headers: simS3ObjectResponseHeaders({
             metadata: simS3SystemMetadataHeadersFrom(output),
+            userMetadata: output["Metadata"],
+            overrides,
             bodyLength: body.length,
             etag: output["ETag"],
             lastModified: output["LastModified"],
             contentRange,
+            storageClass: output["StorageClass"],
+            serverSideEncryption: output["ServerSideEncryption"],
         }),
     });
 }

package/dist/service/s3/serve/api/sim-s3-api-object-routes.js

@@ -1,4 +1,4 @@
-import { copyObjectInput, createMultipartUploadInput, getObjectInput, objectInput, putObjectInput, simS3CopySourceHeader, } from "./sim-s3-api-object-input.js";
+import { copyObjectInput, createMultipartUploadInput, getObjectInput, objectInput, putObjectInput, putObjectTaggingInput, simS3CopySourceHeader, versionedObjectInput, } from "./sim-s3-api-object-input.js";
 import { completeMultipartUploadInput, uploadInput, uploadPartInput, } from "./sim-s3-api-multipart-input.js";
 /**
  * The Object-level S3 operations this endpoint serves.
@@ -16,6 +16,13 @@ export const simS3ObjectApiRoutes = [
         commandName: "GetObjectCommand",
         input: getObjectInput,
     },
+    {
+        method: "GET",
+        target: "object",
+        subResource: "tagging",
+        commandName: "GetObjectTaggingCommand",
+        input: versionedObjectInput,
+    },
     {
         method: "GET",
         target: "object",
@@ -56,6 +63,13 @@ export const simS3ObjectApiRoutes = [
         commandName: "UploadPartCommand",
         input: uploadPartInput,
     },
+    {
+        method: "PUT",
+        target: "object",
+        subResource: "tagging",
+        commandName: "PutObjectTaggingCommand",
+        input: putObjectTaggingInput,
+    },
     {
         // A copy and an upload are both a `PUT` on an Object path, and the copy
         // names its source in a header. Matched first, so an upload carrying no
@@ -72,6 +86,13 @@ export const simS3ObjectApiRoutes = [
         commandName: "PutObjectCommand",
         input: putObjectInput,
     },
+    {
+        method: "DELETE",
+        target: "object",
+        subResource: "tagging",
+        commandName: "DeleteObjectTaggingCommand",
+        input: versionedObjectInput,
+    },
     {
         method: "DELETE",
         target: "object",

package/dist/service/s3/serve/api/sim-s3-api-output.d.ts

@@ -5,5 +5,9 @@
  * the operation rather than of its output: a listing answers in XML, a read
  * answers with the Object itself, and a write answers with a status and
  * headers alone.
+ *
+ * The request's query string is read alongside the output because a read can
+ * name the headers it wants served in place of the Object's own, and those are
+ * a property of the request rather than of what the operation answered.
  */
-export declare function simS3ApiResponse(commandName: string, output: unknown): Promise<Response>;
+export declare function simS3ApiResponse(commandName: string, output: unknown, query: URLSearchParams): Promise<Response>;

package/dist/service/s3/serve/api/sim-s3-api-output.js

@@ -1,8 +1,9 @@
-import { deleteResultXml, notificationConfigurationXml, publicAccessBlockXml, } from "./sim-s3-api-configuration-output.js";
+import { deleteResultXml, encryptionConfigurationXml, notificationConfigurationXml, publicAccessBlockXml, } from "./sim-s3-api-configuration-output.js";
 import { simS3HeadBucketResponse, simS3HeadObjectResponse, } from "./sim-s3-api-head-output.js";
 import { simS3ListBucketsXml, simS3ListObjectsXml, } from "./sim-s3-api-listing.js";
 import { simS3MultipartResponse } from "./sim-s3-api-multipart-output.js";
-import { simS3CopyObjectXml, simS3GetObjectResponse, } from "./sim-s3-api-object-output.js";
+import { simS3CopyObjectXml, simS3GetObjectResponse, simS3ObjectTaggingXml, } from "./sim-s3-api-object-output.js";
+import { simS3ResponseHeaderOverrides } from "../../object/s3-object-response-headers.js";
 const xmlContentType = { "content-type": "application/xml" };
 /**
  * Build the HTTP response an S3 operation's output is sent as.
@@ -11,8 +12,12 @@ const xmlContentType = { "content-type": "application/xml" };
  * the operation rather than of its output: a listing answers in XML, a read
  * answers with the Object itself, and a write answers with a status and
  * headers alone.
+ *
+ * The request's query string is read alongside the output because a read can
+ * name the headers it wants served in place of the Object's own, and those are
+ * a property of the request rather than of what the operation answered.
  */
-export async function simS3ApiResponse(commandName, output) {
+export async function simS3ApiResponse(commandName, output, query) {
     const value = output;
     switch (commandName) {
         case "ListBucketsCommand": {
@@ -25,7 +30,7 @@ export async function simS3ApiResponse(commandName, output) {
             return xml(simS3ListObjectsXml(value, 2));
         }
         case "GetObjectCommand": {
-            return await simS3GetObjectResponse(value);
+            return await simS3GetObjectResponse(value, simS3ResponseHeaderOverrides(query));
         }
         case "GetBucketPolicyCommand": {
             // A Bucket policy is a JSON document, and real S3 answers this one
@@ -39,14 +44,20 @@ export async function simS3ApiResponse(commandName, output) {
         case "GetPublicAccessBlockCommand": {
             return xml(publicAccessBlockXml(value));
         }
+        case "GetBucketEncryptionCommand": {
+            return xml(encryptionConfigurationXml(value));
+        }
         case "GetBucketNotificationConfigurationCommand": {
             return xml(notificationConfigurationXml(value));
         }
+        case "GetObjectTaggingCommand": {
+            return xml(simS3ObjectTaggingXml(value));
+        }
         case "DeleteObjectsCommand": {
             return xml(deleteResultXml(value));
         }
         case "HeadObjectCommand": {
-            return simS3HeadObjectResponse(value);
+            return simS3HeadObjectResponse(value, simS3ResponseHeaderOverrides(query));
         }
         case "HeadBucketCommand": {
             return simS3HeadBucketResponse(value);

package/dist/service/s3/serve/api/sim-s3-api-request.d.ts

@@ -17,12 +17,13 @@ export interface SimS3ApiRequest {
     readonly body: Uint8Array;
 }
 /**
- * Read a request that arrived at the served AWS API endpoint as an S3 request.
+ * Read a request addressed to the S3 REST API as an S3 request.
  *
- * Only path-style addressing is read here. A virtual-host request names its
- * Bucket in the hostname, and simulated Route 53 resolves that to the Bucket's
- * own endpoint before this endpoint is ever reached, so a request that gets
- * this far put its Bucket in the path.
+ * Both of the addressing styles real S3 offers are read, because both arrive
+ * here. A client given an endpoint URL sends path style, with the Bucket as
+ * the first path segment. An SDK resolving S3's own endpoint sends virtual
+ * host style, with the Bucket in the hostname, and function code bundling the
+ * SDK reaches this endpoint with exactly that.
  */
 export declare function readSimS3ApiRequest(request: Request, body: Uint8Array): SimS3ApiRequest;
 /**

package/dist/service/s3/serve/api/sim-s3-api-request.js

@@ -1,19 +1,19 @@
 /**
- * Read a request that arrived at the served AWS API endpoint as an S3 request.
+ * The hostname label S3's own REST endpoints carry.
+ */
+const s3EndpointLabel = "s3";
+/**
+ * Read a request addressed to the S3 REST API as an S3 request.
  *
- * Only path-style addressing is read here. A virtual-host request names its
- * Bucket in the hostname, and simulated Route 53 resolves that to the Bucket's
- * own endpoint before this endpoint is ever reached, so a request that gets
- * this far put its Bucket in the path.
+ * Both of the addressing styles real S3 offers are read, because both arrive
+ * here. A client given an endpoint URL sends path style, with the Bucket as
+ * the first path segment. An SDK resolving S3's own endpoint sends virtual
+ * host style, with the Bucket in the hostname, and function code bundling the
+ * SDK reaches this endpoint with exactly that.
  */
 export function readSimS3ApiRequest(request, body) {
     const url = new URL(request.url);
-    // The first segment is the Bucket and everything after it is the key, which
-    // can itself contain slashes.
-    const path = url.pathname.replace(/^\//, "");
-    const separator = path.indexOf("/");
-    const bucketName = separator === -1 ? path : path.slice(0, separator);
-    const objectKey = separator === -1 ? "" : path.slice(separator + 1);
+    const { bucketName, objectKey } = simS3ApiRequestTargetNames(url.hostname, url.pathname.replace(/^\//, ""));
     return {
         method: request.method,
         bucketName: decodeURIComponent(bucketName),
@@ -23,6 +23,50 @@ export function readSimS3ApiRequest(request, body) {
         body,
     };
 }
+/**
+ * Split what a request addressed into the Bucket it names and the Object key
+ * below it, still encoded as they were sent.
+ *
+ * A virtual host request names its Bucket in the hostname, which leaves its
+ * whole path as the key. A path style request names both in the path, where
+ * the first segment is the Bucket and everything after it is the key, which
+ * can itself contain slashes.
+ */
+function simS3ApiRequestTargetNames(hostname, path) {
+    const hostedBucketName = simS3VirtualHostBucketName(hostname);
+    if (hostedBucketName !== undefined) {
+        return { bucketName: hostedBucketName, objectKey: path };
+    }
+    const separator = path.indexOf("/");
+    if (separator === -1) {
+        return { bucketName: path, objectKey: "" };
+    }
+    return {
+        bucketName: path.slice(0, separator),
+        objectKey: path.slice(separator + 1),
+    };
+}
+/**
+ * The Bucket a virtual host style hostname names, or nothing for a hostname
+ * that names none.
+ *
+ * S3's own endpoint hostnames carry an `s3` label, and virtual host style puts
+ * the Bucket in front of it, as in `<bucket>.s3.<region>.amazonaws.com`. Path
+ * style is the same hostname with nothing in front. The labels before the
+ * first `s3` label are the Bucket, and an empty set of them is path style.
+ *
+ * A Bucket name can contain dots. One Bucket is then several hostname labels,
+ * joined back together here.
+ *
+ * A hostname carrying no `s3` label names no Bucket. That covers the local
+ * endpoint an `--endpoint-url` client sends, which addresses every service on
+ * one hostname and can only be path style.
+ */
+function simS3VirtualHostBucketName(hostname) {
+    const labels = hostname.split(".");
+    const endpoint = labels.indexOf(s3EndpointLabel);
+    return endpoint <= 0 ? undefined : labels.slice(0, endpoint).join(".");
+}
 /**
  * Decode an Object key from the path it was sent in.
  *

package/dist/service/s3/serve/api/sim-s3-api-routes.js

@@ -13,6 +13,8 @@ const servedSubResources = [
     "delete",
     "uploads",
     "uploadId",
+    "encryption",
+    "tagging",
 ];
 /**
  * Every sub-resource S3 defines, served here or not.
@@ -29,7 +31,6 @@ const knownSubResources = new Set([
     "acl",
     "analytics",
     "cors",
-    "encryption",
     "intelligent-tiering",
     "inventory",
     "legal-hold",
@@ -45,7 +46,6 @@ const knownSubResources = new Set([
     "restore",
     "retention",
     "select",
-    "tagging",
     "torrent",
     "versioning",
     "versions",

package/dist/service/s3/serve/api/sim-s3-api-tagging-read.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Read the tag set a PutObjectTagging body carries.
+ *
+ * This sits apart from the other request-body readers because it is the only
+ * one about an Object rather than about a Bucket's configuration. A tag naming
+ * no key comes through with none, so the tagging command refuses it rather than
+ * the reader silently dropping it.
+ */
+export declare function readSimS3Tagging(body: string): object;

package/dist/service/s3/serve/api/sim-s3-api-tagging-read.js

@@ -0,0 +1,14 @@
+import { parseXmlDocument, xmlChild, xmlChildren, xmlText, } from "../../../../util/xml/xml-document.js";
+/**
+ * Read the tag set a PutObjectTagging body carries.
+ *
+ * This sits apart from the other request-body readers because it is the only
+ * one about an Object rather than about a Bucket's configuration. A tag naming
+ * no key comes through with none, so the tagging command refuses it rather than
+ * the reader silently dropping it.
+ */
+export function readSimS3Tagging(body) {
+    return {
+        TagSet: xmlChildren(xmlChild(parseXmlDocument(body), "TagSet"), "Tag").map((tag) => ({ Key: xmlText(tag, "Key"), Value: xmlText(tag, "Value") })),
+    };
+}

package/dist/service/s3/serve/api/sim-s3-api.d.ts

@@ -22,7 +22,13 @@ export declare class SimS3ApiEndpoint {
      * The Region is the one the request was signed for, read from its credential
      * scope, so it arrives as whatever the client wrote rather than as a Region
      * the simulator has already recognised.
+     *
+     * A request nothing has authenticated arrives with no caller, and runs as
+     * the ambient caller of whatever sent it, in the same way an intercepted SDK
+     * client's Command does. A sim Lambda's outbound call relies on that. Its
+     * signature is over placeholder credentials, and the invocation is already
+     * running as the execution Role.
      */
-    handle(request: Request, body: Uint8Array, caller: SimAwsCaller, regionName: string): Promise<Response>;
+    handle(request: Request, body: Uint8Array, caller: SimAwsCaller | undefined, regionName: string): Promise<Response>;
 }
 export {};

package/dist/service/s3/serve/api/sim-s3-api.js

@@ -30,6 +30,12 @@ export class SimS3ApiEndpoint {
      * The Region is the one the request was signed for, read from its credential
      * scope, so it arrives as whatever the client wrote rather than as a Region
      * the simulator has already recognised.
+     *
+     * A request nothing has authenticated arrives with no caller, and runs as
+     * the ambient caller of whatever sent it, in the same way an intercepted SDK
+     * client's Command does. A sim Lambda's outbound call relies on that. Its
+     * signature is over placeholder credentials, and the invocation is already
+     * running as the execution Role.
      */
     async handle(request, body, caller, regionName) {
         const apiRequest = readSimS3ApiRequest(request, body);
@@ -47,7 +53,7 @@ export class SimS3ApiEndpoint {
         }
         try {
             const output = await this.dispatcher.dispatch(makeSimSdkWireCommand(route.commandName, route.input(apiRequest)), makeSimSdkWireClient(s3ServiceId, regionName), undefined, caller);
-            return await simS3ApiResponse(route.commandName, output);
+            return await simS3ApiResponse(route.commandName, output, apiRequest.query);
         }
         catch (error) {
             if (error instanceof SimSdkUnsupportedCommandError) {

package/dist/service/s3/serve/sim-s3-rest-controller.d.ts

@@ -30,11 +30,7 @@ export declare class SimS3RestController {
      */
     private deleteObject;
     /**
-     * Store an uploaded Object.
-     *
-     * The stated checksum is checked before anything is stored, as real S3 does,
-     * so an upload that would be refused there is refused here rather than
-     * quietly landing in the Bucket.
+     * Store an uploaded Object, as whatever the request said about it.
      */
     private putObject;
     private s3For;

package/dist/service/s3/serve/sim-s3-rest-controller.js

@@ -1,6 +1,6 @@
 import { SimS3RestErrorResponse } from "./sim-s3-rest-error-response.js";
 import { SimS3RestObjectReader } from "./sim-s3-rest-object-reader.js";
-import { SimS3UploadChecksum } from "./sim-s3-upload-checksum.js";
+import { simS3RestUploadInput } from "./sim-s3-rest-upload.js";
 /**
  * Serves Object requests that arrived at the simulated S3 REST endpoint.
  *
@@ -51,24 +51,10 @@ export class SimS3RestController {
         return new Response(undefined, { status: 204 });
     }
     /**
-     * Store an uploaded Object.
-     *
-     * The stated checksum is checked before anything is stored, as real S3 does,
-     * so an upload that would be refused there is refused here rather than
-     * quietly landing in the Bucket.
+     * Store an uploaded Object, as whatever the request said about it.
      */
     async putObject(route, serviceRequest) {
-        const { request, body } = serviceRequest;
-        SimS3UploadChecksum.stated(new URL(request.url), request.headers)?.check(body);
-        const contentType = request.headers.get("content-type") ?? undefined;
-        await this.s3For(route).putObject({
-            input: {
-                Bucket: route.bucket.bucketName,
-                Key: route.objectKey,
-                Body: body ?? new Uint8Array(),
-                ...(contentType !== undefined && { ContentType: contentType }),
-            },
-        }, { caller: serviceRequest.caller.toCaller() });
+        await this.s3For(route).putObject({ input: simS3RestUploadInput(route, serviceRequest) }, { caller: serviceRequest.caller.toCaller() });
         return new Response(undefined, { status: 200 });
     }
     s3For(route) {

package/dist/service/s3/serve/sim-s3-rest-object-reader.d.ts

@@ -8,6 +8,9 @@ import type { SimAwsServiceRequest } from "../../../serve/controller/sim-service
  * response real S3 stops short of sending, so they are read the same way here
  * and differ only in what comes back.
  *
+ * Either can name the headers it wants served in place of the Object's own,
+ * which is what a presigned URL handing a browser a download does.
+ *
  * A `GET` may ask for part of the Object, and is answered with that part and
  * `206 Partial Content`. A `HEAD` may not. Simulated S3 describes the whole
  * Object however it is asked about, and HeadObject does the same for an

package/dist/service/s3/serve/sim-s3-rest-object-reader.js

@@ -1,4 +1,4 @@
-import { simS3ObjectResponseHeaders } from "../object/s3-object-response-headers.js";
+import { simS3ObjectResponseHeaders, simS3ResponseHeaderOverrides, } from "../object/s3-object-response-headers.js";
 import { simS3SystemMetadataHeadersFrom } from "../object/s3-system-metadata-read.js";
 /**
  * Answers a `GET` or `HEAD` at the simulated S3 REST endpoint.
@@ -7,6 +7,9 @@ import { simS3SystemMetadataHeadersFrom } from "../object/s3-system-metadata-rea
  * response real S3 stops short of sending, so they are read the same way here
  * and differ only in what comes back.
  *
+ * Either can name the headers it wants served in place of the Object's own,
+ * which is what a presigned URL handing a browser a download does.
+ *
  * A `GET` may ask for part of the Object, and is answered with that part and
  * `206 Partial Content`. A `HEAD` may not. Simulated S3 describes the whole
  * Object however it is asked about, and HeadObject does the same for an
@@ -29,10 +32,14 @@ export class SimS3RestObjectReader {
         const body = await bodyBytes(output.Body);
         const headers = simS3ObjectResponseHeaders({
             metadata: simS3SystemMetadataHeadersFrom(output),
+            userMetadata: output.Metadata,
+            overrides: simS3ResponseHeaderOverrides(new URL(request.url).searchParams),
             bodyLength: body.length,
             etag: output.ETag,
             lastModified: output.LastModified,
             contentRange: output.ContentRange,
+            storageClass: output.StorageClass,
+            serverSideEncryption: output.ServerSideEncryption,
         });
         if (head) {
             return new Response(undefined, { status: 200, headers });

package/dist/service/s3/serve/sim-s3-rest-upload.d.ts

@@ -0,0 +1,20 @@
+import type { SimAwsServiceRequest } from "../../../serve/controller/sim-service-controller.js";
+import type { SimPutObjectCommandInput } from "../command/put-object/put-object.command.js";
+import type { SimS3RestObjectRoute } from "./sim-s3-route.js";
+/**
+ * The write an upload over the S3 REST endpoint asks for.
+ *
+ * A presigned `PUT` states everything about the Object in its headers, since
+ * that is the only place it has to put anything. The metadata headers are read
+ * by the same list a `PutObjectCommand` sets them with, so an upload here can
+ * describe an Object as fully as an in-process write can. A static site upload
+ * usually wants `cache-control` and `content-disposition`.
+ *
+ * The stated checksum is checked while the request is read, as real S3 checks
+ * it before storing anything, so an upload that would be refused there is
+ * refused here instead of quietly landing in the Bucket.
+ *
+ * `x-amz-tagging` is read alongside them, being the tags S3 holds against the
+ * Object rather than metadata it hands back on a read.
+ */
+export declare function simS3RestUploadInput(route: SimS3RestObjectRoute, serviceRequest: SimAwsServiceRequest): SimPutObjectCommandInput;

package/dist/service/s3/serve/sim-s3-rest-upload.js

@@ -0,0 +1,30 @@
+import { simS3WriteMetadataHeaders } from "../object/s3-write-metadata.js";
+import { SimS3UploadChecksum } from "./sim-s3-upload-checksum.js";
+/**
+ * The write an upload over the S3 REST endpoint asks for.
+ *
+ * A presigned `PUT` states everything about the Object in its headers, since
+ * that is the only place it has to put anything. The metadata headers are read
+ * by the same list a `PutObjectCommand` sets them with, so an upload here can
+ * describe an Object as fully as an in-process write can. A static site upload
+ * usually wants `cache-control` and `content-disposition`.
+ *
+ * The stated checksum is checked while the request is read, as real S3 checks
+ * it before storing anything, so an upload that would be refused there is
+ * refused here instead of quietly landing in the Bucket.
+ *
+ * `x-amz-tagging` is read alongside them, being the tags S3 holds against the
+ * Object rather than metadata it hands back on a read.
+ */
+export function simS3RestUploadInput(route, serviceRequest) {
+    const { request, body } = serviceRequest;
+    SimS3UploadChecksum.stated(new URL(request.url), request.headers)?.check(body);
+    const tagging = request.headers.get("x-amz-tagging");
+    return {
+        Bucket: route.bucket.bucketName,
+        Key: route.objectKey,
+        Body: body ?? new Uint8Array(),
+        ...simS3WriteMetadataHeaders(request.headers),
+        ...(tagging !== null && { Tagging: tagging }),
+    };
+}

package/dist/service/s3/serve/website/sim-s3-website-object-loader.js

@@ -46,6 +46,7 @@ export class SimS3WebsiteObjectLoader {
             return new SimS3WebsiteObject({
                 body: await simS3BodyToBuffer(output.Body),
                 metadata: simS3SystemMetadataHeadersFrom(output),
+                userMetadata: output.Metadata,
                 etag: output.ETag,
                 lastModified: output.LastModified,
             });

package/dist/service/s3/serve/website/sim-s3-website-object.d.ts

@@ -1,6 +1,7 @@
 interface SimS3WebsiteObjectProperties {
     readonly body: Buffer;
     readonly metadata?: Readonly<Record<string, string>> | undefined;
+    readonly userMetadata?: Readonly<Record<string, string>> | undefined;
     readonly etag?: string | undefined;
     readonly lastModified?: Date | undefined;
 }
@@ -14,6 +15,7 @@ interface SimS3WebsiteObjectProperties {
 export declare class SimS3WebsiteObject {
     readonly body: Buffer;
     private readonly metadata;
+    private readonly userMetadata;
     private readonly etag;
     private readonly lastModified;
     constructor(properties: SimS3WebsiteObjectProperties);

package/dist/service/s3/serve/website/sim-s3-website-object.js

@@ -9,11 +9,13 @@ import { simS3ObjectResponseHeaders } from "../../object/s3-object-response-head
 export class SimS3WebsiteObject {
     body;
     metadata;
+    userMetadata;
     etag;
     lastModified;
     constructor(properties) {
         this.body = properties.body;
         this.metadata = properties.metadata;
+        this.userMetadata = properties.userMetadata;
         this.etag = properties.etag;
         this.lastModified = properties.lastModified;
     }
@@ -23,6 +25,7 @@ export class SimS3WebsiteObject {
     headers() {
         return simS3ObjectResponseHeaders({
             metadata: this.metadata,
+            userMetadata: this.userMetadata,
             bodyLength: this.body.length,
             etag: this.etag,
             lastModified: this.lastModified,

package/dist/service/s3/sim-s3-commands.d.ts

@@ -4,11 +4,13 @@ import type { SimIamInterServiceAuthZ } from "../iam/authorize/sim-iam-inter-ser
 import type { SimS3Bucket, SimS3BucketName } from "./bucket/sim-s3-bucket.js";
 import { SimS3BucketCommands } from "./command/bucket/sim-s3-bucket-commands.js";
 import { SimS3BucketPolicyCommands } from "./command/bucket-policy/sim-s3-bucket-policy-commands.js";
+import { SimS3EncryptionCommands } from "./command/encryption/sim-s3-encryption-commands.js";
 import { SimS3LifecycleCommands } from "./command/lifecycle/sim-s3-lifecycle-commands.js";
 import { SimS3MultipartCommands } from "./command/multipart/sim-s3-multipart-commands.js";
 import { SimS3NotificationCommands } from "./command/notification/sim-s3-notification-commands.js";
 import { SimS3ObjectCommands } from "./command/object/sim-s3-object-commands.js";
 import { SimS3ObjectLockCommands } from "./command/object-lock/sim-s3-object-lock-commands.js";
+import { SimS3ObjectTaggingCommands } from "./command/tagging/sim-s3-object-tagging-commands.js";
 import { SimS3PublicAccessBlockCommands } from "./command/public-access-block/sim-s3-public-access-block-commands.js";
 import { SimS3VersioningCommands } from "./command/versioning/sim-s3-versioning-commands.js";
 import type { SimS3NotificationDestinations } from "./notification/destination/sim-s3-notification-destination.js";
@@ -55,10 +57,18 @@ export declare class SimS3Commands {
     readonly notifications: SimS3NotificationCommands;
     readonly lifecycles: SimS3LifecycleCommands;
     readonly versioning: SimS3VersioningCommands;
+    readonly encryption: SimS3EncryptionCommands;
     readonly objectLock: SimS3ObjectLockCommands;
     readonly objects: SimS3ObjectCommands;
+    readonly objectTagging: SimS3ObjectTaggingCommands;
     readonly multipartUploads: SimS3MultipartCommands;
     readonly objectNotifier: SimS3ObjectNotifier;
+    /**
+     * The scheduler and clock every command area here shares, which a
+     * simulator-only control on the service facade needs to hand a Bucket it
+     * makes outside the commands.
+     */
+    readonly background: BackgroundScheduler;
     constructor(properties: SimS3CommandsProperties);
 }
 export {};

package/dist/service/s3/sim-s3-commands.js

@@ -2,11 +2,13 @@ import { BackgroundTasks, } from "../../util/background/background.js";
 import { simIamInRegion } from "../iam/authorize/sim-iam-region-auth-z.js";
 import { SimS3BucketCommands } from "./command/bucket/sim-s3-bucket-commands.js";
 import { SimS3BucketPolicyCommands } from "./command/bucket-policy/sim-s3-bucket-policy-commands.js";
+import { SimS3EncryptionCommands } from "./command/encryption/sim-s3-encryption-commands.js";
 import { SimS3LifecycleCommands } from "./command/lifecycle/sim-s3-lifecycle-commands.js";
 import { SimS3MultipartCommands } from "./command/multipart/sim-s3-multipart-commands.js";
 import { SimS3NotificationCommands } from "./command/notification/sim-s3-notification-commands.js";
 import { SimS3ObjectCommands } from "./command/object/sim-s3-object-commands.js";
 import { SimS3ObjectLockCommands } from "./command/object-lock/sim-s3-object-lock-commands.js";
+import { SimS3ObjectTaggingCommands } from "./command/tagging/sim-s3-object-tagging-commands.js";
 import { SimS3PublicAccessBlockCommands } from "./command/public-access-block/sim-s3-public-access-block-commands.js";
 import { SimS3VersioningCommands } from "./command/versioning/sim-s3-versioning-commands.js";
 import { SimS3NoNotificationDestinations } from "./notification/destination/sim-s3-service-notification-destinations.js";
@@ -27,12 +29,21 @@ export class SimS3Commands {
     notifications;
     lifecycles;
     versioning;
+    encryption;
     objectLock;
     objects;
+    objectTagging;
     multipartUploads;
     objectNotifier;
+    /**
+     * The scheduler and clock every command area here shares, which a
+     * simulator-only control on the service facade needs to hand a Bucket it
+     * makes outside the commands.
+     */
+    background;
     constructor(properties) {
         const { background = new BackgroundTasks(), notificationDestinations = new SimS3NoNotificationDestinations(), } = properties;
+        this.background = background;
         const iam = simIamInRegion(properties.iam, properties.accountRegionScope.regionName);
         this.objectNotifier = new SimS3ObjectNotifier({
             destinations: notificationDestinations,
@@ -56,8 +67,10 @@ export class SimS3Commands {
         this.notifications = new SimS3NotificationCommands(state);
         this.lifecycles = new SimS3LifecycleCommands(state);
         this.versioning = new SimS3VersioningCommands(state);
+        this.encryption = new SimS3EncryptionCommands(state);
         this.objectLock = new SimS3ObjectLockCommands(state);
         this.objects = new SimS3ObjectCommands(state);
+        this.objectTagging = new SimS3ObjectTaggingCommands(state);
         this.multipartUploads = new SimS3MultipartCommands(state);
     }
 }