WindowsFileSystem is the Schema for the WindowsFileSystems API. Manages a FSx Windows File System.
Type
CRD
Group
fsx.aws.upbound.io
Version
v1beta1
apiVersion: fsx.aws.upbound.io/v1beta1
kind: WindowsFileSystem
WindowsFileSystemSpec defines the desired state of WindowsFileSystem
No description provided.
Reference to a Directory in ds to populate activeDirectoryId.
Policies for referencing.
Selector for a Directory in ds to populate activeDirectoryId.
Policies for selection.
An array DNS alias names that you want to associate with the Amazon FSx file system. For more information, see Working with DNS Aliases
The configuration that Amazon FSx for Windows File Server uses to audit and log user accesses of files, folders, and file shares on the Amazon FSx for Windows File Server file system. See below.
Reference to a Key in kms to populate kmsKeyId.
Policies for referencing.
Selector for a Key in kms to populate kmsKeyId.
Policies for selection.
References to SecurityGroup in ec2 to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroupIds.
Policies for selection.
A list of IDs for the security groups that apply to the specified network interfaces created for file system access. These security groups will apply to all network interfaces.
Configuration block that Amazon FSx uses to join the Windows File Server instance to your self-managed (including on-premises) Microsoft Active Directory (AD) directory. Cannot be specified with active_directory_id. Detailed below.
A list of up to two IP addresses of DNS servers or domain controllers in the self-managed AD directory. The IP addresses need to be either in the same VPC CIDR range as the file system or in the private IP version 4 (IPv4) address ranges as specified in RFC 1918.
References to Subnet in ec2 to populate subnetIds.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnetIds.
Policies for selection.
A list of IDs for the subnets that the file system will be accessible from. To specify more than a single subnet set deployment_type to MULTI_AZ_1.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
WindowsFileSystemStatus defines the observed state of WindowsFileSystem.
No description provided.
Set of Elastic Network Interface identifiers from which the file system is accessible.
Conditions of the resource.
example
apiVersion: fsx.aws.upbound.io/v1beta1
kind: WindowsFileSystem
metadata:
annotations:
meta.upbound.io/example-id: fsx/v1beta1/windowsfilesystem
uptest.upbound.io/timeout: "7200"
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
activeDirectoryIdSelector:
matchLabels:
testing.upbound.io/example-name: bar
kmsKeyIdSelector:
matchLabels:
testing.upbound.io/example-name: sample-key
region: us-east-1
skipFinalBackup: true
storageCapacity: 32
subnetIdRefs:
- name: foo
throughputCapacity: 8
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.