@cfxlabsinc/b2b-services
    Preparing search index...
    interface AuroraCIUserArgs {
        accountId?: Input<string>;
        clusterResourceId: Input<string>;
        env: Input<string>;
        githubOrg?: Input<string>;
        githubRepo: Input<string>;
        permissionsBoundaryArn?: Input<string>;
        region?: Input<string>;
        subjectClaim?: Input<string>;
        username: Input<string>;
    }
    Index
    accountId?: Input<string>

    Defaults to caller identity.

    clusterResourceId: Input<string>

    Aurora cluster resource ID (cluster-XXXXXXXX). Exported by cfx-db as auroraClusterResourceId. Used to scope rds-db:connect to this cluster + username.

    env: Input<string>

    Environment tag (e.g. dev, prod). Also embedded in the role name.

    githubOrg?: Input<string>

    Org the repo lives under, in the OIDC subject claim. Defaults to CFXLabsInc.

    githubRepo: Input<string>

    GitHub repo (e.g. cfx-platform) whose Actions OIDC identity is trusted to assume the CI role. Assumed to live under the CFXLabsInc org.

    permissionsBoundaryArn?: Input<string>

    Optional permissions boundary. Defaults to cfx-workload-boundary.

    region?: Input<string>

    Defaults to the current provider region.

    subjectClaim?: Input<string>

    Restricts which workflow runs can assume the role, via the token.actions.githubusercontent.com:sub claim. Defaults to * (any branch / env). Tighten to e.g. environment:prod or ref:refs/heads/main for production deploys.

    username: Input<string>

    Postgres username that CI will authenticate as via IAM. Typically the <db>_ci role created by cfx-db and exported as <db>CiUsername. The component does not create the Postgres role — only the AWS-side IAM role + rds-db:connect inline policy that lets CI generate auth tokens for this user.