@propulsionworks/cloudformation 0.0.1 → 0.1.0

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

@@ -0,0 +1,86 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EKSIdentityProviderConfig = ResourceDefinitionWithAttributes<"AWS::EKS::IdentityProviderConfig", EKSIdentityProviderConfigProps, EKSIdentityProviderConfigAttribs>;
+/**
+ * Associates an identity provider configuration to a cluster.
+ *
+ * If you want to authenticate identities using an identity provider, you can create an identity provider configuration and associate it to your cluster. After configuring authentication to your cluster you can create Kubernetes `Role` and `ClusterRole` objects, assign permissions to them, and then bind them to the identities using Kubernetes `RoleBinding` and `ClusterRoleBinding` objects. For more information see [Using RBAC Authorization](https://docs.aws.amazon.com/https://kubernetes.io/docs/reference/access-authn-authz/rbac/) in the Kubernetes documentation.
+ */
+export type EKSIdentityProviderConfigProps = {
+    /**
+     * The name of your cluster.
+     */
+    ClusterName: string;
+    /**
+     * The name of the configuration.
+     */
+    IdentityProviderConfigName?: string | undefined;
+    /**
+     * An object representing an OpenID Connect (OIDC) identity provider configuration.
+     */
+    Oidc?: OidcIdentityProviderConfig | 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;
+    /**
+     * The type of the identity provider configuration. The only type available is `oidc` .
+     */
+    Type: "oidc";
+};
+export type EKSIdentityProviderConfigAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) associated with the identity provider config.
+     */
+    IdentityProviderConfigArn: string;
+};
+/**
+ * An object representing the configuration for an OpenID Connect (OIDC) identity provider.
+ */
+export type OidcIdentityProviderConfig = {
+    /**
+     * This is also known as *audience* . The ID of the client application that makes authentication requests to the OIDC identity provider.
+     */
+    ClientId: string;
+    /**
+     * The JSON web token (JWT) claim that the provider uses to return your groups.
+     */
+    GroupsClaim?: string | undefined;
+    /**
+     * The prefix that is prepended to group claims to prevent clashes with existing names (such as `system:` groups). For example, the value `oidc:` creates group names like `oidc:engineering` and `oidc:infra` . The prefix can't contain `system:`
+     */
+    GroupsPrefix?: string | undefined;
+    /**
+     * The URL of the OIDC identity provider that allows the API server to discover public signing keys for verifying tokens.
+     */
+    IssuerUrl: string;
+    /**
+     * The key-value pairs that describe required claims in the identity token. If set, each claim is verified to be present in the token with a matching value.
+     */
+    RequiredClaims?: RequiredClaim[] | undefined;
+    /**
+     * The JSON Web token (JWT) claim that is used as the username.
+     */
+    UsernameClaim?: string | undefined;
+    /**
+     * The prefix that is prepended to username claims to prevent clashes with existing names. The prefix can't contain `system:`
+     */
+    UsernamePrefix?: string | undefined;
+};
+/**
+ * A key-value pair that describes a required claim in the identity token. If set, each claim is verified to be present in the token with a matching value.
+ */
+export type RequiredClaim = {
+    /**
+     * The key to match from the token.
+     * @minLength 1
+     * @maxLength 63
+     */
+    Key: string;
+    /**
+     * The value for the key from the token.
+     * @minLength 1
+     * @maxLength 253
+     */
+    Value: string;
+};
+//# sourceMappingURL=aws-eks-identityproviderconfig.d.ts.map

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

