diff --git a/codegen/sdk-codegen/aws-models/appflow.json b/codegen/sdk-codegen/aws-models/appflow.json index b7289d08e05..b905e855324 100644 --- a/codegen/sdk-codegen/aws-models/appflow.json +++ b/codegen/sdk-codegen/aws-models/appflow.json @@ -7886,7 +7886,7 @@ "oAuth2GrantType": { "target": "com.amazonaws.appflow#OAuth2GrantType", "traits": { - "smithy.api#documentation": "
Specifies the OAuth 2.0 grant type that Amazon AppFlow uses when it requests an\n access token from Salesforce. Amazon AppFlow requires an access token each time it\n attempts to access your Salesforce records.
\nYou can specify one of the following values:
\nAmazon AppFlow passes an authorization code when it requests the access token\n from Salesforce. Amazon AppFlow receives the authorization code from Salesforce\n after you log in to your Salesforce account and authorize Amazon AppFlow to access\n your records.
\nAmazon AppFlow passes client credentials (a client ID and client secret) when\n it requests the access token from Salesforce. You provide these credentials to Amazon AppFlow when you define the connection to your Salesforce account.
\nAmazon AppFlow passes a JSON web token (JWT) when it requests the access token\n from Salesforce. You provide the JWT to Amazon AppFlow when you define the\n connection to your Salesforce account. When you use this grant type, you don't need to\n log in to your Salesforce account to authorize Amazon AppFlow to access your\n records.
\nSpecifies the OAuth 2.0 grant type that Amazon AppFlow uses when it requests an\n access token from Salesforce. Amazon AppFlow requires an access token each time it\n attempts to access your Salesforce records.
\nYou can specify one of the following values:
\nAmazon AppFlow passes an authorization code when it requests the access token\n from Salesforce. Amazon AppFlow receives the authorization code from Salesforce\n after you log in to your Salesforce account and authorize Amazon AppFlow to access\n your records.
\nAmazon AppFlow passes a JSON web token (JWT) when it requests the access token\n from Salesforce. You provide the JWT to Amazon AppFlow when you define the\n connection to your Salesforce account. When you use this grant type, you don't need to\n log in to your Salesforce account to authorize Amazon AppFlow to access your\n records.
\nThe CLIENT_CREDENTIALS value is not supported for Salesforce.
\nThe OAuth 2.0 grant types that Amazon AppFlow can use when it requests an access\n token from Salesforce. Amazon AppFlow requires an access token each time it attempts to\n access your Salesforce records.
\nAmazon AppFlow passes an authorization code when it requests the access token\n from Salesforce. Amazon AppFlow receives the authorization code from Salesforce\n after you log in to your Salesforce account and authorize Amazon AppFlow to access\n your records.
\nAmazon AppFlow passes client credentials (a client ID and client secret) when\n it requests the access token from Salesforce. You provide these credentials to Amazon AppFlow when you define the connection to your Salesforce account.
\nAmazon AppFlow passes a JSON web token (JWT) when it requests the access token\n from Salesforce. You provide the JWT to Amazon AppFlow when you define the\n connection to your Salesforce account. When you use this grant type, you don't need to\n log in to your Salesforce account to authorize Amazon AppFlow to access your\n records.
\nThe OAuth 2.0 grant types that Amazon AppFlow can use when it requests an access\n token from Salesforce. Amazon AppFlow requires an access token each time it attempts to\n access your Salesforce records.
\nAmazon AppFlow passes an authorization code when it requests the access token\n from Salesforce. Amazon AppFlow receives the authorization code from Salesforce\n after you log in to your Salesforce account and authorize Amazon AppFlow to access\n your records.
\nAmazon AppFlow passes a JSON web token (JWT) when it requests the access token\n from Salesforce. You provide the JWT to Amazon AppFlow when you define the\n connection to your Salesforce account. When you use this grant type, you don't need to\n log in to your Salesforce account to authorize Amazon AppFlow to access your\n records.
\nThe CLIENT_CREDENTIALS value is not supported for Salesforce.
\nThe state of the override.
" + } + }, + "Reason": { + "target": "com.amazonaws.elasticloadbalancingv2#TargetAdministrativeOverrideReasonEnum", + "traits": { + "smithy.api#documentation": "The reason code for the state.
" + } + }, + "Description": { + "target": "com.amazonaws.elasticloadbalancingv2#Description", + "traits": { + "smithy.api#documentation": "A description of the override state that provides additional details.
" + } + } + }, + "traits": { + "smithy.api#documentation": "Information about the override status applied to a target.
" + } + }, "com.amazonaws.elasticloadbalancingv2#AllocationId": { "type": "string" }, @@ -5884,7 +5910,7 @@ "Key": { "target": "com.amazonaws.elasticloadbalancingv2#LoadBalancerAttributeKey", "traits": { - "smithy.api#documentation": "The name of the attribute.
\nThe following attributes are supported by all load balancers:
\n\n deletion_protection.enabled
- Indicates whether deletion protection is\n enabled. The value is true
or false
. The default is\n false
.
\n load_balancing.cross_zone.enabled
- Indicates whether cross-zone load\n balancing is enabled. The possible values are true
and false
.\n The default for Network Load Balancers and Gateway Load Balancers is false
. \n The default for Application Load Balancers is true
, and cannot be changed.
The following attributes are supported by both Application Load Balancers and Network Load\n Balancers:
\n\n access_logs.s3.enabled
- Indicates whether access logs are enabled. The\n value is true
or false
. The default is\n false
.
\n access_logs.s3.bucket
- The name of the S3 bucket for the access logs.\n This attribute is required if access logs are enabled. The bucket must exist in the same\n region as the load balancer and have a bucket policy that grants Elastic Load Balancing\n permissions to write to the bucket.
\n access_logs.s3.prefix
- The prefix for the location in the S3 bucket for the\n access logs.
\n ipv6.deny_all_igw_traffic
- Blocks internet gateway (IGW) access to the\n load balancer. It is set to false
for internet-facing load balancers and\n true
for internal load balancers, preventing unintended access to your\n internal load balancer through an internet gateway.
The following attributes are supported by only Application Load Balancers:
\n\n idle_timeout.timeout_seconds
- The idle timeout value, in seconds. The\n valid range is 1-4000 seconds. The default is 60 seconds.
\n client_keep_alive.seconds
- The client keep alive value, in seconds. The \n valid range is 60-604800 seconds. The default is 3600 seconds.
\n connection_logs.s3.enabled
- Indicates whether connection logs are enabled. The\n value is true
or false
. The default is false
.
\n connection_logs.s3.bucket
- The name of the S3 bucket for the connection logs.\n This attribute is required if connection logs are enabled. The bucket must exist in the same\n region as the load balancer and have a bucket policy that grants Elastic Load Balancing\n permissions to write to the bucket.
\n connection_logs.s3.prefix
- The prefix for the location in the S3 bucket for the\n connection logs.
\n routing.http.desync_mitigation_mode
- Determines how the load balancer\n handles requests that might pose a security risk to your application. The possible values\n are monitor
, defensive
, and strictest
. The default\n is defensive
.
\n routing.http.drop_invalid_header_fields.enabled
- Indicates whether HTTP\n headers with invalid header fields are removed by the load balancer (true
) or\n routed to targets (false
). The default is false
.
\n routing.http.preserve_host_header.enabled
- Indicates whether the\n Application Load Balancer should preserve the Host
header in the HTTP request\n and send it to the target without any change. The possible values are true
\n and false
. The default is false
.
\n routing.http.x_amzn_tls_version_and_cipher_suite.enabled
- Indicates\n whether the two headers (x-amzn-tls-version
and\n x-amzn-tls-cipher-suite
), which contain information about the negotiated\n TLS version and cipher suite, are added to the client request before sending it to the\n target. The x-amzn-tls-version
header has information about the TLS protocol\n version negotiated with the client, and the x-amzn-tls-cipher-suite
header\n has information about the cipher suite negotiated with the client. Both headers are in\n OpenSSL format. The possible values for the attribute are true
and\n false
. The default is false
.
\n routing.http.xff_client_port.enabled
- Indicates whether the\n X-Forwarded-For
header should preserve the source port that the client used\n to connect to the load balancer. The possible values are true
and\n false
. The default is false
.
\n routing.http.xff_header_processing.mode
- Enables you to modify,\n preserve, or remove the X-Forwarded-For
header in the HTTP request before the\n Application Load Balancer sends the request to the target. The possible values are\n append
, preserve
, and remove
. The default is\n append
.
If the value is append
, the Application Load Balancer adds the client\n IP address (of the last hop) to the X-Forwarded-For
header in the HTTP\n request before it sends it to targets.
If the value is preserve
the Application Load Balancer preserves the\n X-Forwarded-For
header in the HTTP request, and sends it to targets\n without any change.
If the value is remove
, the Application Load Balancer removes the\n X-Forwarded-For
header in the HTTP request before it sends it to\n targets.
\n routing.http2.enabled
- Indicates whether HTTP/2 is enabled. The possible\n values are true
and false
. The default is true
.\n Elastic Load Balancing requires that message header names contain only alphanumeric\n characters and hyphens.
\n waf.fail_open.enabled
- Indicates whether to allow a WAF-enabled load\n balancer to route requests to targets if it is unable to forward the request to Amazon Web Services WAF. The possible values are true
and false
. The\n default is false
.
The following attributes are supported by only Network Load Balancers:
\n\n dns_record.client_routing_policy
- Indicates how traffic is \n distributed among the load balancer Availability Zones. The possible values are \n availability_zone_affinity
with 100 percent zonal affinity, \n partial_availability_zone_affinity
with 85 percent zonal affinity, \n and any_availability_zone
with 0 percent zonal affinity.
The name of the attribute.
\nThe following attributes are supported by all load balancers:
\n\n deletion_protection.enabled
- Indicates whether deletion protection is\n enabled. The value is true
or false
. The default is\n false
.
\n load_balancing.cross_zone.enabled
- Indicates whether cross-zone load\n balancing is enabled. The possible values are true
and false
.\n The default for Network Load Balancers and Gateway Load Balancers is false
. \n The default for Application Load Balancers is true
, and cannot be changed.
The following attributes are supported by both Application Load Balancers and Network Load\n Balancers:
\n\n access_logs.s3.enabled
- Indicates whether access logs are enabled. The\n value is true
or false
. The default is\n false
.
\n access_logs.s3.bucket
- The name of the S3 bucket for the access logs.\n This attribute is required if access logs are enabled. The bucket must exist in the same\n region as the load balancer and have a bucket policy that grants Elastic Load Balancing\n permissions to write to the bucket.
\n access_logs.s3.prefix
- The prefix for the location in the S3 bucket for the\n access logs.
\n ipv6.deny_all_igw_traffic
- Blocks internet gateway (IGW) access to the\n load balancer. It is set to false
for internet-facing load balancers and\n true
for internal load balancers, preventing unintended access to your\n internal load balancer through an internet gateway.
The following attributes are supported by only Application Load Balancers:
\n\n idle_timeout.timeout_seconds
- The idle timeout value, in seconds. The\n valid range is 1-4000 seconds. The default is 60 seconds.
\n client_keep_alive.seconds
- The client keep alive value, in seconds. The \n valid range is 60-604800 seconds. The default is 3600 seconds.
\n connection_logs.s3.enabled
- Indicates whether connection logs are enabled. The\n value is true
or false
. The default is false
.
\n connection_logs.s3.bucket
- The name of the S3 bucket for the connection logs.\n This attribute is required if connection logs are enabled. The bucket must exist in the same\n region as the load balancer and have a bucket policy that grants Elastic Load Balancing\n permissions to write to the bucket.
\n connection_logs.s3.prefix
- The prefix for the location in the S3 bucket for the\n connection logs.
\n routing.http.desync_mitigation_mode
- Determines how the load balancer\n handles requests that might pose a security risk to your application. The possible values\n are monitor
, defensive
, and strictest
. The default\n is defensive
.
\n routing.http.drop_invalid_header_fields.enabled
- Indicates whether HTTP\n headers with invalid header fields are removed by the load balancer (true
) or\n routed to targets (false
). The default is false
.
\n routing.http.preserve_host_header.enabled
- Indicates whether the\n Application Load Balancer should preserve the Host
header in the HTTP request\n and send it to the target without any change. The possible values are true
\n and false
. The default is false
.
\n routing.http.x_amzn_tls_version_and_cipher_suite.enabled
- Indicates\n whether the two headers (x-amzn-tls-version
and\n x-amzn-tls-cipher-suite
), which contain information about the negotiated\n TLS version and cipher suite, are added to the client request before sending it to the\n target. The x-amzn-tls-version
header has information about the TLS protocol\n version negotiated with the client, and the x-amzn-tls-cipher-suite
header\n has information about the cipher suite negotiated with the client. Both headers are in\n OpenSSL format. The possible values for the attribute are true
and\n false
. The default is false
.
\n routing.http.xff_client_port.enabled
- Indicates whether the\n X-Forwarded-For
header should preserve the source port that the client used\n to connect to the load balancer. The possible values are true
and\n false
. The default is false
.
\n routing.http.xff_header_processing.mode
- Enables you to modify,\n preserve, or remove the X-Forwarded-For
header in the HTTP request before the\n Application Load Balancer sends the request to the target. The possible values are\n append
, preserve
, and remove
. The default is\n append
.
If the value is append
, the Application Load Balancer adds the client\n IP address (of the last hop) to the X-Forwarded-For
header in the HTTP\n request before it sends it to targets.
If the value is preserve
the Application Load Balancer preserves the\n X-Forwarded-For
header in the HTTP request, and sends it to targets\n without any change.
If the value is remove
, the Application Load Balancer removes the\n X-Forwarded-For
header in the HTTP request before it sends it to\n targets.
\n routing.http2.enabled
- Indicates whether HTTP/2 is enabled. The possible\n values are true
and false
. The default is true
.\n Elastic Load Balancing requires that message header names contain only alphanumeric\n characters and hyphens.
\n waf.fail_open.enabled
- Indicates whether to allow a WAF-enabled load\n balancer to route requests to targets if it is unable to forward the request to Amazon Web Services WAF. The possible values are true
and false
. The\n default is false
.
The following attributes are supported by only Network Load Balancers:
\n\n dns_record.client_routing_policy
- Indicates how traffic is \n distributed among the load balancer Availability Zones. The possible values are \n availability_zone_affinity
with 100 percent zonal affinity, \n partial_availability_zone_affinity
with 85 percent zonal affinity, \n and any_availability_zone
with 0 percent zonal affinity.
\n zonal_shift.config.enabled
- Indicates whether zonal shift is \n enabled. The possible values are true
and false
. The \n default is false
.
The anomaly detection result for the target.
\nIf no anomalies were detected, the result is normal
.
If anomalies were detected, the result is anomalous
.
The administrative override information for the target.
" + } } }, "traits": { diff --git a/codegen/sdk-codegen/aws-models/emr.json b/codegen/sdk-codegen/aws-models/emr.json index 670c426e41f..1dd27524426 100644 --- a/codegen/sdk-codegen/aws-models/emr.json +++ b/codegen/sdk-codegen/aws-models/emr.json @@ -4568,6 +4568,12 @@ "traits": { "smithy.api#documentation": "The resize specification for the instance fleet.
" } + }, + "Context": { + "target": "com.amazonaws.emr#XmlStringMaxLen256", + "traits": { + "smithy.api#documentation": "Reserved.
" + } } }, "traits": { @@ -4620,6 +4626,12 @@ "traits": { "smithy.api#documentation": "The resize specification for the instance fleet.
" } + }, + "Context": { + "target": "com.amazonaws.emr#XmlStringMaxLen256", + "traits": { + "smithy.api#documentation": "Reserved.
" + } } }, "traits": { @@ -4675,6 +4687,12 @@ "traits": { "smithy.api#documentation": "An array of InstanceTypeConfig objects that specify how Amazon EMR provisions Amazon EC2 instances\n when it fulfills On-Demand and Spot capacities. For more information, see InstanceTypeConfig.
" } + }, + "Context": { + "target": "com.amazonaws.emr#XmlStringMaxLen256", + "traits": { + "smithy.api#documentation": "Reserved.
" + } } }, "traits": { diff --git a/codegen/sdk-codegen/aws-models/guardduty.json b/codegen/sdk-codegen/aws-models/guardduty.json index 3e052ca8466..e81b116ea54 100644 --- a/codegen/sdk-codegen/aws-models/guardduty.json +++ b/codegen/sdk-codegen/aws-models/guardduty.json @@ -11049,6 +11049,13 @@ "smithy.api#jsonName": "localIpDetails" } }, + "LocalNetworkInterface": { + "target": "com.amazonaws.guardduty#String", + "traits": { + "smithy.api#documentation": "The EC2 instance's local elastic network interface utilized for the connection.
", + "smithy.api#jsonName": "localNetworkInterface" + } + }, "RemoteIpDetails": { "target": "com.amazonaws.guardduty#RemoteIpDetails", "traits": { diff --git a/codegen/sdk-codegen/aws-models/robomaker.json b/codegen/sdk-codegen/aws-models/robomaker.json index dcdd2970fab..bce47bd0a1c 100644 --- a/codegen/sdk-codegen/aws-models/robomaker.json +++ b/codegen/sdk-codegen/aws-models/robomaker.json @@ -94,7 +94,7 @@ } ], "traits": { - "smithy.api#documentation": "Deletes one or more worlds in a batch operation.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDeletes one or more worlds in a batch operation.
", "smithy.api#http": { "method": "POST", "uri": "/batchDeleteWorlds", @@ -154,7 +154,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes one or more simulation jobs.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes one or more simulation jobs.
", "smithy.api#http": { "method": "POST", "uri": "/batchDescribeSimulationJob", @@ -255,7 +255,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Cancels the specified deployment job.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nCancels the specified deployment job.
", "smithy.api#http": { "method": "POST", "uri": "/cancelDeploymentJob", @@ -314,7 +314,7 @@ } ], "traits": { - "smithy.api#documentation": "Cancels the specified simulation job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCancels the specified simulation job.
", "smithy.api#http": { "method": "POST", "uri": "/cancelSimulationJob", @@ -345,7 +345,7 @@ } ], "traits": { - "smithy.api#documentation": "Cancels a simulation job batch. When you cancel a simulation job batch, you are also\n cancelling all of the active simulation jobs created as part of the batch.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCancels a simulation job batch. When you cancel a simulation job batch, you are also\n cancelling all of the active simulation jobs created as part of the batch.
", "smithy.api#http": { "method": "POST", "uri": "/cancelSimulationJobBatch", @@ -420,7 +420,7 @@ } ], "traits": { - "smithy.api#documentation": "Cancels the specified export job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCancels the specified export job.
", "smithy.api#http": { "method": "POST", "uri": "/cancelWorldExportJob", @@ -473,7 +473,7 @@ } ], "traits": { - "smithy.api#documentation": "Cancels the specified world generator job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCancels the specified world generator job.
", "smithy.api#http": { "method": "POST", "uri": "/cancelWorldGenerationJob", @@ -646,7 +646,7 @@ "smithy.api#deprecated": { "message": "AWS RoboMaker is unable to process this request as the support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Deploys a specific version of a robot application to robots in a fleet.
\nThis API is no longer supported and will throw an error if used.
\nThe robot application must have a numbered applicationVersion
for\n consistency reasons. To create a new version, use\n CreateRobotApplicationVersion
or see Creating a Robot Application Version.
After 90 days, deployment jobs expire and will be deleted. They will no longer be\n accessible.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported and will throw an error if used. For more information, see the January 31, 2022 update in the Support policy page.
\nDeploys a specific version of a robot application to robots in a fleet.
\nThe robot application must have a numbered applicationVersion
for\n consistency reasons. To create a new version, use CreateRobotApplicationVersion
or see \n Creating a Robot Application Version.\n
After 90 days, deployment jobs expire and will be deleted. They will no longer be\n accessible.
\nCreates a fleet, a logical group of robots running the same robot application.
\nThis API is no longer supported and will throw an error if used.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported and will throw an error if used. For more information, see the January 31, 2022 update in the Support policy page.
\nCreates a fleet, a logical group of robots running the same robot application.
", "smithy.api#http": { "method": "POST", "uri": "/createFleet", @@ -886,7 +886,7 @@ "smithy.api#deprecated": { "message": "AWS RoboMaker is unable to process this request as the support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Creates a robot.
\nThis API is no longer supported and will throw an error if used.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported and will throw an error if used. For more information, see the January 31, 2022 update in the Support policy page.
\nCreates a robot.
", "smithy.api#http": { "method": "POST", "uri": "/createRobot", @@ -923,7 +923,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a robot application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a robot application.
", "smithy.api#http": { "method": "POST", "uri": "/createRobotApplication", @@ -950,7 +950,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribuition) used by the robot application.
", + "smithy.api#documentation": "The robot software suite used by the robot application.
", "smithy.api#required": {} } }, @@ -1001,7 +1001,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribution) used by the robot application.
" + "smithy.api#documentation": "The robot software suite used by the robot application.
" } }, "lastUpdatedAt": { @@ -1059,7 +1059,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a version of a robot application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a version of a robot application.
", "smithy.api#http": { "method": "POST", "uri": "/createRobotApplicationVersion", @@ -1130,7 +1130,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribution) used by the robot application.
" + "smithy.api#documentation": "The robot software suite used by the robot application.
" } }, "lastUpdatedAt": { @@ -1270,7 +1270,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a simulation application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a simulation application.
", "smithy.api#http": { "method": "POST", "uri": "/createSimulationApplication", @@ -1304,7 +1304,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribution) used by the simulation application.
", + "smithy.api#documentation": "The robot software suite used by the simulation application.
", "smithy.api#required": {} } }, @@ -1367,7 +1367,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "Information about the robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about the robot software suite.
" } }, "renderingEngine": { @@ -1431,7 +1431,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a simulation application with a specific revision id.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a simulation application with a specific revision id.
", "smithy.api#http": { "method": "POST", "uri": "/createSimulationApplicationVersion", @@ -1508,7 +1508,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "Information about the robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about the robot software suite.
" } }, "renderingEngine": { @@ -1572,7 +1572,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a simulation job.
\nAfter 90 days, simulation jobs expire and will be deleted. They will no longer be\n accessible.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a simulation job.
\nAfter 90 days, simulation jobs expire and will be deleted. They will no longer be\n accessible.
\nCreates a world export job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a world export job.
", "smithy.api#http": { "method": "POST", "uri": "/createWorldExportJob", @@ -1957,7 +1957,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates worlds using the specified template.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates worlds using the specified template.
", "smithy.api#http": { "method": "POST", "uri": "/createWorldGenerationJob", @@ -2097,7 +2097,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates a world template.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nCreates a world template.
", "smithy.api#http": { "method": "POST", "uri": "/createWorldTemplate", @@ -2333,7 +2333,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Deletes a fleet.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nDeletes a fleet.
", "smithy.api#http": { "method": "POST", "uri": "/deleteFleet", @@ -2392,7 +2392,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Deletes a robot.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nDeletes a robot.
", "smithy.api#http": { "method": "POST", "uri": "/deleteRobot", @@ -2420,7 +2420,7 @@ } ], "traits": { - "smithy.api#documentation": "Deletes a robot application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDeletes a robot application.
", "smithy.api#http": { "method": "POST", "uri": "/deleteRobotApplication", @@ -2504,7 +2504,7 @@ } ], "traits": { - "smithy.api#documentation": "Deletes a simulation application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDeletes a simulation application.
", "smithy.api#http": { "method": "POST", "uri": "/deleteSimulationApplication", @@ -2563,7 +2563,7 @@ } ], "traits": { - "smithy.api#documentation": "Deletes a world template.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDeletes a world template.
", "smithy.api#http": { "method": "POST", "uri": "/deleteWorldTemplate", @@ -3003,7 +3003,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Deregisters a robot.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nDeregisters a robot.
", "smithy.api#http": { "method": "POST", "uri": "/deregisterRobot", @@ -3085,7 +3085,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Describes a deployment job.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nDescribes a deployment job.
", "smithy.api#http": { "method": "POST", "uri": "/describeDeploymentJob", @@ -3208,7 +3208,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Describes a fleet.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nDescribes a fleet.
", "smithy.api#http": { "method": "POST", "uri": "/describeFleet", @@ -3319,7 +3319,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Describes a robot.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\nDescribes a robot.
", "smithy.api#http": { "method": "POST", "uri": "/describeRobot", @@ -3350,7 +3350,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a robot application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a robot application.
", "smithy.api#http": { "method": "POST", "uri": "/describeRobotApplication", @@ -3409,7 +3409,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribution) used by the robot application.
" + "smithy.api#documentation": "The robot software suite used by the robot application.
" } }, "revisionId": { @@ -3559,7 +3559,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a simulation application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a simulation application.
", "smithy.api#http": { "method": "POST", "uri": "/describeSimulationApplication", @@ -3624,7 +3624,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "Information about the robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about the robot software suite.
" } }, "renderingEngine": { @@ -3691,7 +3691,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a simulation job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a simulation job.
", "smithy.api#http": { "method": "POST", "uri": "/describeSimulationJob", @@ -3719,7 +3719,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a simulation job batch.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a simulation job batch.
", "smithy.api#http": { "method": "POST", "uri": "/describeSimulationJobBatch", @@ -3996,7 +3996,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a world.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a world.
", "smithy.api#http": { "method": "POST", "uri": "/describeWorld", @@ -4027,7 +4027,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a world export job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a world export job.
", "smithy.api#http": { "method": "POST", "uri": "/describeWorldExportJob", @@ -4138,7 +4138,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a world generation job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a world generation job.
", "smithy.api#http": { "method": "POST", "uri": "/describeWorldGenerationJob", @@ -4317,7 +4317,7 @@ } ], "traits": { - "smithy.api#documentation": "Describes a world template.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nDescribes a world template.
", "smithy.api#http": { "method": "POST", "uri": "/describeWorldTemplate", @@ -4710,7 +4710,7 @@ } ], "traits": { - "smithy.api#documentation": "Gets the world template body.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nGets the world template body.
", "smithy.api#http": { "method": "POST", "uri": "/getWorldTemplateBody", @@ -4936,7 +4936,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Returns a list of deployment jobs for a fleet. You can optionally provide filters to retrieve specific deployment jobs.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\n\n Returns a list of deployment jobs for a fleet. You can optionally provide filters to retrieve specific deployment jobs.\n
", "smithy.api#http": { "method": "POST", "uri": "/listDeploymentJobs", @@ -5028,7 +5028,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Returns a list of fleets. You can optionally provide filters to retrieve specific fleets.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\n\n Returns a list of fleets. You can optionally provide filters to retrieve specific fleets.\n
", "smithy.api#http": { "method": "POST", "uri": "/listFleets", @@ -5114,7 +5114,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns a list of robot application. You can optionally provide filters to retrieve\n specific robot applications.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nReturns a list of robot application. You can optionally provide filters to retrieve\n specific robot applications.
", "smithy.api#http": { "method": "POST", "uri": "/listRobotApplications", @@ -5206,7 +5206,7 @@ "smithy.api#deprecated": { "message": "Support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Returns a list of robots. You can optionally provide filters to retrieve specific robots.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\n\n Returns a list of robots. You can optionally provide filters to retrieve specific robots.\n
", "smithy.api#http": { "method": "POST", "uri": "/listRobots", @@ -5292,7 +5292,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns a list of simulation applications. You can optionally provide filters to\n retrieve specific simulation applications.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nReturns a list of simulation applications. You can optionally provide filters to\n retrieve specific simulation applications.
", "smithy.api#http": { "method": "POST", "uri": "/listSimulationApplications", @@ -5375,7 +5375,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns a list simulation job batches. You can optionally provide filters to retrieve\n specific simulation batch jobs.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nReturns a list simulation job batches. You can optionally provide filters to retrieve\n specific simulation batch jobs.
", "smithy.api#http": { "method": "POST", "uri": "/listSimulationJobBatches", @@ -5455,7 +5455,7 @@ } ], "traits": { - "smithy.api#documentation": "Returns a list of simulation jobs. You can optionally provide filters to retrieve\n specific simulation jobs.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nReturns a list of simulation jobs. You can optionally provide filters to retrieve\n specific simulation jobs.
", "smithy.api#http": { "method": "POST", "uri": "/listSimulationJobs", @@ -5539,7 +5539,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists all tags on a AWS RoboMaker resource.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nLists all tags on a AWS RoboMaker resource.
", "smithy.api#http": { "method": "GET", "uri": "/tags/{resourceArn}", @@ -5597,7 +5597,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists world export jobs.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nLists world export jobs.
", "smithy.api#http": { "method": "POST", "uri": "/listWorldExportJobs", @@ -5678,7 +5678,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists world generator jobs.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nLists world generator jobs.
", "smithy.api#http": { "method": "POST", "uri": "/listWorldGenerationJobs", @@ -5759,7 +5759,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists world templates.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nLists world templates.
", "smithy.api#http": { "method": "POST", "uri": "/listWorldTemplates", @@ -5833,7 +5833,7 @@ } ], "traits": { - "smithy.api#documentation": "Lists worlds.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nLists worlds.
", "smithy.api#http": { "method": "POST", "uri": "/listWorlds", @@ -6154,7 +6154,7 @@ "smithy.api#deprecated": { "message": "AWS RoboMaker is unable to process this request as the support for the AWS RoboMaker application deployment feature has ended. For additional information, see https://docs.aws.amazon.com/robomaker/latest/dg/fleets.html." }, - "smithy.api#documentation": "Registers a robot with a fleet.
\nThis API is no longer supported and will throw an error if used.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nRegisters a robot with a fleet.
\nThis API is no longer supported and will throw an error if used. For more information, see the January 31, 2022 update in the Support policy page.
\nRestarts a running simulation job.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nRestarts a running simulation job.
", "smithy.api#http": { "method": "POST", "uri": "/restartSimulationJob", @@ -6533,7 +6533,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "Information about a robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about a robot software suite.
" } } }, @@ -6650,18 +6650,18 @@ "name": { "target": "com.amazonaws.robomaker#RobotSoftwareSuiteType", "traits": { - "smithy.api#documentation": "The name of the robot software suite (ROS distribution).
" + "smithy.api#documentation": "The name of the robot software suite. General
is the only supported value.
The version of the robot software suite (ROS distribution).
" + "smithy.api#documentation": "The version of the robot software suite. Not applicable for General software suite.
" } } }, "traits": { - "smithy.api#documentation": "Information about a robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about a robot software suite.
" } }, "com.amazonaws.robomaker#RobotSoftwareSuiteType": { @@ -6937,7 +6937,7 @@ "worldConfigs": { "target": "com.amazonaws.robomaker#WorldConfigs", "traits": { - "smithy.api#documentation": "A list of world configurations.
" + "smithy.api#documentation": "A list of world configurations.
\nThis API is no longer supported and will throw an error if used.
\nInformation about a robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about a robot software suite.
" } }, "simulationSoftwareSuite": { @@ -7267,7 +7267,7 @@ "lastUpdatedAt": { "target": "com.amazonaws.robomaker#LastUpdatedAt", "traits": { - "smithy.api#documentation": "The time, in milliseconds since the epoch, when the simulation job batch was last\n updated.
" + "smithy.api#documentation": "The time, in milliseconds since the epoch, when the simulation job batch was last updated.\n
" } }, "createdAt": { @@ -7717,13 +7717,13 @@ "name": { "target": "com.amazonaws.robomaker#SimulationSoftwareSuiteType", "traits": { - "smithy.api#documentation": "The name of the simulation software suite.
" + "smithy.api#documentation": "The name of the simulation software suite. SimulationRuntime
is the only supported value.
The version of the simulation software suite.
" + "smithy.api#documentation": "The version of the simulation software suite. Not applicable for SimulationRuntime
.
Starts a new simulation job batch. The batch is defined using one or more\n SimulationJobRequest
objects.
End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nStarts a new simulation job batch. The batch is defined using one or more\n SimulationJobRequest
objects.
Syncrhonizes robots in a fleet to the latest deployment. This is helpful if robots were added after a deployment.
\nThis API will no longer be supported as of May 2, 2022. Use it to remove resources that were created for Deployment Service.
\nEnd of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nThis API is no longer supported. For more information, see the May 2, 2022 update in the Support policy page.
\n\n Syncrhonizes robots in a fleet to the latest deployment. This is helpful if robots were added after a deployment.\n
", "smithy.api#http": { "method": "POST", "uri": "/syncDeploymentJob", @@ -8185,7 +8185,7 @@ } ], "traits": { - "smithy.api#documentation": "Adds or edits tags for a AWS RoboMaker resource.
\nEach tag consists of a tag key and a tag value. Tag keys and tag values are both\n required, but tag values can be empty strings.
\nFor information about the rules that apply to tag keys and tag values, see User-Defined Tag Restrictions in the AWS Billing and Cost Management\n User Guide.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nAdds or edits tags for a AWS RoboMaker resource.
\nEach tag consists of a tag key and a tag value. Tag keys and tag values are both\n required, but tag values can be empty strings.
\nFor information about the rules that apply to tag keys and tag values, see User-Defined Tag Restrictions in the AWS Billing and Cost Management\n User Guide.
", "smithy.api#http": { "method": "POST", "uri": "/tags/{resourceArn}", @@ -8407,7 +8407,7 @@ } ], "traits": { - "smithy.api#documentation": "Removes the specified tags from the specified AWS RoboMaker resource.
\nTo remove a tag, specify the tag key. To change the tag value of an existing tag key,\n use \n TagResource
\n .
End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nRemoves the specified tags from the specified AWS RoboMaker resource.
\nTo remove a tag, specify the tag key. To change the tag value of an existing tag key,\n use \n TagResource
\n .
Updates a robot application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nUpdates a robot application.
", "smithy.api#http": { "method": "POST", "uri": "/updateRobotApplication", @@ -8499,7 +8499,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribution) used by the robot application.
", + "smithy.api#documentation": "The robot software suite used by the robot application.
", "smithy.api#required": {} } }, @@ -8550,7 +8550,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "The robot software suite (ROS distribution) used by the robot application.
" + "smithy.api#documentation": "The robot software suite used by the robot application.
" } }, "lastUpdatedAt": { @@ -8602,7 +8602,7 @@ } ], "traits": { - "smithy.api#documentation": "Updates a simulation application.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nUpdates a simulation application.
", "smithy.api#http": { "method": "POST", "uri": "/updateSimulationApplication", @@ -8636,7 +8636,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "Information about the robot software suite (ROS distribution).
", + "smithy.api#documentation": "Information about the robot software suite.
", "smithy.api#required": {} } }, @@ -8699,7 +8699,7 @@ "robotSoftwareSuite": { "target": "com.amazonaws.robomaker#RobotSoftwareSuite", "traits": { - "smithy.api#documentation": "Information about the robot software suite (ROS distribution).
" + "smithy.api#documentation": "Information about the robot software suite.
" } }, "renderingEngine": { @@ -8754,7 +8754,7 @@ } ], "traits": { - "smithy.api#documentation": "Updates a world template.
", + "smithy.api#documentation": "End of support notice: On September 10, 2025, Amazon Web Services\n will discontinue support for Amazon Web Services RoboMaker. After September 10, 2025, you will\n no longer be able to access the Amazon Web Services RoboMaker console or Amazon Web Services RoboMaker resources. \n For more information on transitioning to Batch to help run containerized\n simulations, visit https://aws.amazon.com/blogs/hpc/run-simulations-using-multiple-containers-in-a-single-aws-batch-job/.\n
\nUpdates a world template.
", "smithy.api#http": { "method": "POST", "uri": "/updateWorldTemplate", @@ -8850,7 +8850,7 @@ "name": { "target": "com.amazonaws.robomaker#Name", "traits": { - "smithy.api#documentation": "A prefix that specifies where files will be uploaded in Amazon S3. It is appended to the\n simulation output location to determine the final path.
\n For example, if your simulation output location is s3://my-bucket
and your\n upload configuration name is robot-test
, your files will be uploaded to\n s3://my-bucket/
.
A prefix that specifies where files will be uploaded in Amazon S3. It is appended to the\n simulation output location to determine the final path.
\n For example, if your simulation output location is s3://amzn-s3-demo-bucket
and your\n upload configuration name is robot-test
, your files will be uploaded to\n s3://amzn-s3-demo-bucket/
.