Update SDK models

Author: aws-sdk-rust-ci

Cargo.toml

@@ -1,8 +1,8 @@
 [workspace]
 resolver = "2"
 exclude = [
-    "tests/webassembly",
     "tests/telemetry",
+    "tests/webassembly",
     "tests/no-default-features"
 ]
 members = [

aws-models/ecs.json

@@ -15436,7 +15436,7 @@
                 }
             ],
             "traits": {
-                "smithy.api#documentation": "<p>Stops a running task. Any tags associated with the task will be deleted.</p>\n         <p>When you call <code>StopTask</code> on a task, the equivalent of <code>docker\n\t\t\t\tstop</code> is issued to the containers running in the task. This results in a\n\t\t\t\t<code>SIGTERM</code> value and a default 30-second timeout, after which the\n\t\t\t\t<code>SIGKILL</code> value is sent and the containers are forcibly stopped. If the\n\t\t\tcontainer handles the <code>SIGTERM</code> value gracefully and exits within 30 seconds\n\t\t\tfrom receiving it, no <code>SIGKILL</code> value is sent.</p>\n         <p>For Windows containers, POSIX signals do not work and runtime stops the container by\n\t\t\tsending a <code>CTRL_SHUTDOWN_EVENT</code>. For more information, see <a href=\"https://github.com/moby/moby/issues/25982\">Unable to react to graceful shutdown\n\t\t\t\tof (Windows) container #25982</a> on GitHub.</p>\n         <note>\n            <p>The default 30-second timeout can be configured on the Amazon ECS container agent\n\t\t\t\twith the <code>ECS_CONTAINER_STOP_TIMEOUT</code> variable. For more information, see\n\t\t\t\t\t<a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html\">Amazon ECS Container Agent Configuration</a> in the\n\t\t\t\t\t<i>Amazon Elastic Container Service Developer Guide</i>.</p>\n         </note>",
+                "smithy.api#documentation": "<p>Stops a running task. Any tags associated with the task will be deleted.</p>\n         <p>When you call <code>StopTask</code> on a task, the equivalent of <code>docker\n\t\t\t\tstop</code> is issued to the containers running in the task. This results in a\n\t\t\t\tstop signal value and a default 30-second timeout, after which the\n\t\t\t\t<code>SIGKILL</code> value is sent and the containers are forcibly stopped. This \n\t\t\t\tsignal can be defined in your container image with the <code>STOPSIGNAL</code> instruction\n\t\t\t\tand will default to <code>SIGTERM</code>. If the container handles the <code>SIGTERM</code>\n\t\t\t\tvalue gracefully and exits within 30 seconds from receiving it, no <code>SIGKILL</code> value\n\t\t\t\tis sent.</p>\n         <p>For Windows containers, POSIX signals do not work and runtime stops the container by\n\t\t\tsending a <code>CTRL_SHUTDOWN_EVENT</code>. For more information, see <a href=\"https://github.com/moby/moby/issues/25982\">Unable to react to graceful shutdown\n\t\t\t\tof (Windows) container #25982</a> on GitHub.</p>\n         <note>\n            <p>The default 30-second timeout can be configured on the Amazon ECS container agent\n\t\t\t\twith the <code>ECS_CONTAINER_STOP_TIMEOUT</code> variable. For more information, see\n\t\t\t\t\t<a href=\"https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-agent-config.html\">Amazon ECS Container Agent Configuration</a> in the\n\t\t\t\t\t<i>Amazon Elastic Container Service Developer Guide</i>.</p>\n         </note>",
                 "smithy.api#examples": [
                     {
                         "title": "To stop a task",

aws-models/iam.json

@@ -4616,7 +4616,13 @@
                 "State": {
                     "target": "com.amazonaws.iam#stateType",
                     "traits": {
-                        "smithy.api#documentation": "<p>The state of this delegation request.</p>\n         <p>See the <a href=\"IAM/latest/UserGuide/temporary-delegation-building-integration.html\">Understanding the Request Lifecycle</a> for an explanation of how these\n      states are transitioned.</p>"
+                        "smithy.api#documentation": "<p>The state of this delegation request.</p>\n         <p>See the <a href=\"IAM/latest/UserGuide/temporary-delegation-building-integration.html#temporary-delegation-request-lifecycle\">Understanding the Request Lifecycle</a> for an explanation of how these\n      states are transitioned.</p>"
+                    }
+                },
+                "ExpirationTime": {
+                    "target": "com.amazonaws.iam#dateType",
+                    "traits": {
+                        "smithy.api#documentation": "<p>The expiry time of this delegation request</p>\n         <p>See the <a href=\"IAM/latest/UserGuide/temporary-delegation-building-integration.html#temporary-delegation-request-lifecycle\">Understanding the Request Lifecycle</a> for\n               details on the life time of a delegation request at each state.</p>"
                     }
                 },
                 "RequestorId": {

aws-models/inspector2.json

@@ -15376,7 +15376,7 @@
                 "reason": {
                     "target": "com.amazonaws.inspector2#ScanStatusReason",
                     "traits": {
-                        "smithy.api#documentation": "<p>The scan status. Possible return values and descriptions are: </p>\n         <p>\n            <code>ACCESS_DENIED</code> - Resource access policy restricting Amazon Inspector access. Please\n         update the IAM policy.</p>\n         <p>\n            <code>ACCESS_DENIED_TO_ENCRYPTION_KEY</code> - The KMS key policy doesn't allow Amazon Inspector\n         access. Update the key policy.</p>\n         <p>\n            <code>DEEP_INSPECTION_COLLECTION_TIME_LIMIT_EXCEEDED</code> - Amazon Inspector failed to extract\n         the package inventory because the package collection time exceeding the maximum threshold\n         of 15 minutes.</p>\n         <p>\n            <code>DEEP_INSPECTION_DAILY_SSM_INVENTORY_LIMIT_EXCEEDED</code> - The SSM agent couldn't\n         send inventory to Amazon Inspector because the SSM quota for Inventory data collected per instance per\n         day has already been reached for this instance.</p>\n         <p>\n            <code>DEEP_INSPECTION_NO_INVENTORY</code> - The Amazon Inspector plugin hasn't yet been able to\n         collect an inventory of packages for this instance. This is usually the result of a pending\n         scan, however, if this status persists after 6 hours, use SSM to ensure that\n         the required Amazon Inspector associations exist and are running for the instance.</p>\n         <p>\n            <code>DEEP_INSPECTION_PACKAGE_COLLECTION_LIMIT_EXCEEDED</code> - The instance has\n         exceeded the 5000 package limit for Amazon Inspector Deep inspection. To resume Deep inspection for\n         this instance you can try to adjust the custom paths associated with the account.</p>\n         <p>\n            <code>EC2_INSTANCE_STOPPED</code> - This EC2 instance is in a stopped state, therefore,\n         Amazon Inspector will pause scanning. The existing findings will continue to exist until the instance\n         is terminated. Once the instance is re-started, Inspector will automatically start scanning\n         the instance again. Please note that you will not be charged for this instance while it's\n         in a stopped state.</p>\n         <p>\n            <code>EXCLUDED_BY_TAG</code> - This resource was not scanned because it has been\n         excluded by a tag.</p>\n         <p>\n            <code>IMAGE_SIZE_EXCEEDED</code> - Reserved for future use.</p>\n         <p>\n            <code>INTEGRATION_CONNNECTION_LOST</code> - Amazon Inspector couldn't communicate with the source\n         code management platform.</p>\n         <p>\n            <code>INTERNAL_ERROR</code> - Amazon Inspector has encountered an internal error for this resource.\n         Amazon Inspector service will automatically resolve the issue and resume the scanning. No action\n         required from the user.</p>\n         <p>\n            <code>NO_INVENTORY</code> - Amazon Inspector couldn't find software application inventory to scan\n         for vulnerabilities. This might be caused due to required Amazon Inspector associations being deleted\n         or failing to run on your resource. Please verify the status of\n         <code>InspectorInventoryCollection-do-not-delete</code> association in the SSM console\n         for the resource. Additionally, you can verify the instance's inventory in the SSM Fleet\n         Manager console.</p>\n         <p>\n            <code>NO_RESOURCES_FOUND</code> - Reserved for future use.</p>\n         <p>\n            <code>NO_SCAN_CONFIGURATION_ASSOCIATED</code> - The code repository resource doesn't\n         have an associated scan configuration.</p>\n         <p>\n            <code>PENDING_DISABLE</code> - This resource is pending cleanup during disablement. The\n         customer will not be billed while a resource is in the pending disable status.</p>\n         <p>\n            <code>PENDING_INITIAL_SCAN</code> - This resource has been identified for scanning,\n         results will be available soon.</p>\n         <p>\n            <code>RESOURCE_TERMINATED</code> - This resource has been terminated. The findings and\n         coverage associated with this resource are in the process of being cleaned up.</p>\n         <p>\n            <code>SCAN_ELIGIBILITY_EXPIRED</code> - The configured scan duration has lapsed for this\n         image.</p>\n         <p>\n            <code>SCAN_FREQUENCY_MANUAL</code> - This image will not be covered by Amazon Inspector due to the\n         repository scan frequency configuration.</p>\n         <p>\n            <code>SCAN_FREQUENCY_SCAN_ON_PUSH</code> - This image will be scanned one time and will\n         not new findings because of the scan frequency configuration.</p>\n         <p>\n            <code>SCAN_IN_PROGRESS</code> - The resource is currently being scanned.</p>\n         <p>\n            <code>STALE_INVENTORY</code> - Amazon Inspector wasn't able to collect an updated software\n         application inventory in the last 7 days. Please confirm the required Amazon Inspector associations\n         still exist and you can still see an updated inventory in the SSM console.</p>\n         <p>\n            <code>SUCCESSFUL</code> - The scan was successful.</p>\n         <p>\n            <code>UNMANAGED_EC2_INSTANCE</code> - The EC2 instance is not managed by SSM, please use\n         the following SSM automation to remediate the issue: <a href=\"https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-awssupport-troubleshoot-managed-instance.html\">https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-awssupport-troubleshoot-managed-instance.html</a>.\n         Once the instance becomes managed by SSM, Inspector will automatically begin scanning this\n         instance. </p>\n         <p>\n            <code>UNSUPPORTED_CONFIG_FILE</code> - Reserved for future use.</p>\n         <p>\n            <code>UNSUPPORTED_LANGUAGE</code> - The scan was unsuccessful because the repository\n         contains files in an unsupported programming language.</p>\n         <p>\n            <code>UNSUPPORTED_MEDIA_TYPE </code>- The ECR image has an unsupported media\n         type.</p>\n         <p>\n            <code>UNSUPPORTED_OS</code> - Amazon Inspector does not support this OS, architecture, or image\n         manifest type at this time. To see a complete list of supported operating systems see:\n         <a href=\" https://docs.aws.amazon.com/inspector/latest/user/supported.html\">https://docs.aws.amazon.com/inspector/latest/user/supported.html</a>.</p>\n         <p>\n            <code>UNSUPPORTED_RUNTIME</code> - The function was not scanned because it has an\n         unsupported runtime. To see a complete list of supported runtimes see: <a href=\" https://docs.aws.amazon.com/inspector/latest/user/supported.html\">https://docs.aws.amazon.com/inspector/latest/user/supported.html</a>.</p>\n         <p>\n            <code>IMAGE_ARCHIVED</code> - This image has been archived in Amazon ECR and is no longer available for scanning in Amazon Inspector.\n      </p>",
+                        "smithy.api#documentation": "<p>The scan status. Possible return values and descriptions are: </p>\n         <p>\n            <code>ACCESS_DENIED</code> - Resource access policy restricting Amazon Inspector access. Please\n         update the IAM policy.</p>\n         <p>\n            <code>ACCESS_DENIED_TO_ENCRYPTION_KEY</code> - The KMS key policy doesn't allow Amazon Inspector\n         access. Update the key policy.</p>\n         <p>\n            <code>DEEP_INSPECTION_COLLECTION_TIME_LIMIT_EXCEEDED</code> - Amazon Inspector failed to extract\n         the package inventory because the package collection time exceeding the maximum threshold\n         of 15 minutes.</p>\n         <p>\n            <code>DEEP_INSPECTION_DAILY_SSM_INVENTORY_LIMIT_EXCEEDED</code> - The SSM agent couldn't\n         send inventory to Amazon Inspector because the SSM quota for Inventory data collected per instance per\n         day has already been reached for this instance.</p>\n         <p>\n            <code>DEEP_INSPECTION_NO_INVENTORY</code> - The Amazon Inspector plugin hasn't yet been able to\n         collect an inventory of packages for this instance. This is usually the result of a pending\n         scan, however, if this status persists after 6 hours, use SSM to ensure that\n         the required Amazon Inspector associations exist and are running for the instance.</p>\n         <p>\n            <code>DEEP_INSPECTION_PACKAGE_COLLECTION_LIMIT_EXCEEDED</code> - The instance has\n         exceeded the 5000 package limit for Amazon Inspector Deep inspection. To resume Deep inspection for\n         this instance you can try to adjust the custom paths associated with the account.</p>\n         <p>\n            <code>EC2_INSTANCE_STOPPED</code> - This EC2 instance is in a stopped state, therefore,\n         Amazon Inspector will pause scanning. The existing findings will continue to exist until the instance\n         is terminated. Once the instance is re-started, Inspector will automatically start scanning\n         the instance again. Please note that you will not be charged for this instance while it's\n         in a stopped state.</p>\n         <p>\n            <code>EXCLUDED_BY_TAG</code> - This resource was not scanned because it has been\n         excluded by a tag.</p>\n         <p>\n            <code>IMAGE_SIZE_EXCEEDED</code> - Reserved for future use.</p>\n         <p>\n            <code>INTEGRATION_CONNNECTION_LOST</code> - Amazon Inspector couldn't communicate with the source\n         code management platform.</p>\n         <p>\n            <code>INTERNAL_ERROR</code> - Amazon Inspector has encountered an internal error for this resource.\n         Amazon Inspector service will automatically resolve the issue and resume the scanning. No action\n         required from the user.</p>\n         <p>\n            <code>NO_INVENTORY</code> - Amazon Inspector couldn't find software application inventory to scan\n         for vulnerabilities. This might be caused due to required Amazon Inspector associations being deleted\n         or failing to run on your resource. Please verify the status of\n         <code>InspectorInventoryCollection-do-not-delete</code> association in the SSM console\n         for the resource. Additionally, you can verify the instance's inventory in the SSM Fleet\n         Manager console.</p>\n         <p>\n            <code>NO_RESOURCES_FOUND</code> - Reserved for future use.</p>\n         <p>\n            <code>NO_SCAN_CONFIGURATION_ASSOCIATED</code> - The code repository resource doesn't\n         have an associated scan configuration.</p>\n         <p>\n            <code>PENDING_DISABLE</code> - This resource is pending cleanup during disablement. The\n         customer will not be billed while a resource is in the pending disable status.</p>\n         <p>\n            <code>PENDING_INITIAL_SCAN</code> - This resource has been identified for scanning,\n         results will be available soon.</p>\n         <p>\n            <code>RESOURCE_TERMINATED</code> - This resource has been terminated. The findings and\n         coverage associated with this resource are in the process of being cleaned up.</p>\n         <p>\n            <code>SCAN_ELIGIBILITY_EXPIRED</code> - The configured scan duration has lapsed for this\n         image.</p>\n         <p>\n            <code>SCAN_FREQUENCY_MANUAL</code> - This image will not be covered by Amazon Inspector due to the\n         repository scan frequency configuration.</p>\n         <p>\n            <code>SCAN_FREQUENCY_SCAN_ON_PUSH</code> - This image will be scanned one time and will\n         not new findings because of the scan frequency configuration.</p>\n         <p>\n            <code>SCAN_IN_PROGRESS</code> - The resource is currently being scanned.</p>\n         <p>\n            <code>STALE_INVENTORY</code> - Amazon Inspector wasn't able to collect an updated software\n         application inventory in the last 7 days. Please confirm the required Amazon Inspector associations\n         still exist and you can still see an updated inventory in the SSM console.</p>\n         <p>\n            <code>SUCCESSFUL</code> - The scan was successful.</p>\n         <p>\n            <code>UNMANAGED_EC2_INSTANCE</code> - The EC2 instance is not managed by SSM, please use\n         the following SSM automation to remediate the issue: <a href=\"https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-awssupport-troubleshoot-managed-instance.html\">https://docs.aws.amazon.com/systems-manager-automation-runbooks/latest/userguide/automation-awssupport-troubleshoot-managed-instance.html</a>.\n         Once the instance becomes managed by SSM, Inspector will automatically begin scanning this\n         instance. </p>\n         <p>\n            <code>UNSUPPORTED_CODE_ARTIFACTS </code> - The function was not scanned because it has an unsupported code artifacts.</p>\n         <p>\n            <code>UNSUPPORTED_CONFIG_FILE</code> - Reserved for future use.</p>\n         <p>\n            <code>UNSUPPORTED_LANGUAGE</code> - The scan was unsuccessful because the repository\n         contains files in an unsupported programming language.</p>\n         <p>\n            <code>UNSUPPORTED_MEDIA_TYPE </code>- The ECR image has an unsupported media\n         type.</p>\n         <p>\n            <code>UNSUPPORTED_OS</code> - Amazon Inspector does not support this OS, architecture, or image\n         manifest type at this time. To see a complete list of supported operating systems see:\n         <a href=\" https://docs.aws.amazon.com/inspector/latest/user/supported.html\">https://docs.aws.amazon.com/inspector/latest/user/supported.html</a>.</p>\n         <p>\n            <code>UNSUPPORTED_RUNTIME</code> - The function was not scanned because it has an\n         unsupported runtime. To see a complete list of supported runtimes see: <a href=\" https://docs.aws.amazon.com/inspector/latest/user/supported.html\">https://docs.aws.amazon.com/inspector/latest/user/supported.html</a>.</p>\n         <p>\n            <code>IMAGE_ARCHIVED</code> - This image has been archived in Amazon ECR and is no longer available for scanning in Amazon Inspector.\n      </p>",
                         "smithy.api#required": {}
                     }
                 }
@@ -15535,6 +15535,10 @@
                     {
                         "value": "IMAGE_ARCHIVED",
                         "name": "IMAGE_ARCHIVED"
+                    },
+                    {
+                        "value": "UNSUPPORTED_CODE_ARTIFACTS",
+                        "name": "UNSUPPORTED_CODE_ARTIFACTS"
                     }
                 ]
             }