@propulsionworks/cloudformation 0.0.1 → 0.1.0

package/out/exports/resources.generated/aws-eks-addon.d.ts

@@ -0,0 +1,82 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EKSAddon = ResourceDefinitionWithAttributes<"AWS::EKS::Addon", EKSAddonProps, EKSAddonAttribs>;
+/**
+ * Creates an Amazon EKS add-on.
+ *
+ * Amazon EKS add-ons help to automate the provisioning and lifecycle management of common operational software for Amazon EKS clusters. For more information, see [Amazon EKS add-ons](https://docs.aws.amazon.com/eks/latest/userguide/eks-add-ons.html) in the *Amazon EKS User Guide* .
+ */
+export type EKSAddonProps = {
+    /**
+     * The name of the add-on.
+     * @minLength 1
+     */
+    AddonName: string;
+    /**
+     * The version of the add-on.
+     * @minLength 1
+     */
+    AddonVersion?: string | undefined;
+    /**
+     * The name of your cluster.
+     * @minLength 1
+     */
+    ClusterName: string;
+    /**
+     * The configuration values that you provided.
+     * @minLength 1
+     */
+    ConfigurationValues?: string | undefined;
+    /**
+     * An array of Pod Identity Assocations owned by the Addon. Each EKS Pod Identity association maps a role to a service account in a namespace in the cluster.
+     *
+     * For more information, see [Attach an IAM Role to an Amazon EKS add-on using Pod Identity](https://docs.aws.amazon.com/eks/latest/userguide/add-ons-iam.html) in the *Amazon EKS User Guide* .
+     */
+    PodIdentityAssociations?: PodIdentityAssociation[] | undefined;
+    /**
+     * Specifying this option preserves the add-on software on your cluster but Amazon EKS stops managing any settings for the add-on. If an IAM account is associated with the add-on, it isn't removed.
+     */
+    PreserveOnDelete?: boolean | undefined;
+    /**
+     * How to resolve field value conflicts for an Amazon EKS add-on. Conflicts are handled based on the value you choose:
+     *
+     * - *None* – If the self-managed version of the add-on is installed on your cluster, Amazon EKS doesn't change the value. Creation of the add-on might fail.
+     * - *Overwrite* – If the self-managed version of the add-on is installed on your cluster and the Amazon EKS default value is different than the existing value, Amazon EKS changes the value to the Amazon EKS default value.
+     * - *Preserve* – This is similar to the NONE option. If the self-managed version of the add-on is installed on your cluster Amazon EKS doesn't change the add-on resource properties. Creation of the add-on might fail if conflicts are detected. This option works differently during the update operation. For more information, see [`UpdateAddon`](https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateAddon.html) .
+     *
+     * If you don't currently have the self-managed version of the add-on installed on your cluster, the Amazon EKS add-on is installed. Amazon EKS sets all values to default values, regardless of the option that you specify.
+     * @minLength 1
+     */
+    ResolveConflicts?: "NONE" | "OVERWRITE" | "PRESERVE" | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of an existing IAM role to bind to the add-on's service account. The role must be assigned the IAM permissions required by the add-on. If you don't specify an existing IAM role, then the add-on uses the permissions assigned to the node IAM role. For more information, see [Amazon EKS node IAM role](https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html) in the *Amazon EKS User Guide* .
+     *
+     * > To specify an existing IAM role, you must have an IAM OpenID Connect (OIDC) provider created for your cluster. For more information, see [Enabling IAM roles for service accounts on your cluster](https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html) in the *Amazon EKS User Guide* .
+     * @minLength 1
+     */
+    ServiceAccountRoleArn?: string | undefined;
+    /**
+     * The metadata that you apply to the add-on to assist with categorization and organization. Each tag consists of a key and an optional value, both of which you define. Add-on tags do not propagate to any other resources associated with the cluster.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type EKSAddonAttribs = {
+    /**
+     * The ARN of the add-on, such as `arn:aws:eks:us-west-2:111122223333:addon/1-19/vpc-cni/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx` .
+     */
+    Arn: string;
+};
+/**
+ * Amazon EKS Pod Identity associations provide the ability to manage credentials for your applications, similar to the way that Amazon EC2 instance profiles provide credentials to Amazon EC2 instances.
+ */
+export type PodIdentityAssociation = {
+    /**
+     * The Amazon Resource Name (ARN) of the IAM role to associate with the service account. The EKS Pod Identity agent manages credentials to assume this role for applications in the containers in the pods that use this service account.
+     * @pattern ^arn:aws(-cn|-us-gov|-iso(-[a-z])?)?:iam::\d{12}:(role)\/*
+     */
+    RoleArn: string;
+    /**
+     * The name of the Kubernetes service account inside the cluster to associate the IAM credentials with.
+     */
+    ServiceAccount: string;
+};
+//# sourceMappingURL=aws-eks-addon.d.ts.map

package/out/exports/resources.generated/aws-eks-cluster.d.ts

