Optional ReadonlyadditionalSecurity groups granted ingress to all NiFi cluster EFS security groups. Per-cluster also supported.
ReadonlyadminAdmin roles with access to EKS cluster resources.
Optional ReadonlycaCA certificate validity period. Defaults to 6 days. Must be <7 days for ACM Private CA short-term certs.
Optional ReadonlycaTime before CA cert expiration to trigger renewal. Defaults to 12 hours.
Optional ReadonlycertCertificate key algorithm (e.g., RSA, ECDSA).
Optional ReadonlycertCertificate key size in bits (e.g., 2048, 4096).
Optional ReadonlyclustersNamed NiFi cluster configurations.
Optional ReadonlyeksIngress rules for the EKS control plane security group.
Optional ReadonlyexistingExisting ACM Private CA ARN for signing the internal CA. If omitted, a new CA is created.
Optional ReadonlymgmtOptional EC2 management instance for EKS cluster administration with kubectl access.
Optional ReadonlynodeNode certificate validity period. Defaults to 5 days. Must be <6 days for ACM Private CA short-term certs.
Optional ReadonlynodeTime before node cert expiration to trigger renewal. Defaults to 12 hours.
Optional ReadonlyregistryNiFi Registry configuration for flow versioning and template management.
Optional ReadonlysecurityGlobal egress rules for all NiFi cluster security groups. Per-cluster rules also supported.
Optional ReadonlysecurityIPv4 CIDRs granted ingress to all NiFi cluster security groups. Per-cluster also supported.
Optional ReadonlysecuritySecurity groups granted ingress to all NiFi cluster security groups. Per-cluster also supported.
ReadonlysubnetNamed subnet ID mappings for cluster deployment.
ReadonlyvpcVPC ID for EKS and NiFi cluster deployment.
NiFi deployment configuration for data flow orchestration and processing.
Defines the complete NiFi infrastructure including EKS cluster, networking, certificate management, and cluster configurations.
Use cases: Data flow orchestration; Multi-cluster NiFi deployment; EKS-based NiFi infrastructure
AWS: Apache NiFi configuration for EKS-based data flow orchestration
Validation: vpcId, subnetIds, and adminRoles required; clusters and registry optional