@kensio/yulin 1.8.0 → 1.10.0

package/dist/service/s3/notification/destination/sim-s3-notification-destination.d.ts

@@ -53,7 +53,7 @@ export interface SimS3NotificationDestination {
  * under `LambdaFunctionConfigurations` is refused for not being a function
  * rather than quietly delivered to as a queue.
  */
-export type SimS3NotificationDestinationService = "lambda" | "sqs";
+export type SimS3NotificationDestinationService = "lambda" | "sns" | "sqs";
 /**
  * The destinations one simulated S3 scope can reach.
  */

package/dist/service/s3/notification/destination/sim-s3-notification-destination.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sim-s3-notification-destination.d.ts","sourceRoot":"","sources":["../../../../../src/service/s3/notification/destination/sim-s3-notification-destination.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,iCAAiC,CAAC;AAExE;;;;;;GAMG;AACH,MAAM,WAAW,mCAAmC;IAClD,QAAQ,CAAC,cAAc,EAAE,MAAM,CAAC;IAChC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,oBAAoB,EAAE,MAAM,CAAC;IAEtC;;;;;OAKG;IACH,QAAQ,CAAC,gBAAgB,EAAE,MAAM,CAAC;CACnC;AAED;;GAEG;AACH,MAAM,WAAW,gCAAiC,SAAQ,mCAAmC;IAC3F,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,KAAK,EAAE,gBAAgB,CAAC;CAClC;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,4BAA4B;IAC3C;;;OAGG;IACH,QAAQ,CAAC,OAAO,EAAE,mCAAmC,GAAG,IAAI,CAAC;IAE7D;;OAEG;IACH,OAAO,CAAC,OAAO,EAAE,gCAAgC,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;CACnE;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,mCAAmC,GAAG,QAAQ,GAAG,KAAK,CAAC;AAEnE;;GAEG;AACH,MAAM,WAAW,6BAA6B;IAC5C;;;;OAIG;IACH,OAAO,CACL,OAAO,EAAE,mCAAmC,EAC5C,cAAc,EAAE,MAAM,GACrB,4BAA4B,CAAC;CACjC"}
+{"version":3,"file":"sim-s3-notification-destination.d.ts","sourceRoot":"","sources":["../../../../../src/service/s3/notification/destination/sim-s3-notification-destination.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,iCAAiC,CAAC;AAExE;;;;;;GAMG;AACH,MAAM,WAAW,mCAAmC;IAClD,QAAQ,CAAC,cAAc,EAAE,MAAM,CAAC;IAChC,QAAQ,CAAC,SAAS,EAAE,MAAM,CAAC;IAC3B,QAAQ,CAAC,oBAAoB,EAAE,MAAM,CAAC;IAEtC;;;;;OAKG;IACH,QAAQ,CAAC,gBAAgB,EAAE,MAAM,CAAC;CACnC;AAED;;GAEG;AACH,MAAM,WAAW,gCAAiC,SAAQ,mCAAmC;IAC3F,QAAQ,CAAC,eAAe,EAAE,MAAM,CAAC;IACjC,QAAQ,CAAC,KAAK,EAAE,gBAAgB,CAAC;CAClC;AAED;;;;;;;;GAQG;AACH,MAAM,WAAW,4BAA4B;IAC3C;;;OAGG;IACH,QAAQ,CAAC,OAAO,EAAE,mCAAmC,GAAG,IAAI,CAAC;IAE7D;;OAEG;IACH,OAAO,CAAC,OAAO,EAAE,gCAAgC,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC;CACnE;AAED;;;;;;;GAOG;AACH,MAAM,MAAM,mCAAmC,GAAG,QAAQ,GAAG,KAAK,GAAG,KAAK,CAAC;AAE3E;;GAEG;AACH,MAAM,WAAW,6BAA6B;IAC5C;;;;OAIG;IACH,OAAO,CACL,OAAO,EAAE,mCAAmC,EAC5C,cAAc,EAAE,MAAM,GACrB,4BAA4B,CAAC;CACjC"}

package/dist/service/s3/notification/destination/sim-s3-service-notification-destinations.d.ts

@@ -1,6 +1,7 @@
 import type { SimS3NotificationDestination, SimS3NotificationDestinations, SimS3NotificationDestinationService } from "./sim-s3-notification-destination.js";
 interface SimS3ServiceNotificationDestinationsProperties {
     readonly lambda: SimS3NotificationDestination;
+    readonly sns: SimS3NotificationDestination;
     readonly sqs: SimS3NotificationDestination;
 }
 /**
@@ -13,6 +14,7 @@ interface SimS3ServiceNotificationDestinationsProperties {
  */
 export declare class SimS3ServiceNotificationDestinations implements SimS3NotificationDestinations {
     private readonly lambda;
+    private readonly sns;
     private readonly sqs;
     constructor(properties: SimS3ServiceNotificationDestinationsProperties);
     /**

package/dist/service/s3/notification/destination/sim-s3-service-notification-destinations.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"sim-s3-service-notification-destinations.d.ts","sourceRoot":"","sources":["../../../../../src/service/s3/notification/destination/sim-s3-service-notification-destinations.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EACV,4BAA4B,EAC5B,6BAA6B,EAC7B,mCAAmC,EACpC,MAAM,sCAAsC,CAAC;AAE9C,UAAU,8CAA8C;IACtD,QAAQ,CAAC,MAAM,EAAE,4BAA4B,CAAC;IAC9C,QAAQ,CAAC,GAAG,EAAE,4BAA4B,CAAC;CAC5C;AAED;;;;;;;GAOG;AACH,qBAAa,oCAAqC,YAAW,6BAA6B;IACxF,OAAO,CAAC,QAAQ,CAAC,MAAM,CAA+B;IACtD,OAAO,CAAC,QAAQ,CAAC,GAAG,CAA+B;IAEnD,YAAY,UAAU,EAAE,8CAA8C,EAGrE;IAED;;OAEG;IACH,OAAO,CACL,OAAO,EAAE,mCAAmC,GAC3C,4BAA4B,CAS9B;CACF;AAED;;;;;;;GAOG;AACH,qBAAa,+BAAgC,YAAW,6BAA6B;IACnF;;OAEG;IACH,OAAO,CACL,QAAQ,EAAE,mCAAmC,EAC7C,cAAc,EAAE,MAAM,GACrB,KAAK,CAOP;CACF"}
+{"version":3,"file":"sim-s3-service-notification-destinations.d.ts","sourceRoot":"","sources":["../../../../../src/service/s3/notification/destination/sim-s3-service-notification-destinations.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EACV,4BAA4B,EAC5B,6BAA6B,EAC7B,mCAAmC,EACpC,MAAM,sCAAsC,CAAC;AAE9C,UAAU,8CAA8C;IACtD,QAAQ,CAAC,MAAM,EAAE,4BAA4B,CAAC;IAC9C,QAAQ,CAAC,GAAG,EAAE,4BAA4B,CAAC;IAC3C,QAAQ,CAAC,GAAG,EAAE,4BAA4B,CAAC;CAC5C;AAED;;;;;;;GAOG;AACH,qBAAa,oCAAqC,YAAW,6BAA6B;IACxF,OAAO,CAAC,QAAQ,CAAC,MAAM,CAA+B;IACtD,OAAO,CAAC,QAAQ,CAAC,GAAG,CAA+B;IACnD,OAAO,CAAC,QAAQ,CAAC,GAAG,CAA+B;IAEnD,YAAY,UAAU,EAAE,8CAA8C,EAIrE;IAED;;OAEG;IACH,OAAO,CACL,OAAO,EAAE,mCAAmC,GAC3C,4BAA4B,CAY9B;CACF;AAED;;;;;;;GAOG;AACH,qBAAa,+BAAgC,YAAW,6BAA6B;IACnF;;OAEG;IACH,OAAO,CACL,QAAQ,EAAE,mCAAmC,EAC7C,cAAc,EAAE,MAAM,GACrB,KAAK,CAOP;CACF"}

package/dist/service/s3/notification/destination/sim-s3-service-notification-destinations.js

@@ -9,9 +9,11 @@ import { SimS3NotImplemented } from "../../error/sim-s3.error.js";
  */
 export class SimS3ServiceNotificationDestinations {
     lambda;
+    sns;
     sqs;
     constructor(properties) {
         this.lambda = properties.lambda;
+        this.sns = properties.sns;
         this.sqs = properties.sqs;
     }
     /**
@@ -22,6 +24,9 @@ export class SimS3ServiceNotificationDestinations {
             case "lambda": {
                 return this.lambda;
             }
+            case "sns": {
+                return this.sns;
+            }
             case "sqs": {
                 return this.sqs;
             }

package/dist/service/s3/notification/destination/sim-s3-service-notification-destinations.js.map

@@ -1 +1 @@
-{"version":3,"file":"sim-s3-service-notification-destinations.js","sourceRoot":"","sources":["../../../../../src/service/s3/notification/destination/sim-s3-service-notification-destinations.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,6BAA6B,CAAC;AAYlE;;;;;;;GAOG;AACH,MAAM,OAAO,oCAAoC;IAC9B,MAAM,CAA+B;IACrC,GAAG,CAA+B;IAEnD,YAAY,UAA0D;QACpE,IAAI,CAAC,MAAM,GAAG,UAAU,CAAC,MAAM,CAAC;QAChC,IAAI,CAAC,GAAG,GAAG,UAAU,CAAC,GAAG,CAAC;IAC5B,CAAC;IAED;;OAEG;IACH,OAAO,CACL,OAA4C;QAE5C,QAAQ,OAAO,EAAE,CAAC;YAChB,KAAK,QAAQ,EAAE,CAAC;gBACd,OAAO,IAAI,CAAC,MAAM,CAAC;YACrB,CAAC;YACD,KAAK,KAAK,EAAE,CAAC;gBACX,OAAO,IAAI,CAAC,GAAG,CAAC;YAClB,CAAC;QACH,CAAC;IACH,CAAC;CACF;AAED;;;;;;;GAOG;AACH,MAAM,OAAO,+BAA+B;IAC1C;;OAEG;IACH,OAAO,CACL,QAA6C,EAC7C,cAAsB;QAEtB,MAAM,IAAI,mBAAmB,CAC3B,iBAAiB,cAAc,sCAAsC;YACnE,qEAAqE;YACrE,iEAAiE;YACjE,iDAAiD,CACpD,CAAC;IACJ,CAAC;CACF"}
+{"version":3,"file":"sim-s3-service-notification-destinations.js","sourceRoot":"","sources":["../../../../../src/service/s3/notification/destination/sim-s3-service-notification-destinations.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,mBAAmB,EAAE,MAAM,6BAA6B,CAAC;AAalE;;;;;;;GAOG;AACH,MAAM,OAAO,oCAAoC;IAC9B,MAAM,CAA+B;IACrC,GAAG,CAA+B;IAClC,GAAG,CAA+B;IAEnD,YAAY,UAA0D;QACpE,IAAI,CAAC,MAAM,GAAG,UAAU,CAAC,MAAM,CAAC;QAChC,IAAI,CAAC,GAAG,GAAG,UAAU,CAAC,GAAG,CAAC;QAC1B,IAAI,CAAC,GAAG,GAAG,UAAU,CAAC,GAAG,CAAC;IAC5B,CAAC;IAED;;OAEG;IACH,OAAO,CACL,OAA4C;QAE5C,QAAQ,OAAO,EAAE,CAAC;YAChB,KAAK,QAAQ,EAAE,CAAC;gBACd,OAAO,IAAI,CAAC,MAAM,CAAC;YACrB,CAAC;YACD,KAAK,KAAK,EAAE,CAAC;gBACX,OAAO,IAAI,CAAC,GAAG,CAAC;YAClB,CAAC;YACD,KAAK,KAAK,EAAE,CAAC;gBACX,OAAO,IAAI,CAAC,GAAG,CAAC;YAClB,CAAC;QACH,CAAC;IACH,CAAC;CACF;AAED;;;;;;;GAOG;AACH,MAAM,OAAO,+BAA+B;IAC1C;;OAEG;IACH,OAAO,CACL,QAA6C,EAC7C,cAAsB;QAEtB,MAAM,IAAI,mBAAmB,CAC3B,iBAAiB,cAAc,sCAAsC;YACnE,qEAAqE;YACrE,iEAAiE;YACjE,iDAAiD,CACpD,CAAC;IACJ,CAAC;CACF"}

package/dist/service/s3/notification/destination/sns/sim-aws-s3-notification-topics.d.ts

@@ -0,0 +1,38 @@
+import type { SimAws } from "../../../../aws/sim-aws.js";
+import type { SimS3NotificationDestinationRequest } from "../sim-s3-notification-destination.js";
+import type { SimS3NotificationTopics } from "./sim-s3-notification-topics.js";
+interface SimAwsS3NotificationTopicsProperties {
+    readonly simAws: SimAws;
+}
+/**
+ * The simulated SNS topics of one simulated AWS instance, as S3 notification
+ * destinations.
+ *
+ * Topics are looked up when a configuration is applied or an event is
+ * delivered, never when this is built, for the same reason the other
+ * destinations do it that way: reaching another service while this one is being
+ * constructed is a cycle with no bottom to it.
+ *
+ * A topic in another Account is allowed, and evaluated against the IAM of the
+ * Account owning it. Real S3 asks only that the topic is in the Bucket's
+ * Region, the same rule it applies to a destination queue.
+ */
+export declare class SimAwsS3NotificationTopics implements SimS3NotificationTopics {
+    private readonly simAws;
+    constructor(properties: SimAwsS3NotificationTopicsProperties);
+    /**
+     * Why S3 may not publish to the topic, or nothing when it may.
+     *
+     * The Region is this side's rule and the rest is the topic's own. What S3
+     * adds to the topic's decision is which Bucket is sending, so a policy
+     * granting one Bucket does not open the topic to another.
+     */
+    publishRefusal(request: SimS3NotificationDestinationRequest): string | undefined;
+    /**
+     * Publish the event document to the topic.
+     */
+    publish(request: SimS3NotificationDestinationRequest, body: string): Promise<void>;
+    private topic;
+}
+export {};
+//# sourceMappingURL=sim-aws-s3-notification-topics.d.ts.map

package/dist/service/s3/notification/destination/sns/sim-aws-s3-notification-topics.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-aws-s3-notification-topics.d.ts","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-aws-s3-notification-topics.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,EAAE,MAAM,4BAA4B,CAAC;AACzD,OAAO,KAAK,EAAE,mCAAmC,EAAE,MAAM,uCAAuC,CAAC;AAGjG,OAAO,KAAK,EAAE,uBAAuB,EAAE,MAAM,iCAAiC,CAAC;AAE/E,UAAU,oCAAoC;IAC5C,QAAQ,CAAC,MAAM,EAAE,MAAM,CAAC;CACzB;AAED;;;;;;;;;;;;GAYG;AACH,qBAAa,0BAA2B,YAAW,uBAAuB;IACxE,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAS;IAEhC,YAAY,UAAU,EAAE,oCAAoC,EAE3D;IAED;;;;;;OAMG;IACH,cAAc,CACZ,OAAO,EAAE,mCAAmC,GAC3C,MAAM,GAAG,SAAS,CAYpB;IAED;;OAEG;IACG,OAAO,CACX,OAAO,EAAE,mCAAmC,EAC5C,IAAI,EAAE,MAAM,GACX,OAAO,CAAC,IAAI,CAAC,CAIf;IAED,OAAO,CAAC,KAAK;CAMd"}

package/dist/service/s3/notification/destination/sns/sim-aws-s3-notification-topics.js

@@ -0,0 +1,50 @@
+import { SimS3NotificationTopic } from "./sim-s3-notification-topic.js";
+import { SimS3NotificationTopicArn } from "./sim-s3-notification-topic-arn.js";
+/**
+ * The simulated SNS topics of one simulated AWS instance, as S3 notification
+ * destinations.
+ *
+ * Topics are looked up when a configuration is applied or an event is
+ * delivered, never when this is built, for the same reason the other
+ * destinations do it that way: reaching another service while this one is being
+ * constructed is a cycle with no bottom to it.
+ *
+ * A topic in another Account is allowed, and evaluated against the IAM of the
+ * Account owning it. Real S3 asks only that the topic is in the Bucket's
+ * Region, the same rule it applies to a destination queue.
+ */
+export class SimAwsS3NotificationTopics {
+    simAws;
+    constructor(properties) {
+        this.simAws = properties.simAws;
+    }
+    /**
+     * Why S3 may not publish to the topic, or nothing when it may.
+     *
+     * The Region is this side's rule and the rest is the topic's own. What S3
+     * adds to the topic's decision is which Bucket is sending, so a policy
+     * granting one Bucket does not open the topic to another.
+     */
+    publishRefusal(request) {
+        const arn = SimS3NotificationTopicArn.parse(request.destinationArn);
+        if (!arn.isIn(request.bucketRegionName)) {
+            return (`${request.destinationArn} is in ${arn.regionName}, and an S3 event ` +
+                "notification destination topic must be in the Bucket's Region, " +
+                `${request.bucketRegionName}.`);
+        }
+        return this.topic(arn).publishRefusal(request);
+    }
+    /**
+     * Publish the event document to the topic.
+     */
+    async publish(request, body) {
+        await this.topic(SimS3NotificationTopicArn.parse(request.destinationArn)).publish(request, body);
+    }
+    topic(arn) {
+        return new SimS3NotificationTopic({
+            arn,
+            scope: this.simAws.accountRegionScope(arn.accountId, arn.regionName),
+        });
+    }
+}
+//# sourceMappingURL=sim-aws-s3-notification-topics.js.map

package/dist/service/s3/notification/destination/sns/sim-aws-s3-notification-topics.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-aws-s3-notification-topics.js","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-aws-s3-notification-topics.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,sBAAsB,EAAE,MAAM,gCAAgC,CAAC;AACxE,OAAO,EAAE,yBAAyB,EAAE,MAAM,oCAAoC,CAAC;AAO/E;;;;;;;;;;;;GAYG;AACH,MAAM,OAAO,0BAA0B;IACpB,MAAM,CAAS;IAEhC,YAAY,UAAgD;QAC1D,IAAI,CAAC,MAAM,GAAG,UAAU,CAAC,MAAM,CAAC;IAClC,CAAC;IAED;;;;;;OAMG;IACH,cAAc,CACZ,OAA4C;QAE5C,MAAM,GAAG,GAAG,yBAAyB,CAAC,KAAK,CAAC,OAAO,CAAC,cAAc,CAAC,CAAC;QAEpE,IAAI,CAAC,GAAG,CAAC,IAAI,CAAC,OAAO,CAAC,gBAAgB,CAAC,EAAE,CAAC;YACxC,OAAO,CACL,GAAG,OAAO,CAAC,cAAc,UAAU,GAAG,CAAC,UAAU,oBAAoB;gBACrE,iEAAiE;gBACjE,GAAG,OAAO,CAAC,gBAAgB,GAAG,CAC/B,CAAC;QACJ,CAAC;QAED,OAAO,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,cAAc,CAAC,OAAO,CAAC,CAAC;IACjD,CAAC;IAED;;OAEG;IACH,KAAK,CAAC,OAAO,CACX,OAA4C,EAC5C,IAAY;QAEZ,MAAM,IAAI,CAAC,KAAK,CACd,yBAAyB,CAAC,KAAK,CAAC,OAAO,CAAC,cAAc,CAAC,CACxD,CAAC,OAAO,CAAC,OAAO,EAAE,IAAI,CAAC,CAAC;IAC3B,CAAC;IAEO,KAAK,CAAC,GAA8B;QAC1C,OAAO,IAAI,sBAAsB,CAAC;YAChC,GAAG;YACH,KAAK,EAAE,IAAI,CAAC,MAAM,CAAC,kBAAkB,CAAC,GAAG,CAAC,SAAS,EAAE,GAAG,CAAC,UAAU,CAAC;SACrE,CAAC,CAAC;IACL,CAAC;CACF"}

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic-arn.d.ts

@@ -0,0 +1,31 @@
+import type { SimAwsAccountId } from "../../../../aws/sim-aws-account.js";
+import type { AwsRegionName } from "../../../../aws/sim-aws-region.js";
+/**
+ * The SNS topic ARN a notification configuration names.
+ *
+ * A topic ARN has no resource type segment, so the topic name follows the
+ * Account id directly, which is why the shared ARN reader cannot read one and
+ * SNS's own reader is borrowed here instead.
+ */
+export declare class SimS3NotificationTopicArn {
+    readonly regionName: AwsRegionName;
+    readonly accountId: SimAwsAccountId;
+    readonly topicName: string;
+    readonly value: string;
+    private constructor();
+    /**
+     * Read an SNS topic ARN, refusing anything else.
+     *
+     * A FIFO topic is refused by its name, as real S3 refuses one as an event
+     * notification destination. Simulated SNS has no FIFO topics either, so
+     * without this the refusal would be that the topic does not exist, which
+     * points at the wrong thing to fix.
+     */
+    static parse(arn: string): SimS3NotificationTopicArn;
+    /**
+     * Whether this topic is in a Region, which a destination topic has to share
+     * with the Bucket notifying it.
+     */
+    isIn(regionName: string): boolean;
+}
+//# sourceMappingURL=sim-s3-notification-topic-arn.d.ts.map

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic-arn.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-notification-topic-arn.d.ts","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-notification-topic-arn.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,oCAAoC,CAAC;AAC1E,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,mCAAmC,CAAC;AAOvE;;;;;;GAMG;AACH,qBAAa,yBAAyB;IACpC,SAAgB,UAAU,EAAE,aAAa,CAAC;IAC1C,SAAgB,SAAS,EAAE,eAAe,CAAC;IAC3C,SAAgB,SAAS,EAAE,MAAM,CAAC;IAClC,SAAgB,KAAK,EAAE,MAAM,CAAC;IAE9B,OAAO,eAUN;IAED;;;;;;;OAOG;IACH,MAAM,CAAC,KAAK,CAAC,GAAG,EAAE,MAAM,GAAG,yBAAyB,CAoBnD;IAED;;;OAGG;IACH,IAAI,CAAC,UAAU,EAAE,MAAM,GAAG,OAAO,CAEhC;CACF"}

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic-arn.js

@@ -0,0 +1,48 @@
+import { parseSnsTopicArn } from "../../../../sns/topic/sim-sns-topic-arn.js";
+import { SimS3InvalidArgument, SimS3NotImplemented, } from "../../../error/sim-s3.error.js";
+/**
+ * The SNS topic ARN a notification configuration names.
+ *
+ * A topic ARN has no resource type segment, so the topic name follows the
+ * Account id directly, which is why the shared ARN reader cannot read one and
+ * SNS's own reader is borrowed here instead.
+ */
+export class SimS3NotificationTopicArn {
+    regionName;
+    accountId;
+    topicName;
+    value;
+    constructor(regionName, accountId, topicName, value) {
+        this.regionName = regionName;
+        this.accountId = accountId;
+        this.topicName = topicName;
+        this.value = value;
+    }
+    /**
+     * Read an SNS topic ARN, refusing anything else.
+     *
+     * A FIFO topic is refused by its name, as real S3 refuses one as an event
+     * notification destination. Simulated SNS has no FIFO topics either, so
+     * without this the refusal would be that the topic does not exist, which
+     * points at the wrong thing to fix.
+     */
+    static parse(arn) {
+        const location = parseSnsTopicArn(arn);
+        if (location === undefined) {
+            throw new SimS3InvalidArgument(`${arn} is not an SNS topic ARN.`);
+        }
+        if (location.name.endsWith(".fifo")) {
+            throw new SimS3NotImplemented(`Cannot notify ${arn}: a FIFO topic is not a valid S3 event ` +
+                "notification destination, and simulated SNS has no FIFO topics.");
+        }
+        return new SimS3NotificationTopicArn(location.regionName, location.accountId, location.name, arn);
+    }
+    /**
+     * Whether this topic is in a Region, which a destination topic has to share
+     * with the Bucket notifying it.
+     */
+    isIn(regionName) {
+        return this.regionName === regionName;
+    }
+}
+//# sourceMappingURL=sim-s3-notification-topic-arn.js.map

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic-arn.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-notification-topic-arn.js","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-notification-topic-arn.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,gBAAgB,EAAE,MAAM,4CAA4C,CAAC;AAC9E,OAAO,EACL,oBAAoB,EACpB,mBAAmB,GACpB,MAAM,gCAAgC,CAAC;AAExC;;;;;;GAMG;AACH,MAAM,OAAO,yBAAyB;IACpB,UAAU,CAAgB;IAC1B,SAAS,CAAkB;IAC3B,SAAS,CAAS;IAClB,KAAK,CAAS;IAE9B,YACE,UAAyB,EACzB,SAA0B,EAC1B,SAAiB,EACjB,KAAa;QAEb,IAAI,CAAC,UAAU,GAAG,UAAU,CAAC;QAC7B,IAAI,CAAC,SAAS,GAAG,SAAS,CAAC;QAC3B,IAAI,CAAC,SAAS,GAAG,SAAS,CAAC;QAC3B,IAAI,CAAC,KAAK,GAAG,KAAK,CAAC;IACrB,CAAC;IAED;;;;;;;OAOG;IACH,MAAM,CAAC,KAAK,CAAC,GAAW;QACtB,MAAM,QAAQ,GAAG,gBAAgB,CAAC,GAAG,CAAC,CAAC;QAEvC,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;YAC3B,MAAM,IAAI,oBAAoB,CAAC,GAAG,GAAG,2BAA2B,CAAC,CAAC;QACpE,CAAC;QAED,IAAI,QAAQ,CAAC,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,EAAE,CAAC;YACpC,MAAM,IAAI,mBAAmB,CAC3B,iBAAiB,GAAG,yCAAyC;gBAC3D,iEAAiE,CACpE,CAAC;QACJ,CAAC;QAED,OAAO,IAAI,yBAAyB,CAClC,QAAQ,CAAC,UAA2B,EACpC,QAAQ,CAAC,SAA4B,EACrC,QAAQ,CAAC,IAAI,EACb,GAAG,CACJ,CAAC;IACJ,CAAC;IAED;;;OAGG;IACH,IAAI,CAAC,UAAkB;QACrB,OAAO,IAAI,CAAC,UAAU,KAAK,UAAU,CAAC;IACxC,CAAC;CACF"}

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic.d.ts

@@ -0,0 +1,43 @@
+import type { SimAwsAccountRegionContainer } from "../../../../aws/sim-aws-account-region-scope.js";
+import type { SimS3NotificationDestinationRequest } from "../sim-s3-notification-destination.js";
+import type { SimS3NotificationTopicArn } from "./sim-s3-notification-topic-arn.js";
+/**
+ * The subject real S3 publishes every event notification with.
+ *
+ * It is the same string for every Bucket and every event, so a subscriber
+ * cannot tell one notification from another by it. It is carried because the
+ * SNS envelope a queue receives has a `Subject` field in it, and leaving it out
+ * would make a simulated envelope differ from a real one for no reason.
+ */
+export declare const simS3NotificationSubject = "Amazon S3 Notification";
+interface SimS3NotificationTopicProperties {
+    readonly arn: SimS3NotificationTopicArn;
+    readonly scope: SimAwsAccountRegionContainer;
+}
+/**
+ * One topic an S3 Bucket is notifying, in the Account and Region its ARN names.
+ *
+ * Everything here is asked of the topic's own Account, which is what makes a
+ * topic in another Account reachable: its policy is the grant, and its
+ * Account's IAM is what evaluates it.
+ */
+export declare class SimS3NotificationTopic {
+    private readonly arn;
+    private readonly scope;
+    constructor(properties: SimS3NotificationTopicProperties);
+    /**
+     * Why S3 may not publish to this topic, or nothing when it may.
+     */
+    publishRefusal(request: SimS3NotificationDestinationRequest): string | undefined;
+    /**
+     * Publish one message body to this topic as the S3 service principal.
+     *
+     * This goes through the ordinary Publish path rather than handing the message
+     * to the topic's subscriptions directly, so a delivered event is the same
+     * thing an SDK caller would have published, and is authorized again on the
+     * way in.
+     */
+    publish(request: SimS3NotificationDestinationRequest, body: string): Promise<void>;
+}
+export {};
+//# sourceMappingURL=sim-s3-notification-topic.d.ts.map

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-notification-topic.d.ts","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-notification-topic.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,4BAA4B,EAAE,MAAM,iDAAiD,CAAC;AAEpG,OAAO,KAAK,EAAE,mCAAmC,EAAE,MAAM,uCAAuC,CAAC;AAEjG,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,oCAAoC,CAAC;AAEpF;;;;;;;GAOG;AACH,eAAO,MAAM,wBAAwB,2BAA2B,CAAC;AAEjE,UAAU,gCAAgC;IACxC,QAAQ,CAAC,GAAG,EAAE,yBAAyB,CAAC;IACxC,QAAQ,CAAC,KAAK,EAAE,4BAA4B,CAAC;CAC9C;AAED;;;;;;GAMG;AACH,qBAAa,sBAAsB;IACjC,OAAO,CAAC,QAAQ,CAAC,GAAG,CAA4B;IAChD,OAAO,CAAC,QAAQ,CAAC,KAAK,CAA+B;IAErD,YAAY,UAAU,EAAE,gCAAgC,EAGvD;IAED;;OAEG;IACH,cAAc,CACZ,OAAO,EAAE,mCAAmC,GAC3C,MAAM,GAAG,SAAS,CAyBpB;IAED;;;;;;;OAOG;IACG,OAAO,CACX,OAAO,EAAE,mCAAmC,EAC5C,IAAI,EAAE,MAAM,GACX,OAAO,CAAC,IAAI,CAAC,CAef;CACF"}

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic.js

@@ -0,0 +1,71 @@
+import { SimSnsServicePublishAuthorizer } from "../../../../sns/command/authorize/sim-sns-service-publish-authorizer.js";
+import { simS3ServicePrincipal } from "../sim-s3-service-principal.js";
+/**
+ * The subject real S3 publishes every event notification with.
+ *
+ * It is the same string for every Bucket and every event, so a subscriber
+ * cannot tell one notification from another by it. It is carried because the
+ * SNS envelope a queue receives has a `Subject` field in it, and leaving it out
+ * would make a simulated envelope differ from a real one for no reason.
+ */
+export const simS3NotificationSubject = "Amazon S3 Notification";
+/**
+ * One topic an S3 Bucket is notifying, in the Account and Region its ARN names.
+ *
+ * Everything here is asked of the topic's own Account, which is what makes a
+ * topic in another Account reachable: its policy is the grant, and its
+ * Account's IAM is what evaluates it.
+ */
+export class SimS3NotificationTopic {
+    arn;
+    scope;
+    constructor(properties) {
+        this.arn = properties.arn;
+        this.scope = properties.scope;
+    }
+    /**
+     * Why S3 may not publish to this topic, or nothing when it may.
+     */
+    publishRefusal(request) {
+        const topic = this.scope.sns().findTopic(this.arn.topicName);
+        if (topic === undefined) {
+            return `${request.destinationArn} is not a simulated SNS topic.`;
+        }
+        const decision = new SimSnsServicePublishAuthorizer({
+            iam: this.scope.iam(),
+        }).authorize({
+            topic,
+            servicePrincipal: simS3ServicePrincipal,
+            sourceArn: request.bucketArn,
+            sourceAccount: request.bucketOwnerAccountId,
+        });
+        if (decision.isDenied) {
+            return (`The topic policy of ${request.destinationArn} does not allow ` +
+                `${simS3ServicePrincipal} to publish to it for ${request.bucketArn}. ` +
+                "Grant sns:Publish with the topic's Policy attribute.");
+        }
+        return undefined;
+    }
+    /**
+     * Publish one message body to this topic as the S3 service principal.
+     *
+     * This goes through the ordinary Publish path rather than handing the message
+     * to the topic's subscriptions directly, so a delivered event is the same
+     * thing an SDK caller would have published, and is authorized again on the
+     * way in.
+     */
+    async publish(request, body) {
+        await this.scope.sns().publish({
+            input: {
+                TopicArn: this.arn.value,
+                Subject: simS3NotificationSubject,
+                Message: body,
+            },
+        }, {
+            caller: { kind: "service", service: simS3ServicePrincipal },
+            sourceArn: request.bucketArn,
+            sourceAccount: request.bucketOwnerAccountId,
+        });
+    }
+}
+//# sourceMappingURL=sim-s3-notification-topic.js.map

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topic.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-notification-topic.js","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-notification-topic.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,8BAA8B,EAAE,MAAM,yEAAyE,CAAC;AAEzH,OAAO,EAAE,qBAAqB,EAAE,MAAM,gCAAgC,CAAC;AAGvE;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,wBAAwB,CAAC;AAOjE;;;;;;GAMG;AACH,MAAM,OAAO,sBAAsB;IAChB,GAAG,CAA4B;IAC/B,KAAK,CAA+B;IAErD,YAAY,UAA4C;QACtD,IAAI,CAAC,GAAG,GAAG,UAAU,CAAC,GAAG,CAAC;QAC1B,IAAI,CAAC,KAAK,GAAG,UAAU,CAAC,KAAK,CAAC;IAChC,CAAC;IAED;;OAEG;IACH,cAAc,CACZ,OAA4C;QAE5C,MAAM,KAAK,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,EAAE,CAAC,SAAS,CAAC,IAAI,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAE7D,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;YACxB,OAAO,GAAG,OAAO,CAAC,cAAc,gCAAgC,CAAC;QACnE,CAAC;QAED,MAAM,QAAQ,GAAG,IAAI,8BAA8B,CAAC;YAClD,GAAG,EAAE,IAAI,CAAC,KAAK,CAAC,GAAG,EAAE;SACtB,CAAC,CAAC,SAAS,CAAC;YACX,KAAK;YACL,gBAAgB,EAAE,qBAAqB;YACvC,SAAS,EAAE,OAAO,CAAC,SAAS;YAC5B,aAAa,EAAE,OAAO,CAAC,oBAAoB;SAC5C,CAAC,CAAC;QAEH,IAAI,QAAQ,CAAC,QAAQ,EAAE,CAAC;YACtB,OAAO,CACL,uBAAuB,OAAO,CAAC,cAAc,kBAAkB;gBAC/D,GAAG,qBAAqB,yBAAyB,OAAO,CAAC,SAAS,IAAI;gBACtE,sDAAsD,CACvD,CAAC;QACJ,CAAC;QAED,OAAO,SAAS,CAAC;IACnB,CAAC;IAED;;;;;;;OAOG;IACH,KAAK,CAAC,OAAO,CACX,OAA4C,EAC5C,IAAY;QAEZ,MAAM,IAAI,CAAC,KAAK,CAAC,GAAG,EAAE,CAAC,OAAO,CAC5B;YACE,KAAK,EAAE;gBACL,QAAQ,EAAE,IAAI,CAAC,GAAG,CAAC,KAAK;gBACxB,OAAO,EAAE,wBAAwB;gBACjC,OAAO,EAAE,IAAI;aACd;SACF,EACD;YACE,MAAM,EAAE,EAAE,IAAI,EAAE,SAAS,EAAE,OAAO,EAAE,qBAAqB,EAAE;YAC3D,SAAS,EAAE,OAAO,CAAC,SAAS;YAC5B,aAAa,EAAE,OAAO,CAAC,oBAAoB;SAC5C,CACF,CAAC;IACJ,CAAC;CACF"}

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topics.d.ts

@@ -0,0 +1,22 @@
+import type { SimS3NotificationDestinationRequest } from "../sim-s3-notification-destination.js";
+/**
+ * The narrow slice of simulated SNS that S3 event notification needs.
+ *
+ * S3 asks two questions of a topic: whether it may publish to it, and then to
+ * publish to it. Both are asked by ARN, because a notification configuration
+ * names a topic by ARN and that ARN can name another Account.
+ */
+export interface SimS3NotificationTopics {
+    /**
+     * Why S3 may not publish to the topic, or nothing when it may.
+     *
+     * A reason rather than a boolean, because both the configuration-time refusal
+     * and the delivery-time record repeat it back to whoever has to fix it.
+     */
+    publishRefusal(request: SimS3NotificationDestinationRequest): string | undefined;
+    /**
+     * Publish one message body to the topic.
+     */
+    publish(request: SimS3NotificationDestinationRequest, body: string): Promise<void>;
+}
+//# sourceMappingURL=sim-s3-notification-topics.d.ts.map

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topics.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-notification-topics.d.ts","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-notification-topics.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,mCAAmC,EAAE,MAAM,uCAAuC,CAAC;AAEjG;;;;;;GAMG;AACH,MAAM,WAAW,uBAAuB;IACtC;;;;;OAKG;IACH,cAAc,CACZ,OAAO,EAAE,mCAAmC,GAC3C,MAAM,GAAG,SAAS,CAAC;IAEtB;;OAEG;IACH,OAAO,CACL,OAAO,EAAE,mCAAmC,EAC5C,IAAI,EAAE,MAAM,GACX,OAAO,CAAC,IAAI,CAAC,CAAC;CAClB"}

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topics.js

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=sim-s3-notification-topics.js.map

package/dist/service/s3/notification/destination/sns/sim-s3-notification-topics.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-notification-topics.js","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-notification-topics.ts"],"names":[],"mappings":""}

package/dist/service/s3/notification/destination/sns/sim-s3-sns-notification-destination.d.ts

@@ -0,0 +1,40 @@
+import type { SimS3NotificationDeliveryRequest, SimS3NotificationDestination, SimS3NotificationDestinationRequest } from "../sim-s3-notification-destination.js";
+import type { SimS3NotificationTopics } from "./sim-s3-notification-topics.js";
+interface SimS3SnsNotificationDestinationProperties {
+    readonly topics: SimS3NotificationTopics;
+}
+/**
+ * A simulated SNS topic as somewhere S3 sends Object events.
+ *
+ * The whole `Records` document is published as the message, which is the same
+ * text a queue destination receives as its message body. A subscriber reaching
+ * it through an SNS envelope therefore has two layers to parse rather than one:
+ * the envelope's `Message` is the S3 event document as text.
+ *
+ * The same question is asked twice on purpose, as it is for the other
+ * destinations. Real S3 checks the topic policy when the configuration is
+ * applied and checks it again for every event, so a permission removed
+ * afterwards stops delivery.
+ */
+export declare class SimS3SnsNotificationDestination implements SimS3NotificationDestination {
+    private readonly topics;
+    constructor(properties: SimS3SnsNotificationDestinationProperties);
+    /**
+     * Refuse a topic the Bucket may not publish to.
+     *
+     * Real S3 answers InvalidArgument for a destination it could not validate,
+     * which is what a topic policy that does not admit `s3.amazonaws.com`
+     * produces.
+     */
+    validate(request: SimS3NotificationDestinationRequest): void;
+    /**
+     * Publish the event document to the topic, if it still admits this Bucket.
+     *
+     * The refusal is asked for before publishing rather than left to the publish,
+     * which authorizes the same way, so that a topic policy saying no is recorded
+     * as a refusal rather than as a fault in the simulation.
+     */
+    deliver(request: SimS3NotificationDeliveryRequest): Promise<void>;
+}
+export {};
+//# sourceMappingURL=sim-s3-sns-notification-destination.d.ts.map

package/dist/service/s3/notification/destination/sns/sim-s3-sns-notification-destination.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-sns-notification-destination.d.ts","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-sns-notification-destination.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EACV,gCAAgC,EAChC,4BAA4B,EAC5B,mCAAmC,EACpC,MAAM,uCAAuC,CAAC;AAC/C,OAAO,KAAK,EAAE,uBAAuB,EAAE,MAAM,iCAAiC,CAAC;AAE/E,UAAU,yCAAyC;IACjD,QAAQ,CAAC,MAAM,EAAE,uBAAuB,CAAC;CAC1C;AAED;;;;;;;;;;;;GAYG;AACH,qBAAa,+BAAgC,YAAW,4BAA4B;IAClF,OAAO,CAAC,QAAQ,CAAC,MAAM,CAA0B;IAEjD,YAAY,UAAU,EAAE,yCAAyC,EAEhE;IAED;;;;;;OAMG;IACH,QAAQ,CAAC,OAAO,EAAE,mCAAmC,GAAG,IAAI,CAQ3D;IAED;;;;;;OAMG;IACG,OAAO,CAAC,OAAO,EAAE,gCAAgC,GAAG,OAAO,CAAC,IAAI,CAAC,CAatE;CACF"}

package/dist/service/s3/notification/destination/sns/sim-s3-sns-notification-destination.js

@@ -0,0 +1,51 @@
+import { jsonStringify } from "../../../../../util/type-guard/json.js";
+import { SimS3InvalidArgument } from "../../../error/sim-s3.error.js";
+import { SimS3NotificationNotPermitted } from "../../../error/sim-s3-notification.error.js";
+import { simS3EventRecordsDocument } from "../../event/sim-s3-event-records.js";
+/**
+ * A simulated SNS topic as somewhere S3 sends Object events.
+ *
+ * The whole `Records` document is published as the message, which is the same
+ * text a queue destination receives as its message body. A subscriber reaching
+ * it through an SNS envelope therefore has two layers to parse rather than one:
+ * the envelope's `Message` is the S3 event document as text.
+ *
+ * The same question is asked twice on purpose, as it is for the other
+ * destinations. Real S3 checks the topic policy when the configuration is
+ * applied and checks it again for every event, so a permission removed
+ * afterwards stops delivery.
+ */
+export class SimS3SnsNotificationDestination {
+    topics;
+    constructor(properties) {
+        this.topics = properties.topics;
+    }
+    /**
+     * Refuse a topic the Bucket may not publish to.
+     *
+     * Real S3 answers InvalidArgument for a destination it could not validate,
+     * which is what a topic policy that does not admit `s3.amazonaws.com`
+     * produces.
+     */
+    validate(request) {
+        const refusal = this.topics.publishRefusal(request);
+        if (refusal !== undefined) {
+            throw new SimS3InvalidArgument(`Unable to validate the following destination configurations: ${refusal}`);
+        }
+    }
+    /**
+     * Publish the event document to the topic, if it still admits this Bucket.
+     *
+     * The refusal is asked for before publishing rather than left to the publish,
+     * which authorizes the same way, so that a topic policy saying no is recorded
+     * as a refusal rather than as a fault in the simulation.
+     */
+    async deliver(request) {
+        const refusal = this.topics.publishRefusal(request);
+        if (refusal !== undefined) {
+            throw new SimS3NotificationNotPermitted(refusal);
+        }
+        await this.topics.publish(request, jsonStringify(simS3EventRecordsDocument(request.event, request.configurationId)));
+    }
+}
+//# sourceMappingURL=sim-s3-sns-notification-destination.js.map

package/dist/service/s3/notification/destination/sns/sim-s3-sns-notification-destination.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sim-s3-sns-notification-destination.js","sourceRoot":"","sources":["../../../../../../src/service/s3/notification/destination/sns/sim-s3-sns-notification-destination.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,MAAM,wCAAwC,CAAC;AACvE,OAAO,EAAE,oBAAoB,EAAE,MAAM,gCAAgC,CAAC;AACtE,OAAO,EAAE,6BAA6B,EAAE,MAAM,6CAA6C,CAAC;AAC5F,OAAO,EAAE,yBAAyB,EAAE,MAAM,qCAAqC,CAAC;AAYhF;;;;;;;;;;;;GAYG;AACH,MAAM,OAAO,+BAA+B;IACzB,MAAM,CAA0B;IAEjD,YAAY,UAAqD;QAC/D,IAAI,CAAC,MAAM,GAAG,UAAU,CAAC,MAAM,CAAC;IAClC,CAAC;IAED;;;;;;OAMG;IACH,QAAQ,CAAC,OAA4C;QACnD,MAAM,OAAO,GAAG,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC,OAAO,CAAC,CAAC;QAEpD,IAAI,OAAO,KAAK,SAAS,EAAE,CAAC;YAC1B,MAAM,IAAI,oBAAoB,CAC5B,gEAAgE,OAAO,EAAE,CAC1E,CAAC;QACJ,CAAC;IACH,CAAC;IAED;;;;;;OAMG;IACH,KAAK,CAAC,OAAO,CAAC,OAAyC;QACrD,MAAM,OAAO,GAAG,IAAI,CAAC,MAAM,CAAC,cAAc,CAAC,OAAO,CAAC,CAAC;QAEpD,IAAI,OAAO,KAAK,SAAS,EAAE,CAAC;YAC1B,MAAM,IAAI,6BAA6B,CAAC,OAAO,CAAC,CAAC;QACnD,CAAC;QAED,MAAM,IAAI,CAAC,MAAM,CAAC,OAAO,CACvB,OAAO,EACP,aAAa,CACX,yBAAyB,CAAC,OAAO,CAAC,KAAK,EAAE,OAAO,CAAC,eAAe,CAAC,CAClE,CACF,CAAC;IACJ,CAAC;CACF"}

package/dist/service/s3/object/s3-object-response-headers.d.ts

@@ -0,0 +1,17 @@
+/**
+ * The headers S3 sets on a read from what it was told when the Object was
+ * written.
+ *
+ * S3 keeps these as Object system metadata and hands them straight back,
+ * unchanged, on every read. That matters most for `Content-Encoding`: an Object
+ * stored as brotli and served without its encoding header is bytes no client
+ * can decode. `Cache-Control` matters for a different reason, being the only
+ * one of these a caller can set per Object rather than per response.
+ *
+ * Every path that serves an Object goes through here, so they agree on what
+ * reading one looks like.
+ *
+ * https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html
+ */
+export declare function simS3ObjectResponseHeaders(metadata: Readonly<Record<string, string>> | undefined, bodyLength: number): Record<string, string>;
+//# sourceMappingURL=s3-object-response-headers.d.ts.map

package/dist/service/s3/object/s3-object-response-headers.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"s3-object-response-headers.d.ts","sourceRoot":"","sources":["../../../../src/service/s3/object/s3-object-response-headers.ts"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;GAcG;AACH,wBAAgB,0BAA0B,CACxC,QAAQ,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC,GAAG,SAAS,EACtD,UAAU,EAAE,MAAM,GACjB,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAcxB"}

package/dist/service/s3/object/s3-object-response-headers.js

@@ -0,0 +1,29 @@
+import { simS3SystemMetadataHeaders } from "./s3-system-metadata.js";
+/**
+ * The headers S3 sets on a read from what it was told when the Object was
+ * written.
+ *
+ * S3 keeps these as Object system metadata and hands them straight back,
+ * unchanged, on every read. That matters most for `Content-Encoding`: an Object
+ * stored as brotli and served without its encoding header is bytes no client
+ * can decode. `Cache-Control` matters for a different reason, being the only
+ * one of these a caller can set per Object rather than per response.
+ *
+ * Every path that serves an Object goes through here, so they agree on what
+ * reading one looks like.
+ *
+ * https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html
+ */
+export function simS3ObjectResponseHeaders(metadata, bodyLength) {
+    const headers = {
+        "content-length": String(bodyLength),
+    };
+    for (const header of simS3SystemMetadataHeaders) {
+        const value = metadata?.[header.name];
+        if (value !== undefined) {
+            headers[header.name] = value;
+        }
+    }
+    return headers;
+}
+//# sourceMappingURL=s3-object-response-headers.js.map

package/dist/service/s3/object/s3-object-response-headers.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"s3-object-response-headers.js","sourceRoot":"","sources":["../../../../src/service/s3/object/s3-object-response-headers.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,0BAA0B,EAAE,MAAM,yBAAyB,CAAC;AAErE;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,0BAA0B,CACxC,QAAsD,EACtD,UAAkB;IAElB,MAAM,OAAO,GAA2B;QACtC,gBAAgB,EAAE,MAAM,CAAC,UAAU,CAAC;KACrC,CAAC;IAEF,KAAK,MAAM,MAAM,IAAI,0BAA0B,EAAE,CAAC;QAChD,MAAM,KAAK,GAAG,QAAQ,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,CAAC;QAEtC,IAAI,KAAK,KAAK,SAAS,EAAE,CAAC;YACxB,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,KAAK,CAAC;QAC/B,CAAC;IACH,CAAC;IAED,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/dist/service/s3/object/s3-system-metadata.d.ts

@@ -0,0 +1,32 @@
+/**
+ * One header S3 keeps about an Object when it is written and hands back,
+ * unchanged, on every read.
+ *
+ * The request field a write sets the header with and the key the value is
+ * stored under are paired here rather than in the write and read paths. Adding
+ * a header to the list below adds it to `PutObject` and to every endpoint that
+ * serves an Object at the same time, so the two sides cannot drift apart.
+ *
+ * https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html
+ */
+export declare class SimS3SystemMetadataHeader {
+    readonly field: SimS3SystemMetadataField;
+    readonly name: string;
+    constructor(field: SimS3SystemMetadataField, name: string);
+}
+/**
+ * The request field name a write sets a system metadata header with.
+ *
+ * These are the AWS SDK spellings, so an input carrying system metadata is
+ * indexable by them.
+ */
+export type SimS3SystemMetadataField = "CacheControl" | "ContentDisposition" | "ContentEncoding" | "ContentLanguage" | "ContentType" | "Expires";
+/**
+ * The system metadata S3 stores as a header and returns as one.
+ *
+ * Content length is not here because it describes the body rather than being
+ * remembered about it, and content type is set for almost every Object because
+ * a deployment or the console guesses one from the file extension.
+ */
+export declare const simS3SystemMetadataHeaders: readonly SimS3SystemMetadataHeader[];
+//# sourceMappingURL=s3-system-metadata.d.ts.map

package/dist/service/s3/object/s3-system-metadata.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"s3-system-metadata.d.ts","sourceRoot":"","sources":["../../../../src/service/s3/object/s3-system-metadata.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AACH,qBAAa,yBAAyB;aAElB,KAAK,EAAE,wBAAwB;aAC/B,IAAI,EAAE,MAAM;IAF9B,YACkB,KAAK,EAAE,wBAAwB,EAC/B,IAAI,EAAE,MAAM,EAC1B;CACL;AAED;;;;;GAKG;AACH,MAAM,MAAM,wBAAwB,GAChC,cAAc,GACd,oBAAoB,GACpB,iBAAiB,GACjB,iBAAiB,GACjB,aAAa,GACb,SAAS,CAAC;AAEd;;;;;;GAMG;AACH,eAAO,MAAM,0BAA0B,EAAE,SAAS,yBAAyB,EAQxE,CAAC"}