Update SDK models (a4949004) · Commits · Public Repositories / aws-sdk-rs

Cargo.toml

+2 −2

Original line number	Diff line number	Diff line
		[workspace]
		resolver = "2"
		exclude = [
		"tests/webassembly",
		"tests/telemetry",
		"tests/no-default-features",
		"tests/webassembly"
		"tests/no-default-features"
		]
		members = [
		"sdk/accessanalyzer",

aws-models/connect.json

+631 −2

File changed.

Preview size limit exceeded, changes collapsed.

aws-models/cost-explorer.json

+1 −1

Original line number	Diff line number	Diff line
		@@ -7429,7 +7429,7 @@
		"SupportedResourceTypes": {
		"target": "com.amazonaws.costexplorer#ResourceTypesFilterInput",
		"traits": {
		"smithy.api#documentation": "<p>\n Filter cost category definitions that are supported by given resource types based on the latest version. If the filter is present, the result only includes Cost Categories that supports input resource type. If the filter isn't provided, no filtering is applied. The valid values are <code>billing:rispgroupsharing</code>.\n </p>"
		"smithy.api#documentation": "<p>\n Filter cost category definitions that are supported by given resource types based on the latest version. If the filter is present, the result only includes Cost Categories that supports input resource type. If the filter isn't provided, no filtering is applied. The valid values are <code>billing:rispgroupsharing</code> and <code>billing:billingview</code>.\n </p>"
		}
		}
		},

aws-models/eks.json

+17 −5