@@ -0,0 +1,458 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EKSCluster = ResourceDefinitionWithAttributes<"AWS::EKS::Cluster", EKSClusterProps, EKSClusterAttribs>;
+/**
+ * Creates an Amazon EKS control plane.
+ *
+ * The Amazon EKS control plane consists of control plane instances that run the Kubernetes software, such as `etcd` and the API server. The control plane runs in an account managed by AWS , and the Kubernetes API is exposed by the Amazon EKS API server endpoint. Each Amazon EKS cluster control plane is single tenant and unique. It runs on its own set of Amazon EC2 instances.
+ *
+ * The cluster control plane is provisioned across multiple Availability Zones and fronted by an Elastic Load Balancing Network Load Balancer. Amazon EKS also provisions elastic network interfaces in your VPC subnets to provide connectivity from the control plane instances to the nodes (for example, to support `kubectl exec` , `logs` , and `proxy` data flows).
+ *
+ * Amazon EKS nodes run in your AWS account and connect to your cluster's control plane over the Kubernetes API server endpoint and a certificate file that is created for your cluster.
+ *
+ * You can use the `endpointPublicAccess` and `endpointPrivateAccess` parameters to enable or disable public and private access to your cluster's Kubernetes API server endpoint. By default, public access is enabled, and private access is disabled. For more information, see [Amazon EKS Cluster Endpoint Access Control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) in the **Amazon EKS User Guide** .
+ *
+ * You can use the `logging` parameter to enable or disable exporting the Kubernetes control plane logs for your cluster to CloudWatch Logs. By default, cluster control plane logs aren't exported to CloudWatch Logs. For more information, see [Amazon EKS Cluster Control Plane Logs](https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html) in the **Amazon EKS User Guide** .
+ *
+ * > CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported control plane logs. For more information, see [CloudWatch Pricing](https://docs.aws.amazon.com/cloudwatch/pricing/) .
+ *
+ * In most cases, it takes several minutes to create a cluster. After you create an Amazon EKS cluster, you must configure your Kubernetes tooling to communicate with the API server and launch nodes into your cluster. For more information, see [Allowing users to access your cluster](https://docs.aws.amazon.com/eks/latest/userguide/cluster-auth.html) and [Launching Amazon EKS nodes](https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html) in the *Amazon EKS User Guide* .
+ */
+export type EKSClusterProps = {
+    /**
+     * The access configuration for the cluster.
+     */
+    AccessConfig?: AccessConfig | undefined;
+    /**
+     * If you set this value to `False` when creating a cluster, the default networking add-ons will not be installed.
+     *
+     * The default networking addons include vpc-cni, coredns, and kube-proxy.
+     *
+     * Use this option when you plan to install third-party alternative add-ons or self-manage the default networking add-ons.
+     */
+    BootstrapSelfManagedAddons?: boolean | undefined;
+    /**
+     * Indicates the current configuration of the compute capability on your EKS Auto Mode cluster. For example, if the capability is enabled or disabled. If the compute capability is enabled, EKS Auto Mode will create and delete EC2 Managed Instances in your AWS account. For more information, see EKS Auto Mode compute capability in the *Amazon EKS User Guide* .
+     */
+    ComputeConfig?: ComputeConfig | undefined;
+    /**
+     * The encryption configuration for the cluster.
+     */
+    EncryptionConfig?: EncryptionConfig[] | undefined;
+    /**
+     * Set this value to `true` to override upgrade-blocking readiness checks when updating a cluster.
+     * @default false
+     */
+    Force?: boolean | undefined;
+    /**
+     * The Kubernetes network configuration for the cluster.
+     */
+    KubernetesNetworkConfig?: KubernetesNetworkConfig | undefined;
+    /**
+     * The logging configuration for your cluster.
+     */
+    Logging?: Logging | undefined;
+    /**
+     * The unique name to give to your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the AWS Region and AWS account that you're creating the cluster in. Note that underscores can't be used in AWS CloudFormation .
+     * @minLength 1
+     * @maxLength 100
+     * @pattern ^[0-9A-Za-z][A-Za-z0-9\-_]*
+     */
+    Name?: string | undefined;
+    /**
+     * An object representing the configuration of your local Amazon EKS cluster on an AWS Outpost. This object isn't available for clusters on the AWS cloud.
+     */
+    OutpostConfig?: OutpostConfig | undefined;
+    /**
+     * The configuration in the cluster for EKS Hybrid Nodes. You can add, change, or remove this configuration after the cluster is created.
+     */
+    RemoteNetworkConfig?: RemoteNetworkConfig | undefined;
+    /**
+     * The VPC configuration that's used by the cluster control plane. Amazon EKS VPC resources have specific requirements to work properly with Kubernetes. For more information, see [Cluster VPC Considerations](https://docs.aws.amazon.com/eks/latest/userguide/network_reqs.html) and [Cluster Security Group Considerations](https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html) in the *Amazon EKS User Guide* . You must specify at least two subnets. You can specify up to five security groups, but we recommend that you use a dedicated security group for your cluster control plane.
+     */
+    ResourcesVpcConfig: ResourcesVpcConfig;
+    /**
+     * The Amazon Resource Name (ARN) of the IAM role that provides permissions for the Kubernetes control plane to make calls to AWS API operations on your behalf. For more information, see [Amazon EKS Service IAM Role](https://docs.aws.amazon.com/eks/latest/userguide/service_IAM_role.html) in the **Amazon EKS User Guide** .
+     */
+    RoleArn: string;
+    /**
+     * Indicates the current configuration of the block storage capability on your EKS Auto Mode cluster. For example, if the capability is enabled or disabled. If the block storage capability is enabled, EKS Auto Mode will create and delete EBS volumes in your AWS account. For more information, see EKS Auto Mode block storage capability in the *Amazon EKS User Guide* .
+     */
+    StorageConfig?: StorageConfig | undefined;
+    /**
+     * The metadata that you apply to the cluster to assist with categorization and organization. Each tag consists of a key and an optional value, both of which you define. Cluster tags don't propagate to any other resources associated with the cluster.
+     *
+     * > You must have the `eks:TagResource` and `eks:UntagResource` permissions for your [IAM principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html) to manage the AWS CloudFormation stack. If you don't have these permissions, there might be unexpected behavior with stack-level tags propagating to the resource during resource creation and update.
+     */
+    Tags?: Tag[] | undefined;
+    /**
+     * This value indicates if extended support is enabled or disabled for the cluster.
+     *
+     * [Learn more about EKS Extended Support in the *Amazon EKS User Guide* .](https://docs.aws.amazon.com/eks/latest/userguide/extended-support-control.html)
+     */
+    UpgradePolicy?: UpgradePolicy | undefined;
+    /**
+     * The desired Kubernetes version for your cluster. If you don't specify a value here, the default version available in Amazon EKS is used.
+     *
+     * > The default version might not be the latest version available.
+     * @pattern 1\.\d\d
+     */
+    Version?: string | undefined;
+    /**
+     * The configuration for zonal shift for the cluster.
+     */
+    ZonalShiftConfig?: ZonalShiftConfig | undefined;
+};
+export type EKSClusterAttribs = {
+    /**
+     * The ARN of the cluster, such as `arn:aws:eks:us-west-2:666666666666:cluster/prod` .
+     */
+    Arn: string;
+    /**
+     * The `certificate-authority-data` for your cluster.
+     */
+    CertificateAuthorityData: string;
+    /**
+     * The cluster security group that was created by Amazon EKS for the cluster. Managed node groups use this security group for control plane to data plane communication.
+     *
+     * This parameter is only returned by Amazon EKS clusters that support managed node groups. For more information, see [Managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html) in the *Amazon EKS User Guide* .
+     */
+    ClusterSecurityGroupId: string;
+    /**
+     * Amazon Resource Name (ARN) or alias of the customer master key (CMK).
+     */
+    EncryptionConfigKeyArn: string;
+    /**
+     * The endpoint for your Kubernetes API server, such as `https://5E1D0CEXAMPLEA591B746AFC5AB30262.yl4.us-west-2.eks.amazonaws.com` .
+     */
+    Endpoint: string;
+    /**
+     * The ID of your local Amazon EKS cluster on an AWS Outpost. This property isn't available for an Amazon EKS cluster on the AWS cloud.
+     */
+    Id: string;
+    /**
+     * The CIDR block that Kubernetes Service IP addresses are assigned from if you created a `1.21` or later cluster with version `>1.10.1` or later of the Amazon VPC CNI add-on and specified `ipv6` for *ipFamily* when you created the cluster. Kubernetes assigns Service addresses from the unique local address range ( `fc00::/7` ) because you can't specify a custom `IPv6` CIDR block when you create the cluster.
+     */
+    "KubernetesNetworkConfig.ServiceIpv6Cidr": string;
+    /**
+     * The issuer URL for the OIDC identity provider of the cluster, such as `https://oidc.eks.us-west-2.amazonaws.com/id/EXAMPLED539D4633E53DE1B716D3041E` . If you need to remove `https://` from this output value, you can include the following code in your template.
+     *
+     * `!Select [1, !Split ["//", !GetAtt EKSCluster.OpenIdConnectIssuerUrl]]`
+     */
+    OpenIdConnectIssuerUrl: string;
+};
+/**
+ * The access configuration for the cluster.
+ */
+export type AccessConfig = {
+    /**
+     * The desired authentication mode for the cluster. If you create a cluster by using the EKS API, AWS SDKs, or AWS CloudFormation , the default is `CONFIG_MAP` . If you create the cluster by using the AWS Management Console , the default value is `API_AND_CONFIG_MAP` .
+     */
+    AuthenticationMode?: "CONFIG_MAP" | "API_AND_CONFIG_MAP" | "API" | undefined;
+    /**
+     * Specifies whether or not the cluster creator IAM principal was set as a cluster admin access entry during cluster creation time. The default value is `true` .
+     */
+    BootstrapClusterCreatorAdminPermissions?: boolean | undefined;
+};
+/**
+ * Indicates the current configuration of the block storage capability on your EKS Auto Mode cluster. For example, if the capability is enabled or disabled. If the block storage capability is enabled, EKS Auto Mode will create and delete EBS volumes in your AWS account. For more information, see EKS Auto Mode block storage capability in the *Amazon EKS User Guide* .
+ */
+export type BlockStorage = {
+    /**
+     * Indicates if the block storage capability is enabled on your EKS Auto Mode cluster. If the block storage capability is enabled, EKS Auto Mode will create and delete EBS volumes in your AWS account.
+     */
+    Enabled?: boolean | undefined;
+};
+/**
+ * The cluster control plane logging configuration for your cluster.
+ *
+ * > When updating a resource, you must include this `ClusterLogging` property if the previous CloudFormation template of the resource had it.
+ */
+export type ClusterLogging = {
+    /**
+     * The enabled control plane logs for your cluster. All log types are disabled if the array is empty.
+     *
+     * > When updating a resource, you must include this `EnabledTypes` property if the previous CloudFormation template of the resource had it.
+     */
+    EnabledTypes?: LoggingTypeConfig[] | undefined;
+};
+/**
+ * Indicates the current configuration of the compute capability on your EKS Auto Mode cluster. For example, if the capability is enabled or disabled. If the compute capability is enabled, EKS Auto Mode will create and delete EC2 Managed Instances in your AWS account. For more information, see EKS Auto Mode compute capability in the *Amazon EKS User Guide* .
+ */
+export type ComputeConfig = {
+    /**
+     * Request to enable or disable the compute capability on your EKS Auto Mode cluster. If the compute capability is enabled, EKS Auto Mode will create and delete EC2 Managed Instances in your AWS account.
+     */
+    Enabled?: boolean | undefined;
+    /**
+     * Configuration for node pools that defines the compute resources for your EKS Auto Mode cluster. For more information, see EKS Auto Mode Node Pools in the *Amazon EKS User Guide* .
+     */
+    NodePools?: string[] | undefined;
+    /**
+     * The ARN of the IAM Role EKS will assign to EC2 Managed Instances in your EKS Auto Mode cluster. This value cannot be changed after the compute capability of EKS Auto Mode is enabled. For more information, see the IAM Reference in the *Amazon EKS User Guide* .
+     */
+    NodeRoleArn?: string | undefined;
+};
+/**
+ * The placement configuration for all the control plane instances of your local Amazon EKS cluster on an AWS Outpost. For more information, see [Capacity considerations](https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts-capacity-considerations.html) in the *Amazon EKS User Guide* .
+ */
+export type ControlPlanePlacement = {
+    /**
+     * The name of the placement group for the Kubernetes control plane instances. This property is only used for a local cluster on an AWS Outpost.
+     */
+    GroupName?: string | undefined;
+};
+/**
+ * Indicates the current configuration of the load balancing capability on your EKS Auto Mode cluster. For example, if the capability is enabled or disabled. For more information, see EKS Auto Mode load balancing capability in the *Amazon EKS User Guide* .
+ */
+export type ElasticLoadBalancing = {
+    /**
+     * Indicates if the load balancing capability is enabled on your EKS Auto Mode cluster. If the load balancing capability is enabled, EKS Auto Mode will create and delete load balancers in your AWS account.
+     */
+    Enabled?: boolean | undefined;
+};
+/**
+ * The encryption configuration for the cluster.
+ */
+export type EncryptionConfig = {
+    /**
+     * The encryption provider for the cluster.
+     */
+    Provider?: Provider | undefined;
+    /**
+     * Specifies the resources to be encrypted. The only supported value is `secrets` .
+     */
+    Resources?: string[] | undefined;
+};
+/**
+ * The Kubernetes network configuration for the cluster.
+ */
+export type KubernetesNetworkConfig = {
+    /**
+     * Request to enable or disable the load balancing capability on your EKS Auto Mode cluster. For more information, see EKS Auto Mode load balancing capability in the *Amazon EKS User Guide* .
+     */
+    ElasticLoadBalancing?: ElasticLoadBalancing | undefined;
+    /**
+     * Specify which IP family is used to assign Kubernetes pod and service IP addresses. If you don't specify a value, `ipv4` is used by default. You can only specify an IP family when you create a cluster and can't change this value once the cluster is created. If you specify `ipv6` , the VPC and subnets that you specify for cluster creation must have both `IPv4` and `IPv6` CIDR blocks assigned to them. You can't specify `ipv6` for clusters in China Regions.
+     *
+     * You can only specify `ipv6` for `1.21` and later clusters that use version `1.10.1` or later of the Amazon VPC CNI add-on. If you specify `ipv6` , then ensure that your VPC meets the requirements listed in the considerations listed in [Assigning IPv6 addresses to pods and services](https://docs.aws.amazon.com/eks/latest/userguide/cni-ipv6.html) in the *Amazon EKS User Guide* . Kubernetes assigns services `IPv6` addresses from the unique local address range `(fc00::/7)` . You can't specify a custom `IPv6` CIDR block. Pod addresses are assigned from the subnet's `IPv6` CIDR.
+     */
+    IpFamily?: "ipv4" | "ipv6" | undefined;
+    /**
+     * Don't specify a value if you select `ipv6` for *ipFamily* . The CIDR block to assign Kubernetes service IP addresses from. If you don't specify a block, Kubernetes assigns addresses from either the `10.100.0.0/16` or `172.20.0.0/16` CIDR blocks. We recommend that you specify a block that does not overlap with resources in other networks that are peered or connected to your VPC. The block must meet the following requirements:
+     *
+     * - Within one of the following private IP address blocks: `10.0.0.0/8` , `172.16.0.0/12` , or `192.168.0.0/16` .
+     * - Doesn't overlap with any CIDR block assigned to the VPC that you selected for VPC.
+     * - Between `/24` and `/12` .
+     *
+     * > You can only specify a custom CIDR block when you create a cluster. You can't change this value after the cluster is created.
+     */
+    ServiceIpv4Cidr?: string | undefined;
+};
+/**
+ * Enable or disable exporting the Kubernetes control plane logs for your cluster to CloudWatch Logs. By default, cluster control plane logs aren't exported to CloudWatch Logs. For more information, see [Amazon EKS Cluster control plane logs](https://docs.aws.amazon.com/eks/latest/userguide/control-plane-logs.html) in the **Amazon EKS User Guide** .
+ *
+ * > When updating a resource, you must include this `Logging` property if the previous CloudFormation template of the resource had it. > CloudWatch Logs ingestion, archive storage, and data scanning rates apply to exported control plane logs. For more information, see [CloudWatch Pricing](https://docs.aws.amazon.com/cloudwatch/pricing/) .
+ */
+export type Logging = {
+    /**
+     * The cluster control plane logging configuration for your cluster.
+     */
+    ClusterLogging?: ClusterLogging | undefined;
+};
+/**
+ * The enabled logging type. For a list of the valid logging types, see the [`types` property of `LogSetup`](https://docs.aws.amazon.com/eks/latest/APIReference/API_LogSetup.html#AmazonEKS-Type-LogSetup-types) in the *Amazon EKS API Reference* .
+ */
+export type LoggingTypeConfig = {
+    /**
+     * The name of the log type.
+     */
+    Type?: "api" | "audit" | "authenticator" | "controllerManager" | "scheduler" | undefined;
+};
+/**
+ * The configuration of your local Amazon EKS cluster on an AWS Outpost. Before creating a cluster on an Outpost, review [Creating a local cluster on an Outpost](https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts-local-cluster-create.html) in the *Amazon EKS User Guide* . This API isn't available for Amazon EKS clusters on the AWS cloud.
+ */
+export type OutpostConfig = {
+    /**
+     * The Amazon EC2 instance type that you want to use for your local Amazon EKS cluster on Outposts. Choose an instance type based on the number of nodes that your cluster will have. For more information, see [Capacity considerations](https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts-capacity-considerations.html) in the *Amazon EKS User Guide* .
+     *
+     * The instance type that you specify is used for all Kubernetes control plane instances. The instance type can't be changed after cluster creation. The control plane is not automatically scaled by Amazon EKS.
+     */
+    ControlPlaneInstanceType: string;
+    /**
+     * An object representing the placement configuration for all the control plane instances of your local Amazon EKS cluster on an AWS Outpost. For more information, see [Capacity considerations](https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts-capacity-considerations.html) in the *Amazon EKS User Guide* .
+     */
+    ControlPlanePlacement?: ControlPlanePlacement | undefined;
+    /**
+     * The ARN of the Outpost that you want to use for your local Amazon EKS cluster on Outposts. Only a single Outpost ARN is supported.
+     */
+    OutpostArns: string[];
+};
+/**
+ * Identifies the AWS Key Management Service ( AWS KMS ) key used to encrypt the secrets.
+ */
+export type Provider = {
+    /**
+     * Amazon Resource Name (ARN) or alias of the KMS key. The KMS key must be symmetric and created in the same AWS Region as the cluster. If the KMS key was created in a different account, the [IAM principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html) must have access to the KMS key. For more information, see [Allowing users in other accounts to use a KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html) in the *AWS Key Management Service Developer Guide* .
+     */
+    KeyArn?: string | undefined;
+};
+/**
+ * The configuration in the cluster for EKS Hybrid Nodes. You can add, change, or remove this configuration after the cluster is created.
+ */
+export type RemoteNetworkConfig = {
+    /**
+     * The list of network CIDRs that can contain hybrid nodes.
+     *
+     * These CIDR blocks define the expected IP address range of the hybrid nodes that join the cluster. These blocks are typically determined by your network administrator.
+     *
+     * Enter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example, `10.2.0.0/16` ).
+     *
+     * It must satisfy the following requirements:
+     *
+     * - Each block must be within an `IPv4` RFC-1918 network range. Minimum allowed size is /24, maximum allowed size is /8. Publicly-routable addresses aren't supported.
+     * - Each block cannot overlap with the range of the VPC CIDR blocks for your EKS resources, or the block of the Kubernetes service IP range.
+     * - Each block must have a route to the VPC that uses the VPC CIDR blocks, not public IPs or Elastic IPs. There are many options including AWS Transit Gateway , AWS Site-to-Site VPN , or AWS Direct Connect .
+     * - Each host must allow outbound connection to the EKS cluster control plane on TCP ports `443` and `10250` .
+     * - Each host must allow inbound connection from the EKS cluster control plane on TCP port 10250 for logs, exec and port-forward operations.
+     * - Each host must allow TCP and UDP network connectivity to and from other hosts that are running `CoreDNS` on UDP port `53` for service and pod DNS names.
+     */
+    RemoteNodeNetworks: RemoteNodeNetwork[];
+    /**
+     * The list of network CIDRs that can contain pods that run Kubernetes webhooks on hybrid nodes.
+     *
+     * These CIDR blocks are determined by configuring your Container Network Interface (CNI) plugin. We recommend the Calico CNI or Cilium CNI. Note that the Amazon VPC CNI plugin for Kubernetes isn't available for on-premises and edge locations.
+     *
+     * Enter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example, `10.2.0.0/16` ).
+     *
+     * It must satisfy the following requirements:
+     *
+     * - Each block must be within an `IPv4` RFC-1918 network range. Minimum allowed size is /24, maximum allowed size is /8. Publicly-routable addresses aren't supported.
+     * - Each block cannot overlap with the range of the VPC CIDR blocks for your EKS resources, or the block of the Kubernetes service IP range.
+     */
+    RemotePodNetworks?: RemotePodNetwork[] | undefined;
+};
+/**
+ * A network CIDR that can contain hybrid nodes.
+ *
+ * These CIDR blocks define the expected IP address range of the hybrid nodes that join the cluster. These blocks are typically determined by your network administrator.
+ *
+ * Enter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example, `10.2.0.0/16` ).
+ *
+ * It must satisfy the following requirements:
+ *
+ * - Each block must be within an `IPv4` RFC-1918 network range. Minimum allowed size is /24, maximum allowed size is /8. Publicly-routable addresses aren't supported.
+ * - Each block cannot overlap with the range of the VPC CIDR blocks for your EKS resources, or the block of the Kubernetes service IP range.
+ * - Each block must have a route to the VPC that uses the VPC CIDR blocks, not public IPs or Elastic IPs. There are many options including AWS Transit Gateway , AWS Site-to-Site VPN , or AWS Direct Connect .
+ * - Each host must allow outbound connection to the EKS cluster control plane on TCP ports `443` and `10250` .
+ * - Each host must allow inbound connection from the EKS cluster control plane on TCP port 10250 for logs, exec and port-forward operations.
+ * - Each host must allow TCP and UDP network connectivity to and from other hosts that are running `CoreDNS` on UDP port `53` for service and pod DNS names.
+ */
+export type RemoteNodeNetwork = {
+    /**
+     * A network CIDR that can contain hybrid nodes.
+     *
+     * These CIDR blocks define the expected IP address range of the hybrid nodes that join the cluster. These blocks are typically determined by your network administrator.
+     *
+     * Enter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example, `10.2.0.0/16` ).
+     *
+     * It must satisfy the following requirements:
+     *
+     * - Each block must be within an `IPv4` RFC-1918 network range. Minimum allowed size is /24, maximum allowed size is /8. Publicly-routable addresses aren't supported.
+     * - Each block cannot overlap with the range of the VPC CIDR blocks for your EKS resources, or the block of the Kubernetes service IP range.
+     * - Each block must have a route to the VPC that uses the VPC CIDR blocks, not public IPs or Elastic IPs. There are many options including AWS Transit Gateway , AWS Site-to-Site VPN , or AWS Direct Connect .
+     * - Each host must allow outbound connection to the EKS cluster control plane on TCP ports `443` and `10250` .
+     * - Each host must allow inbound connection from the EKS cluster control plane on TCP port 10250 for logs, exec and port-forward operations.
+     * - Each host must allow TCP and UDP network connectivity to and from other hosts that are running `CoreDNS` on UDP port `53` for service and pod DNS names.
+     */
+    Cidrs: string[];
+};
+/**
+ * A network CIDR that can contain pods that run Kubernetes webhooks on hybrid nodes.
+ *
+ * These CIDR blocks are determined by configuring your Container Network Interface (CNI) plugin. We recommend the Calico CNI or Cilium CNI. Note that the Amazon VPC CNI plugin for Kubernetes isn't available for on-premises and edge locations.
+ *
+ * Enter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example, `10.2.0.0/16` ).
+ *
+ * It must satisfy the following requirements:
+ *
+ * - Each block must be within an `IPv4` RFC-1918 network range. Minimum allowed size is /24, maximum allowed size is /8. Publicly-routable addresses aren't supported.
+ * - Each block cannot overlap with the range of the VPC CIDR blocks for your EKS resources, or the block of the Kubernetes service IP range.
+ */
+export type RemotePodNetwork = {
+    /**
+     * A network CIDR that can contain pods that run Kubernetes webhooks on hybrid nodes.
+     *
+     * These CIDR blocks are determined by configuring your Container Network Interface (CNI) plugin. We recommend the Calico CNI or Cilium CNI. Note that the Amazon VPC CNI plugin for Kubernetes isn't available for on-premises and edge locations.
+     *
+     * Enter one or more IPv4 CIDR blocks in decimal dotted-quad notation (for example, `10.2.0.0/16` ).
+     *
+     * It must satisfy the following requirements:
+     *
+     * - Each block must be within an `IPv4` RFC-1918 network range. Minimum allowed size is /24, maximum allowed size is /8. Publicly-routable addresses aren't supported.
+     * - Each block cannot overlap with the range of the VPC CIDR blocks for your EKS resources, or the block of the Kubernetes service IP range.
+     */
+    Cidrs: string[];
+};
+/**
+ * An object representing the VPC configuration to use for an Amazon EKS cluster.
+ *
+ * > When updating a resource, you must include these properties if the previous CloudFormation template of the resource had them:
+ * >
+ * > - `EndpointPublicAccess`
+ * > - `EndpointPrivateAccess`
+ * > - `PublicAccessCidrs`
+ */
+export type ResourcesVpcConfig = {
+    /**
+     * Set this value to `true` to enable private access for your cluster's Kubernetes API server endpoint. If you enable private access, Kubernetes API requests from within your cluster's VPC use the private VPC endpoint. The default value for this parameter is `false` , which disables private access for your Kubernetes API server. If you disable private access and you have nodes or AWS Fargate pods in the cluster, then ensure that `publicAccessCidrs` includes the necessary CIDR blocks for communication with the nodes or Fargate pods. For more information, see [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) in the **Amazon EKS User Guide** .
+     */
+    EndpointPrivateAccess?: boolean | undefined;
+    /**
+     * Set this value to `false` to disable public access to your cluster's Kubernetes API server endpoint. If you disable public access, your cluster's Kubernetes API server can only receive requests from within the cluster VPC. The default value for this parameter is `true` , which enables public access for your Kubernetes API server. For more information, see [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) in the **Amazon EKS User Guide** .
+     */
+    EndpointPublicAccess?: boolean | undefined;
+    /**
+     * The CIDR blocks that are allowed access to your cluster's public Kubernetes API server endpoint. Communication to the endpoint from addresses outside of the CIDR blocks that you specify is denied. The default value is `0.0.0.0/0` . If you've disabled private endpoint access, make sure that you specify the necessary CIDR blocks for every node and AWS Fargate `Pod` in the cluster. For more information, see [Amazon EKS cluster endpoint access control](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html) in the **Amazon EKS User Guide** .
+     */
+    PublicAccessCidrs?: string[] | undefined;
+    /**
+     * Specify one or more security groups for the cross-account elastic network interfaces that Amazon EKS creates to use that allow communication between your nodes and the Kubernetes control plane. If you don't specify any security groups, then familiarize yourself with the difference between Amazon EKS defaults for clusters deployed with Kubernetes. For more information, see [Amazon EKS security group considerations](https://docs.aws.amazon.com/eks/latest/userguide/sec-group-reqs.html) in the **Amazon EKS User Guide** .
+     */
+    SecurityGroupIds?: string[] | undefined;
+    /**
+     * Specify subnets for your Amazon EKS nodes. Amazon EKS creates cross-account elastic network interfaces in these subnets to allow communication between your nodes and the Kubernetes control plane.
+     */
+    SubnetIds: string[];
+};
+/**
+ * Request to update the configuration of the storage capability of your EKS Auto Mode cluster. For example, enable the capability. For more information, see EKS Auto Mode block storage capability in the *Amazon EKS User Guide* .
+ */
+export type StorageConfig = {
+    /**
+     * Request to configure EBS Block Storage settings for your EKS Auto Mode cluster.
+     */
+    BlockStorage?: BlockStorage | undefined;
+};
+/**
+ * The support policy to use for the cluster. Extended support allows you to remain on specific Kubernetes versions for longer. Clusters in extended support have higher costs. The default value is `EXTENDED` . Use `STANDARD` to disable extended support.
+ *
+ * [Learn more about EKS Extended Support in the *Amazon EKS User Guide* .](https://docs.aws.amazon.com/eks/latest/userguide/extended-support-control.html)
+ */
+export type UpgradePolicy = {
+    /**
+     * If the cluster is set to `EXTENDED` , it will enter extended support at the end of standard support. If the cluster is set to `STANDARD` , it will be automatically upgraded at the end of standard support.
+     *
+     * [Learn more about EKS Extended Support in the *Amazon EKS User Guide* .](https://docs.aws.amazon.com/eks/latest/userguide/extended-support-control.html)
+     */
+    SupportType?: "STANDARD" | "EXTENDED" | undefined;
+};
+/**
+ * The configuration for zonal shift for the cluster.
+ */
+export type ZonalShiftConfig = {
+    /**
+     * If zonal shift is enabled, AWS configures zonal autoshift for the cluster.
+     */
+    Enabled?: boolean | undefined;
+};
+//# sourceMappingURL=aws-eks-cluster.d.ts.map