@@ -0,0 +1,236 @@
+import type { ResourceDefinitionWithAttributes } from "../main.ts";
+export type EKSNodegroup = ResourceDefinitionWithAttributes<"AWS::EKS::Nodegroup", EKSNodegroupProps, EKSNodegroupAttribs>;
+/**
+ * Creates a managed node group for an Amazon EKS cluster.
+ *
+ * You can only create a node group for your cluster that is equal to the current Kubernetes version for the cluster. All node groups are created with the latest AMI release version for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI using a launch template.
+ *
+ * For later updates, you will only be able to update a node group using a launch template only if it was originally deployed with a launch template. Additionally, the launch template ID or name must match what was used when the node group was created. You can update the launch template version with necessary changes. For more information about using launch templates, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) .
+ *
+ * An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that are managed by AWS for an Amazon EKS cluster. 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* .
+ *
+ * > Windows AMI types are only supported for commercial AWS Regions that support Windows on Amazon EKS.
+ */
+export type EKSNodegroupProps = {
+    /**
+     * The AMI type for your node group. If you specify `launchTemplate` , and your launch template uses a custom AMI, then don't specify `amiType` , or the node group deployment will fail. If your launch template uses a Windows custom AMI, then add `eks:kube-proxy-windows` to your Windows nodes `rolearn` in the `aws-auth` `ConfigMap` . For more information about using launch templates with Amazon EKS, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    AmiType?: string | undefined;
+    /**
+     * The capacity type of your managed node group.
+     */
+    CapacityType?: string | undefined;
+    /**
+     * The name of your cluster.
+     * @minLength 1
+     */
+    ClusterName: string;
+    /**
+     * The root device disk size (in GiB) for your node group instances. The default disk size is 20 GiB for Linux and Bottlerocket. The default disk size is 50 GiB for Windows. If you specify `launchTemplate` , then don't specify `diskSize` , or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    DiskSize?: number | undefined;
+    /**
+     * Force the update if any `Pod` on the existing node group can't be drained due to a `Pod` disruption budget issue. If an update fails because all Pods can't be drained, you can force the update after it fails to terminate the old node whether or not any `Pod` is running on the node.
+     * @default false
+     */
+    ForceUpdateEnabled?: boolean | undefined;
+    /**
+     * Specify the instance types for a node group. If you specify a GPU instance type, make sure to also specify an applicable GPU AMI type with the `amiType` parameter. If you specify `launchTemplate` , then you can specify zero or one instance type in your launch template *or* you can specify 0-20 instance types for `instanceTypes` . If however, you specify an instance type in your launch template *and* specify any `instanceTypes` , the node group deployment will fail. If you don't specify an instance type in a launch template or for `instanceTypes` , then `t3.medium` is used, by default. If you specify `Spot` for `capacityType` , then we recommend specifying multiple values for `instanceTypes` . For more information, see [Managed node group capacity types](https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html#managed-node-group-capacity-types) and [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    InstanceTypes?: string[] | undefined;
+    /**
+     * The Kubernetes `labels` applied to the nodes in the node group.
+     *
+     * > Only `labels` that are applied with the Amazon EKS API are shown here. There may be other Kubernetes `labels` applied to the nodes in this group.
+     */
+    Labels?: Record<string, string> | undefined;
+    /**
+     * An object representing a node group's launch template specification. When using this object, don't directly specify `instanceTypes` , `diskSize` , or `remoteAccess` . You cannot later specify a different launch template ID or name than what was used to create the node group.
+     *
+     * Make sure that the launch template meets the requirements in `launchTemplateSpecification` . Also refer to [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    LaunchTemplate?: LaunchTemplateSpecification | undefined;
+    /**
+     * The node auto repair configuration for the node group.
+     */
+    NodeRepairConfig?: NodeRepairConfig | undefined;
+    /**
+     * The Amazon Resource Name (ARN) of the IAM role to associate with your node group. The Amazon EKS worker node `kubelet` daemon makes calls to AWS APIs on your behalf. Nodes receive permissions for these API calls through an IAM instance profile and associated policies. Before you can launch nodes and register them into a cluster, you must create an IAM role for those nodes to use when they are launched. 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** . If you specify `launchTemplate` , then don't specify `[IamInstanceProfile](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_IamInstanceProfile.html)` in your launch template, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    NodeRole: string;
+    /**
+     * The unique name to give your node group.
+     * @minLength 1
+     */
+    NodegroupName?: string | undefined;
+    /**
+     * The AMI version of the Amazon EKS optimized AMI to use with your node group (for example, `1.14.7- *YYYYMMDD*` ). By default, the latest available AMI version for the node group's current Kubernetes version is used. For more information, see [Amazon EKS optimized Linux AMI Versions](https://docs.aws.amazon.com/eks/latest/userguide/eks-linux-ami-versions.html) in the *Amazon EKS User Guide* .
+     *
+     * > Changing this value triggers an update of the node group if one is available. You can't update other properties at the same time as updating `Release Version` .
+     */
+    ReleaseVersion?: string | undefined;
+    /**
+     * The remote access configuration to use with your node group. For Linux, the protocol is SSH. For Windows, the protocol is RDP. If you specify `launchTemplate` , then don't specify `remoteAccess` , or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    RemoteAccess?: RemoteAccess | undefined;
+    /**
+     * The scaling configuration details for the Auto Scaling group that is created for your node group.
+     */
+    ScalingConfig?: ScalingConfig | undefined;
+    /**
+     * The subnets to use for the Auto Scaling group that is created for your node group. If you specify `launchTemplate` , then don't specify `[SubnetId](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkInterface.html)` in your launch template, or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     */
+    Subnets: string[];
+    /**
+     * 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?: Record<string, string> | undefined;
+    /**
+     * The Kubernetes taints to be applied to the nodes in the node group when they are created. Effect is one of `No_Schedule` , `Prefer_No_Schedule` , or `No_Execute` . Kubernetes taints can be used together with tolerations to control how workloads are scheduled to your nodes. For more information, see [Node taints on managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/node-taints-managed-node-groups.html) .
+     */
+    Taints?: Taint[] | undefined;
+    /**
+     * The node group update configuration.
+     */
+    UpdateConfig?: UpdateConfig | undefined;
+    /**
+     * The Kubernetes version to use for your managed nodes. By default, the Kubernetes version of the cluster is used, and this is the only accepted specified value. If you specify `launchTemplate` , and your launch template uses a custom AMI, then don't specify `version` , or the node group deployment will fail. For more information about using launch templates with Amazon EKS, see [Launch template support](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+     *
+     * > You can't update other properties at the same time as updating `Version` .
+     */
+    Version?: string | undefined;
+};
+export type EKSNodegroupAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) associated with the managed node group.
+     */
+    Arn: string;
+    /**
+     * The name of your cluster.
+     * @minLength 1
+     */
+    ClusterName: string;
+    Id: string;
+    /**
+     * The name associated with an Amazon EKS managed node group.
+     * @minLength 1
+     */
+    NodegroupName: string;
+};
+/**
+ * An object representing a node group launch template specification. The launch template can't include [`SubnetId`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateNetworkInterface.html) , [`IamInstanceProfile`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_IamInstanceProfile.html) , [`RequestSpotInstances`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_RequestSpotInstances.html) , [`HibernationOptions`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_HibernationOptionsRequest.html) , or [`TerminateInstances`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_TerminateInstances.html) , or the node group deployment or update will fail. For more information about launch templates, see [`CreateLaunchTemplate`](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateLaunchTemplate.html) in the Amazon EC2 API Reference. For more information about using launch templates with Amazon EKS, see [Customizing managed nodes with launch templates](https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html) in the *Amazon EKS User Guide* .
+ *
+ * You must specify either the launch template ID or the launch template name in the request, but not both.
+ */
+export type LaunchTemplateSpecification = {
+    /**
+     * The ID of the launch template.
+     *
+     * You must specify either the launch template ID or the launch template name in the request, but not both. After node group creation, you cannot use a different ID.
+     * @minLength 1
+     */
+    Id?: string | undefined;
+    /**
+     * The name of the launch template.
+     *
+     * You must specify either the launch template name or the launch template ID in the request, but not both. After node group creation, you cannot use a different name.
+     * @minLength 1
+     */
+    Name?: string | undefined;
+    /**
+     * The version number of the launch template to use. If no version is specified, then the template's default version is used. You can use a different version for node group updates.
+     * @minLength 1
+     */
+    Version?: string | undefined;
+};
+/**
+ * The node auto repair configuration for the node group.
+ */
+export type NodeRepairConfig = {
+    /**
+     * Specifies whether to enable node auto repair for the node group. Node auto repair is disabled by default.
+     */
+    Enabled?: boolean | undefined;
+};
+/**
+ * An object representing the remote access configuration for the managed node group.
+ */
+export type RemoteAccess = {
+    /**
+     * The Amazon EC2 SSH key name that provides access for SSH communication with the nodes in the managed node group. For more information, see [Amazon EC2 key pairs and Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html) in the *Amazon Elastic Compute Cloud User Guide for Linux Instances* . For Windows, an Amazon EC2 SSH key is used to obtain the RDP password. For more information, see [Amazon EC2 key pairs and Windows instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-key-pairs.html) in the *Amazon Elastic Compute Cloud User Guide for Windows Instances* .
+     */
+    Ec2SshKey: string;
+    /**
+     * The security group IDs that are allowed SSH access (port 22) to the nodes. For Windows, the port is 3389. If you specify an Amazon EC2 SSH key but don't specify a source security group when you create a managed node group, then the port on the nodes is opened to the internet ( `0.0.0.0/0` ). For more information, see [Security Groups for Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) in the *Amazon Virtual Private Cloud User Guide* .
+     */
+    SourceSecurityGroups?: string[] | undefined;
+};
+/**
+ * An object representing the scaling configuration details for the Auto Scaling group that is associated with your node group. When creating a node group, you must specify all or none of the properties. When updating a node group, you can specify any or none of the properties.
+ */
+export type ScalingConfig = {
+    /**
+     * The current number of nodes that the managed node group should maintain.
+     *
+     * > If you use the Kubernetes [Cluster Autoscaler](https://docs.aws.amazon.com/https://github.com/kubernetes/autoscaler#kubernetes-autoscaler) , you shouldn't change the `desiredSize` value directly, as this can cause the Cluster Autoscaler to suddenly scale up or scale down.
+     *
+     * Whenever this parameter changes, the number of worker nodes in the node group is updated to the specified size. If this parameter is given a value that is smaller than the current number of running worker nodes, the necessary number of worker nodes are terminated to match the given value. When using CloudFormation, no action occurs if you remove this parameter from your CFN template.
+     *
+     * This parameter can be different from `minSize` in some cases, such as when starting with extra hosts for testing. This parameter can also be different when you want to start with an estimated number of needed hosts, but let the Cluster Autoscaler reduce the number if there are too many. When the Cluster Autoscaler is used, the `desiredSize` parameter is altered by the Cluster Autoscaler (but can be out-of-date for short periods of time). the Cluster Autoscaler doesn't scale a managed node group lower than `minSize` or higher than `maxSize` .
+     * @min 0
+     */
+    DesiredSize?: number | undefined;
+    /**
+     * The maximum number of nodes that the managed node group can scale out to. For information about the maximum number that you can specify, see [Amazon EKS service quotas](https://docs.aws.amazon.com/eks/latest/userguide/service-quotas.html) in the *Amazon EKS User Guide* .
+     * @min 1
+     */
+    MaxSize?: number | undefined;
+    /**
+     * The minimum number of nodes that the managed node group can scale in to.
+     * @min 0
+     */
+    MinSize?: number | undefined;
+};
+/**
+ * A property that allows a node to repel a `Pod` . For more information, see [Node taints on managed node groups](https://docs.aws.amazon.com/eks/latest/userguide/node-taints-managed-node-groups.html) in the *Amazon EKS User Guide* .
+ */
+export type Taint = {
+    /**
+     * The effect of the taint.
+     * @minLength 1
+     */
+    Effect?: string | undefined;
+    /**
+     * The key of the taint.
+     * @minLength 1
+     */
+    Key?: string | undefined;
+    /**
+     * The value of the taint.
+     * @minLength 0
+     */
+    Value?: string | undefined;
+};
+/**
+ * The update configuration for the node group.
+ */
+export type UpdateConfig = {
+    /**
+     * The maximum number of nodes unavailable at once during a version update. Nodes are updated in parallel. This value or `maxUnavailablePercentage` is required to have a value.The maximum number is 100.
+     * @min 1
+     */
+    MaxUnavailable?: number | undefined;
+    /**
+     * The maximum percentage of nodes unavailable during a version update. This percentage of nodes are updated in parallel, up to 100 nodes at once. This value or `maxUnavailable` is required to have a value.
+     * @min 1
+     * @max 100
+     */
+    MaxUnavailablePercentage?: number | undefined;
+    /**
+     * The configuration for the behavior to follow during a node group version update of this managed node group. You choose between two possible strategies for replacing nodes during an [`UpdateNodegroupVersion`](https://docs.aws.amazon.com/eks/latest/APIReference/API_UpdateNodegroupVersion.html) action.
+     *
+     * An Amazon EKS managed node group updates by replacing nodes with new nodes of newer AMI versions in parallel. The *update strategy* changes the managed node update behavior of the managed node group for each quantity. The *default* strategy has guardrails to protect you from misconfiguration and launches the new instances first, before terminating the old instances. The *minimal* strategy removes the guardrails and terminates the old instances before launching the new instances. This minimal strategy is useful in scenarios where you are constrained to resources or costs (for example, with hardware accelerators such as GPUs).
+     */
+    UpdateStrategy?: string | undefined;
+};
+//# sourceMappingURL=aws-eks-nodegroup.d.ts.map

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