Original line number	Diff line number	Diff line
		@@ -92,6 +92,18 @@
		"smithy.api#enumValue": "BOTTLEROCKET_x86_64_NVIDIA"
		}
		},
		"BOTTLEROCKET_ARM_64_NVIDIA_FIPS": {
		"target": "smithy.api#Unit",
		"traits": {
		"smithy.api#enumValue": "BOTTLEROCKET_ARM_64_NVIDIA_FIPS"
		}
		},
		"BOTTLEROCKET_x86_64_NVIDIA_FIPS": {
		"target": "smithy.api#Unit",
		"traits": {
		"smithy.api#enumValue": "BOTTLEROCKET_x86_64_NVIDIA_FIPS"
		}
		},
		"WINDOWS_CORE_2019_x86_64": {
		"target": "smithy.api#Unit",
		"traits": {
		@@ -2533,12 +2545,12 @@
		"name": {
		"target": "com.amazonaws.eks#String",
		"traits": {
		"smithy.api#documentation": "<p>The name of the Amazon EC2 Auto Scaling group associated with an Amazon EKS managed node group.</p>"
		"smithy.api#documentation": "<p>The name of the Auto Scaling group associated with an Amazon EKS managed node group.</p>"
		}
		}
		},
		"traits": {
		"smithy.api#documentation": "<p>An Amazon EC2 Auto Scaling group that is associated with an Amazon EKS managed node group.</p>"
		"smithy.api#documentation": "<p>An Auto Scaling group that is associated with an Amazon EKS managed node group.</p>"
		}
		},
		"com.amazonaws.eks#AutoScalingGroupList": {
		@@ -4570,7 +4582,7 @@
		}
		],
		"traits": {
		"smithy.api#documentation": "<p>Creates a managed node group for an Amazon EKS cluster.</p>\n <p>You can only create a node group for your cluster that is equal to the current Kubernetes\n version for the cluster. All node groups are created with the latest AMI release version\n for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI\n using a launch template.</p>\n <p>For later updates, you will only be able to update a node group using a launch\n template only if it was originally deployed with a launch template. Additionally, the\n launch template ID or name must match what was used when the node group was created. You\n can update the launch template version with necessary changes. For more information\n about using launch templates, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Customizing managed nodes with\n launch templates</a>.</p>\n <p>An Amazon EKS managed node group is an Amazon EC2 Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that\n are managed by Amazon Web Services for an Amazon EKS cluster. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html\">Managed\n node groups</a> in the <i>Amazon EKS User Guide</i>.</p>\n <note>\n <p>Windows AMI types are only supported for commercial Amazon Web Services Regions that support\n Windows on Amazon EKS.</p>\n </note>",
		"smithy.api#documentation": "<p>Creates a managed node group for an Amazon EKS cluster.</p>\n <p>You can only create a node group for your cluster that is equal to the current Kubernetes\n version for the cluster. All node groups are created with the latest AMI release version\n for the respective minor Kubernetes version of the cluster, unless you deploy a custom AMI\n using a launch template.</p>\n <p>For later updates, you will only be able to update a node group using a launch\n template only if it was originally deployed with a launch template. Additionally, the\n launch template ID or name must match what was used when the node group was created. You\n can update the launch template version with necessary changes. For more information\n about using launch templates, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html\">Customizing managed nodes with\n launch templates</a>.</p>\n <p>An Amazon EKS managed node group is an Amazon EC2 Auto Scaling group and associated Amazon EC2 instances that\n are managed by Amazon Web Services for an Amazon EKS cluster. For more information, see <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html\">Managed\n node groups</a> in the <i>Amazon EKS User Guide</i>.</p>\n <note>\n <p>Windows AMI types are only supported for commercial Amazon Web Services Regions that support\n Windows on Amazon EKS.</p>\n </note>",
		"smithy.api#http": {
		"method": "POST",
		"uri": "/clusters/{clusterName}/node-groups",
		@@ -8189,7 +8201,7 @@
		"code": {
		"target": "com.amazonaws.eks#NodegroupIssueCode",
		"traits": {
		"smithy.api#documentation": "<p>A brief description of the error.</p>\n <ul>\n <li>\n <p>\n <b>AccessDenied</b>: Amazon EKS or one or more of your\n managed nodes is failing to authenticate or authorize with your Kubernetes cluster\n API server.</p>\n </li>\n <li>\n <p>\n <b>AsgInstanceLaunchFailures</b>: Your Amazon EC2 Auto Scaling group is\n experiencing failures while attempting to launch instances.</p>\n </li>\n <li>\n <p>\n <b>AutoScalingGroupNotFound</b>: We couldn't find\n the Amazon EC2 Auto Scaling group associated with the managed node group. You may be able to\n recreate an Amazon EC2 Auto Scaling group with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>ClusterUnreachable</b>: Amazon EKS or one or more of\n your managed nodes is unable to to communicate with your Kubernetes cluster API\n server. This can happen if there are network disruptions or if API servers are\n timing out processing requests. </p>\n </li>\n <li>\n <p>\n <b>Ec2InstanceTypeDoesNotExist</b>: One or more of\n the supplied Amazon EC2 instance types do not exist. Amazon EKS checked for the\n instance types that you provided in this Amazon Web Services Region, and one or more aren't\n available.</p>\n </li>\n <li>\n <p>\n <b>Ec2LaunchTemplateNotFound</b>: We couldn't find\n the Amazon EC2 launch template for your managed node group. You may be able to\n recreate a launch template with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>Ec2LaunchTemplateVersionMismatch</b>: The Amazon EC2\n launch template version for your managed node group does not match the version\n that Amazon EKS created. You may be able to revert to the version that Amazon EKS created\n to recover.</p>\n </li>\n <li>\n <p>\n <b>Ec2SecurityGroupDeletionFailure</b>: We could not\n delete the remote access security group for your managed node group. Remove any\n dependencies from the security group.</p>\n </li>\n <li>\n <p>\n <b>Ec2SecurityGroupNotFound</b>: We couldn't find\n the cluster security group for the cluster. You must recreate your\n cluster.</p>\n </li>\n <li>\n <p>\n <b>Ec2SubnetInvalidConfiguration</b>: One or more\n Amazon EC2 subnets specified for a node group do not automatically assign public IP\n addresses to instances launched into it. If you want your instances to be\n assigned a public IP address, then you need to enable the <code>auto-assign\n public IP address</code> setting for the subnet. See <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html#subnet-public-ip\">Modifying\n the public <code>IPv4</code> addressing attribute for your subnet</a> in\n the <i>Amazon VPC User Guide</i>.</p>\n </li>\n <li>\n <p>\n <b>IamInstanceProfileNotFound</b>: We couldn't find\n the IAM instance profile for your managed node group. You may be able to\n recreate an instance profile with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>IamNodeRoleNotFound</b>: We couldn't find the\n IAM role for your managed node group. You may be able to recreate an IAM\n role with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>InstanceLimitExceeded</b>: Your Amazon Web Services account is\n unable to launch any more instances of the specified instance type. You may be\n able to request an Amazon EC2 instance limit increase to recover.</p>\n </li>\n <li>\n <p>\n <b>InsufficientFreeAddresses</b>: One or more of the\n subnets associated with your managed node group does not have enough available\n IP addresses for new nodes.</p>\n </li>\n <li>\n <p>\n <b>InternalFailure</b>: These errors are usually\n caused by an Amazon EKS server-side issue.</p>\n </li>\n <li>\n <p>\n <b>NodeCreationFailure</b>: Your launched instances\n are unable to register with your Amazon EKS cluster. Common causes of this failure\n are insufficient <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html\">node IAM role</a>\n permissions or lack of outbound internet access for the nodes. </p>\n </li>\n </ul>"
		"smithy.api#documentation": "<p>A brief description of the error.</p>\n <ul>\n <li>\n <p>\n <b>AccessDenied</b>: Amazon EKS or one or more of your\n managed nodes is failing to authenticate or authorize with your Kubernetes cluster\n API server.</p>\n </li>\n <li>\n <p>\n <b>AsgInstanceLaunchFailures</b>: Your Auto Scaling group is\n experiencing failures while attempting to launch instances.</p>\n </li>\n <li>\n <p>\n <b>AutoScalingGroupNotFound</b>: We couldn't find\n the Auto Scaling group associated with the managed node group. You may be able to\n recreate an Auto Scaling group with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>ClusterUnreachable</b>: Amazon EKS or one or more of\n your managed nodes is unable to to communicate with your Kubernetes cluster API\n server. This can happen if there are network disruptions or if API servers are\n timing out processing requests. </p>\n </li>\n <li>\n <p>\n <b>Ec2InstanceTypeDoesNotExist</b>: One or more of\n the supplied Amazon EC2 instance types do not exist. Amazon EKS checked for the\n instance types that you provided in this Amazon Web Services Region, and one or more aren't\n available.</p>\n </li>\n <li>\n <p>\n <b>Ec2LaunchTemplateNotFound</b>: We couldn't find\n the Amazon EC2 launch template for your managed node group. You may be able to\n recreate a launch template with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>Ec2LaunchTemplateVersionMismatch</b>: The Amazon EC2\n launch template version for your managed node group does not match the version\n that Amazon EKS created. You may be able to revert to the version that Amazon EKS created\n to recover.</p>\n </li>\n <li>\n <p>\n <b>Ec2SecurityGroupDeletionFailure</b>: We could not\n delete the remote access security group for your managed node group. Remove any\n dependencies from the security group.</p>\n </li>\n <li>\n <p>\n <b>Ec2SecurityGroupNotFound</b>: We couldn't find\n the cluster security group for the cluster. You must recreate your\n cluster.</p>\n </li>\n <li>\n <p>\n <b>Ec2SubnetInvalidConfiguration</b>: One or more\n Amazon EC2 subnets specified for a node group do not automatically assign public IP\n addresses to instances launched into it. If you want your instances to be\n assigned a public IP address, then you need to enable the <code>auto-assign\n public IP address</code> setting for the subnet. See <a href=\"https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html#subnet-public-ip\">Modifying\n the public <code>IPv4</code> addressing attribute for your subnet</a> in\n the <i>Amazon VPC User Guide</i>.</p>\n </li>\n <li>\n <p>\n <b>IamInstanceProfileNotFound</b>: We couldn't find\n the IAM instance profile for your managed node group. You may be able to\n recreate an instance profile with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>IamNodeRoleNotFound</b>: We couldn't find the\n IAM role for your managed node group. You may be able to recreate an IAM\n role with the same settings to recover.</p>\n </li>\n <li>\n <p>\n <b>InstanceLimitExceeded</b>: Your Amazon Web Services account is\n unable to launch any more instances of the specified instance type. You may be\n able to request an Amazon EC2 instance limit increase to recover.</p>\n </li>\n <li>\n <p>\n <b>InsufficientFreeAddresses</b>: One or more of the\n subnets associated with your managed node group does not have enough available\n IP addresses for new nodes.</p>\n </li>\n <li>\n <p>\n <b>InternalFailure</b>: These errors are usually\n caused by an Amazon EKS server-side issue.</p>\n </li>\n <li>\n <p>\n <b>NodeCreationFailure</b>: Your launched instances\n are unable to register with your Amazon EKS cluster. Common causes of this failure\n are insufficient <a href=\"https://docs.aws.amazon.com/eks/latest/userguide/create-node-role.html\">node IAM role</a>\n permissions or lack of outbound internet access for the nodes. </p>\n </li>\n </ul>"
		}
		},
		"message": {
		@@ -10305,7 +10317,7 @@
		}
		},
		"traits": {
		"smithy.api#documentation": "<p>An object representing the scaling configuration details for the Amazon EC2 Auto Scaling group that is\n associated with your node group. When creating a node group, you must specify all or\n none of the properties. When updating a node group, you can specify any or none of the\n properties.</p>"
		"smithy.api#documentation": "<p>An object representing the scaling configuration details for the Auto Scaling group that is\n associated with your node group. When creating a node group, you must specify all or\n none of the properties. When updating a node group, you can specify any or none of the\n properties.</p>"
		}
		},
		"com.amazonaws.eks#NodegroupStatus": {

aws-models/rds.json

+2282 −1663

File changed.

Preview size limit exceeded, changes collapsed.