package/out/exports/resources.generated/aws-eks-fargateprofile.d.ts

@@ -0,0 +1,82 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EKSFargateProfile = ResourceDefinitionWithAttributes<"AWS::EKS::FargateProfile", EKSFargateProfileProps, EKSFargateProfileAttribs>;
+/**
+ * Creates an AWS Fargate profile for your Amazon EKS cluster. You must have at least one Fargate profile in a cluster to be able to run pods on Fargate.
+ *
+ * The Fargate profile allows an administrator to declare which pods run on Fargate and specify which pods run on which Fargate profile. This declaration is done through the profile's selectors. Each profile can have up to five selectors that contain a namespace and labels. A namespace is required for every selector. The label field consists of multiple optional key-value pairs. Pods that match the selectors are scheduled on Fargate. If a to-be-scheduled pod matches any of the selectors in the Fargate profile, then that pod is run on Fargate.
+ *
+ * When you create a Fargate profile, you must specify a pod execution role to use with the pods that are scheduled with the profile. This role is added to the cluster's Kubernetes [Role Based Access Control](https://docs.aws.amazon.com/https://kubernetes.io/docs/reference/access-authn-authz/rbac/) (RBAC) for authorization so that the `kubelet` that is running on the Fargate infrastructure can register with your Amazon EKS cluster so that it can appear in your cluster as a node. The pod execution role also provides IAM permissions to the Fargate infrastructure to allow read access to Amazon ECR image repositories. For more information, see [Pod Execution Role](https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html) in the *Amazon EKS User Guide* .
+ *
+ * Fargate profiles are immutable. However, you can create a new updated profile to replace an existing profile and then delete the original after the updated profile has finished creating.
+ *
+ * If any Fargate profiles in a cluster are in the `DELETING` status, you must wait for that Fargate profile to finish deleting before you can create any other profiles in that cluster.
+ *
+ * For more information, see [AWS Fargate profile](https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html) in the *Amazon EKS User Guide* .
+ */
+export type EKSFargateProfileProps = {
+    /**
+     * The name of your cluster.
+     * @minLength 1
+     */
+    ClusterName: string;
+    /**
+     * The name of the Fargate profile.
+     * @minLength 1
+     */
+    FargateProfileName?: string | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of the `Pod` execution role to use for a `Pod` that matches the selectors in the Fargate profile. The `Pod` execution role allows Fargate infrastructure to register with your cluster as a node, and it provides read access to Amazon ECR image repositories. For more information, see [`Pod` execution role](https://docs.aws.amazon.com/eks/latest/userguide/pod-execution-role.html) in the *Amazon EKS User Guide* .
+     * @minLength 1
+     */
+    PodExecutionRoleArn: string;
+    /**
+     * The selectors to match for a `Pod` to use this Fargate profile. Each selector must have an associated Kubernetes `namespace` . Optionally, you can also specify `labels` for a `namespace` . You may specify up to five selectors in a Fargate profile.
+     */
+    Selectors: Selector[];
+    /**
+     * The IDs of subnets to launch a `Pod` into. A `Pod` running on Fargate isn't assigned a public IP address, so only private subnets (with no direct route to an Internet Gateway) are accepted for this parameter.
+     */
+    Subnets?: string[] | undefined;
+    /**
+     * Metadata that assists with categorization and organization. Each tag consists of a key and an optional value. You define both. Tags don't propagate to any other cluster or AWS resources.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type EKSFargateProfileAttribs = {
+    /**
+     * The ARN of the cluster, such as `arn:aws:eks:us-west-2:666666666666:fargateprofile/myCluster/myFargateProfile/1cb1a11a-1dc1-1d11-cf11-1111f11fa111` .
+     */
+    Arn: string;
+};
+/**
+ * A key-value pair.
+ */
+export type Label = {
+    /**
+     * Enter a key.
+     * @minLength 1
+     * @maxLength 127
+     */
+    Key: string;
+    /**
+     * Enter a value.
+     * @minLength 1
+     * @maxLength 255
+     */
+    Value: string;
+};
+/**
+ * An object representing an AWS Fargate profile selector.
+ */
+export type Selector = {
+    /**
+     * The Kubernetes labels that the selector should match. A pod must contain all of the labels that are specified in the selector for it to be considered a match.
+     */
+    Labels?: Label[] | undefined;
+    /**
+     * The Kubernetes `namespace` that the selector should match.
+     * @minLength 1
+     */
+    Namespace: string;
+};
+//# sourceMappingURL=aws-eks-fargateprofile.d.ts.map