@@ -0,0 +1,50 @@
+import type { ResourceDefinitionWithAttributes, Tag } from "../main.ts";
+export type EKSPodIdentityAssociation = ResourceDefinitionWithAttributes<"AWS::EKS::PodIdentityAssociation", EKSPodIdentityAssociationProps, EKSPodIdentityAssociationAttribs>;
+/**
+ * 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 EKSPodIdentityAssociationProps = {
+    /**
+     * The name of the cluster that the association is in.
+     * @minLength 1
+     */
+    ClusterName: string;
+    /**
+     * The name of the Kubernetes namespace inside the cluster to create the association in. The service account and the pods that use the service account must be in this namespace.
+     */
+    Namespace: string;
+    /**
+     * 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.
+     */
+    RoleArn: string;
+    /**
+     * The name of the Kubernetes service account inside the cluster to associate the IAM credentials with.
+     */
+    ServiceAccount: string;
+    /**
+     * 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.
+     *
+     * The following basic restrictions apply to tags:
+     *
+     * - Maximum number of tags per resource – 50
+     * - For each resource, each tag key must be unique, and each tag key can have only one value.
+     * - Maximum key length – 128 Unicode characters in UTF-8
+     * - Maximum value length – 256 Unicode characters in UTF-8
+     * - If your tagging schema is used across multiple services and resources, remember that other services may have restrictions on allowed characters. Generally allowed characters are: letters, numbers, and spaces representable in UTF-8, and the following characters: + - = . _ : / @.
+     * - Tag keys and values are case-sensitive.
+     * - Do not use `aws:` , `AWS:` , or any upper or lowercase combination of such as a prefix for either keys or values as it is reserved for AWS use. You cannot edit or delete tag keys or values with this prefix. Tags with this prefix do not count against your tags per resource limit.
+     */
+    Tags?: Tag[] | undefined;
+};
+export type EKSPodIdentityAssociationAttribs = {
+    /**
+     * The Amazon Resource Name (ARN) of the association.
+     */
+    AssociationArn: string;
+    /**
+     * The ID of the association.
+     * @minLength 1
+     */
+    AssociationId: string;
+};
+//# sourceMappingURL=aws-eks-podidentityassociation.d.ts.map