import * as core from "@terrascript/core";
export interface PosixProfileArgs extends core.SchemaArgs {
    gid: number | core.NumberOut;
    secondaryGids?: core.Array<number> | core.ArrayOut<core.NumberOut>;
    uid: number | core.NumberOut;
}
export declare class PosixProfile extends core.Schema<PosixProfileArgs> {
    gid: number | core.NumberOut;
    secondaryGids?: core.Array<number> | core.ArrayOut<core.NumberOut>;
    uid: number | core.NumberOut;
}
export interface HomeDirectoryMappingsArgs extends core.SchemaArgs {
    entry: string | core.StringOut;
    target: string | core.StringOut;
}
export declare class HomeDirectoryMappings extends core.Schema<HomeDirectoryMappingsArgs> {
    entry: string | core.StringOut;
    target: string | core.StringOut;
}
export interface AccessArgs extends core.ResourceArgs {
    /**
     * (Required) The SID of a group in the directory connected to the Transfer Server (e.g., `S-1-1-12-123
     * 4567890-123456789-1234567890-1234`)
     */
    externalId: string | core.StringOut;
    /**
     * (Optional) The landing directory (folder) for a user when they log in to the server using their SFTP
     * client.  It should begin with a `/`.  The first item in the path is the name of the home bucket (ac
     * cessible as `${Transfer:HomeBucket}` in the policy) and the rest is the home directory (accessible a
     * s `${Transfer:HomeDirectory}` in the policy). For example, `/example-bucket-1234/username` would set
     * the home bucket to `example-bucket-1234` and the home directory to `username`.
     */
    homeDirectory?: string | core.StringOut;
    /**
     * (Optional) Logical directory mappings that specify what S3 paths and keys should be visible to your
     * user and how you want to make them visible. See [Home Directory Mappings](#home-directory-mappings)
     * below.
     */
    homeDirectoryMappings?: core.Array<HomeDirectoryMappings> | core.ArrayOut<HomeDirectoryMappings>;
    /**
     * (Optional) The type of landing directory (folder) you mapped for your users' home directory. Valid v
     * alues are `PATH` and `LOGICAL`.
     */
    homeDirectoryType?: string | core.StringOut;
    /**
     * (Optional) An IAM JSON policy document that scopes down user access to portions of their Amazon S3 b
     * ucket. IAM variables you can use inside this policy include `${Transfer:UserName}`, `${Transfer:Home
     * Directory}`, and `${Transfer:HomeBucket}`. Since the IAM variable syntax matches Terraform's interpo
     * lation syntax, they must be escaped inside Terraform configuration strings (`$${Transfer:UserName}`)
     * .  These are evaluated on-the-fly when navigating the bucket.
     */
    policy?: string | core.StringOut;
    /**
     * (Optional) Specifies the full POSIX identity, including user ID (Uid), group ID (Gid), and any secon
     * dary groups IDs (SecondaryGids), that controls your users' access to your Amazon EFS file systems. S
     * ee [Posix Profile](#posix-profile) below.
     */
    posixProfile?: PosixProfile;
    /**
     * (Required) Amazon Resource Name (ARN) of an IAM role that allows the service to controls your user’s
     * access to your Amazon S3 bucket.
     */
    role?: string | core.StringOut;
    /**
     * (Required) The Server ID of the Transfer Server (e.g., `s-12345678`)
     */
    serverId: string | core.StringOut;
}
export declare class Access extends core.Resource<AccessArgs> {
    /**
     * (Required) The SID of a group in the directory connected to the Transfer Server (e.g., `S-1-1-12-123
     * 4567890-123456789-1234567890-1234`)
     */
    externalId: string | core.StringOut;
    /**
     * (Optional) The landing directory (folder) for a user when they log in to the server using their SFTP
     * client.  It should begin with a `/`.  The first item in the path is the name of the home bucket (ac
     * cessible as `${Transfer:HomeBucket}` in the policy) and the rest is the home directory (accessible a
     * s `${Transfer:HomeDirectory}` in the policy). For example, `/example-bucket-1234/username` would set
     * the home bucket to `example-bucket-1234` and the home directory to `username`.
     */
    homeDirectory?: string | core.StringOut;
    /**
     * (Optional) Logical directory mappings that specify what S3 paths and keys should be visible to your
     * user and how you want to make them visible. See [Home Directory Mappings](#home-directory-mappings)
     * below.
     */
    homeDirectoryMappings?: core.Array<HomeDirectoryMappings> | core.ArrayOut<HomeDirectoryMappings>;
    /**
     * (Optional) The type of landing directory (folder) you mapped for your users' home directory. Valid v
     * alues are `PATH` and `LOGICAL`.
     */
    homeDirectoryType?: string | core.StringOut;
    id: string | core.StringOut;
    /**
     * (Optional) An IAM JSON policy document that scopes down user access to portions of their Amazon S3 b
     * ucket. IAM variables you can use inside this policy include `${Transfer:UserName}`, `${Transfer:Home
     * Directory}`, and `${Transfer:HomeBucket}`. Since the IAM variable syntax matches Terraform's interpo
     * lation syntax, they must be escaped inside Terraform configuration strings (`$${Transfer:UserName}`)
     * .  These are evaluated on-the-fly when navigating the bucket.
     */
    policy?: string | core.StringOut;
    /**
     * (Optional) Specifies the full POSIX identity, including user ID (Uid), group ID (Gid), and any secon
     * dary groups IDs (SecondaryGids), that controls your users' access to your Amazon EFS file systems. S
     * ee [Posix Profile](#posix-profile) below.
     */
    posixProfile?: PosixProfile;
    /**
     * (Required) Amazon Resource Name (ARN) of an IAM role that allows the service to controls your user’s
     * access to your Amazon S3 bucket.
     */
    role?: string | core.StringOut;
    /**
     * (Required) The Server ID of the Transfer Server (e.g., `s-12345678`)
     */
    serverId: string | core.StringOut;
    constructor(name: string, args?: AccessArgs);
    getNamespace(): string;
}
//# sourceMappingURL=access.d.ts.map