@cfxlabsinc/b2b-services
    Preparing search index...

    Variable S3_BUCKET_BASE_NAMESConst

    S3_BUCKET_BASE_NAMES: {
        bankDocuments: "cfx-bank-documents";
        bucketAccessLogs: "cfx-bucket-access-logs";
        cfxAch: "cfx-ach";
        coinflowAch: "cfx-ach-coinflow";
        customerDocuments: "cfx-customer-documents";
        entityDocuments: "cfx-entity-documents";
        entityDocumentsStaging: "cfx-entity-documents-staging";
        greendot: "cfx-greendot";
        identity: "cfx-identity";
        pulumiBackend: "cfx-pulumi-iac-backend";
        transactionFiles: "cfx-transaction-files";
        transactionFilesStaging: "cfx-transaction-files-staging";
        wireFile: "cfx-wire-file-bucket";
    } = ...

    Every CFX S3 bucket, by base name.

    The physical name is always <base>-<stack> — createBucket in packages/s3/pulumi builds it from these exact values, and consumers derive their grant ARNs from them. One definition, not a set of stack outputs plus a second copy in whichever stack grants access to them.

    This is what lets a consumer drop its cfx-s3 StackReference: the names were never AWS-generated, so reading them back over a stack boundary only moved a string this module already knows.

    Type Declaration

    • ReadonlybankDocuments: "cfx-bank-documents"
    • ReadonlybucketAccessLogs: "cfx-bucket-access-logs"
    • ReadonlycfxAch: "cfx-ach"
    • ReadonlycoinflowAch: "cfx-ach-coinflow"
    • ReadonlycustomerDocuments: "cfx-customer-documents"
    • ReadonlyentityDocuments: "cfx-entity-documents"
    • ReadonlyentityDocumentsStaging: "cfx-entity-documents-staging"
    • Readonlygreendot: "cfx-greendot"
    • Readonlyidentity: "cfx-identity"
    • ReadonlypulumiBackend: "cfx-pulumi-iac-backend"
    • ReadonlytransactionFiles: "cfx-transaction-files"
    • ReadonlytransactionFilesStaging: "cfx-transaction-files-staging"
    • ReadonlywireFile: "cfx-wire-file-bucket"

    Settings
    Member Visibility