|
1 | 1 | { |
2 | 2 | "version": "2.0", |
3 | | - "service": "<p>AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and\n control containerized microservices. App Mesh standardizes how your microservices\n communicate, giving you end-to-end visibility and helping to ensure high-availability for\n your applications.</p>\n <p>App Mesh gives you consistent visibility and network traffic controls for every\n microservice in an application. You can use App Mesh with Amazon ECS\n (using the Amazon EC2 launch type), Amazon EKS, and Kubernetes on AWS.</p>\n <note>\n <p>App Mesh supports containerized microservice applications that use service discovery\n naming for their components. To use App Mesh, you must have a containerized application\n running on Amazon EC2 instances, hosted in either Amazon ECS, Amazon EKS, or Kubernetes on AWS. For\n more information about service discovery on Amazon ECS, see <a href=\"http://docs.aws.amazon.com/AmazonECS/latest/developerguideservice-discovery.html\">Service Discovery</a> in the\n <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes <code>kube-dns</code> is supported.\n For more information, see <a href=\"https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/\">DNS\n for Services and Pods</a> in the Kubernetes documentation.</p>\n </note>", |
| 3 | + "service": "<p>AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and\n control containerized microservices. App Mesh standardizes how your microservices\n communicate, giving you end-to-end visibility and helping to ensure high-availability for\n your applications.</p>\n <p>App Mesh gives you consistent visibility and network traffic controls for every\n microservice in an application. You can use App Mesh with Amazon ECS\n (using the Amazon EC2 launch type), Amazon EKS, and Kubernetes on AWS.</p>\n <note>\n <p>App Mesh supports containerized microservice applications that use service discovery\n naming for their components. To use App Mesh, you must have a containerized application\n running on Amazon EC2 instances, hosted in either Amazon ECS, Amazon EKS, or Kubernetes on AWS. For\n more information about service discovery on Amazon ECS, see <a href=\"http://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html\">Service Discovery</a> in the\n <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes <code>kube-dns</code> is supported.\n For more information, see <a href=\"https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/\">DNS\n for Services and Pods</a> in the Kubernetes documentation.</p>\n </note>", |
4 | 4 | "operations": { |
5 | 5 | "CreateMesh": "<p>Creates a new service mesh. A service mesh is a logical boundary for network traffic\n between the services that reside within it.</p>\n <p>After you create your service mesh, you can create virtual nodes, virtual routers, and\n routes to distribute traffic between the applications in your mesh.</p>", |
6 | 6 | "CreateRoute": "<p>Creates a new route that is associated with a virtual router.</p>\n <p>You can use the <code>prefix</code> parameter in your route specification for path-based\n routing of requests. For example, if your virtual router service name is\n <code>my-service.local</code>, and you want the route to match requests to\n <code>my-service.local/metrics</code>, then your prefix should be\n <code>/metrics</code>.</p>\n <p>If your route matches a request, you can distribute traffic to one or more target\n virtual nodes with relative weighting.</p>", |
|
10 | 10 | "DeleteRoute": "<p>Deletes an existing route.</p>", |
11 | 11 | "DeleteVirtualNode": "<p>Deletes an existing virtual node.</p>", |
12 | 12 | "DeleteVirtualRouter": "<p>Deletes an existing virtual router.</p>\n <p>You must delete any routes associated with the virtual router before you can delete the\n router itself.</p>", |
13 | | - "DescribeMesh": "<p>Describes an existing cluster.</p>", |
| 13 | + "DescribeMesh": "<p>Describes an existing service mesh.</p>", |
14 | 14 | "DescribeRoute": "<p>Describes an existing route.</p>", |
15 | 15 | "DescribeVirtualNode": "<p>Describes an existing virtual node.</p>", |
16 | 16 | "DescribeVirtualRouter": "<p>Describes an existing virtual router.</p>", |
|
210 | 210 | "DnsServiceDiscovery$serviceName": "<p>The DNS service name for your virtual node.</p>" |
211 | 211 | } |
212 | 212 | }, |
213 | | - "DurationMillis": { |
214 | | - "base": null, |
215 | | - "refs": { } |
216 | | - }, |
217 | 213 | "ForbiddenException": { |
218 | 214 | "base": "<p>You do not have permissions to perform this action.</p>", |
219 | 215 | "refs": { } |
220 | 216 | }, |
| 217 | + "HealthCheckIntervalMillis": { |
| 218 | + "base": null, |
| 219 | + "refs": { } |
| 220 | + }, |
221 | 221 | "HealthCheckPolicy": { |
222 | | - "base": "<p>An object representing the health check policy for a virtual node's listener.</p>\n <note>\n <p>Listener health checks are not available during the App Mesh preview.</p>\n </note>", |
| 222 | + "base": "<p>An object representing the health check policy for a virtual node's listener.</p>", |
223 | 223 | "refs": { |
224 | 224 | "HealthCheckPolicy$healthyThreshold": "<p>The number of consecutive successful health checks that must occur before declaring\n listener healthy.</p>", |
225 | 225 | "HealthCheckPolicy$intervalMillis": "<p>The time period in milliseconds between each health check execution.</p>", |
226 | | - "HealthCheckPolicy$path": "<p>The destination path for the health check request.</p>", |
227 | | - "HealthCheckPolicy$port": "<p>The destination port for the health check request.</p>", |
| 226 | + "HealthCheckPolicy$path": "<p>The destination path for the health check request. This is only required if the\n specified protocol is HTTP; if the protocol is TCP, then this parameter is ignored.</p>", |
| 227 | + "HealthCheckPolicy$port": "<p>The destination port for the health check request. This port must match the port defined\n in the <a>PortMapping</a> for the listener.</p>", |
228 | 228 | "HealthCheckPolicy$protocol": "<p>The protocol for the health check request.</p>", |
229 | 229 | "HealthCheckPolicy$timeoutMillis": "<p>The amount of time to wait when receiving a response from the health check, in\n milliseconds.</p>", |
230 | 230 | "HealthCheckPolicy$unhealthyThreshold": "<p>The number of consecutive failed health checks that must occur before declaring a\n virtual node unhealthy. </p>" |
231 | 231 | } |
232 | 232 | }, |
| 233 | + "HealthCheckThreshold": { |
| 234 | + "base": null, |
| 235 | + "refs": { } |
| 236 | + }, |
| 237 | + "HealthCheckTimeoutMillis": { |
| 238 | + "base": null, |
| 239 | + "refs": { } |
| 240 | + }, |
233 | 241 | "HttpRoute": { |
234 | 242 | "base": "<p>An object representing the HTTP routing specification for a route.</p>", |
235 | 243 | "refs": { |
|
336 | 344 | "Listener": { |
337 | 345 | "base": "<p>An object representing a listener for a virtual node.</p>", |
338 | 346 | "refs": { |
339 | | - "Listener$healthCheck": "<p>The health check information for the listener.</p>\n <note>\n <p>Listener health checks are not available during the App Mesh preview.</p>\n </note>", |
| 347 | + "Listener$healthCheck": "<p>The health check information for the listener.</p>", |
340 | 348 | "Listener$portMapping": "<p>The port mapping information for the listener.</p>" |
341 | 349 | } |
342 | 350 | }, |
|
381 | 389 | "base": null, |
382 | 390 | "refs": { } |
383 | 391 | }, |
384 | | - "NonNegativeInt": { |
385 | | - "base": null, |
386 | | - "refs": { } |
387 | | - }, |
388 | 392 | "NotFoundException": { |
389 | 393 | "base": "<p>The specified resource does not exist. Check your request syntax and try again.</p>", |
390 | 394 | "refs": { } |
|
416 | 420 | "base": "<p>An object representing metadata for a resource.</p>", |
417 | 421 | "refs": { |
418 | 422 | "ResourceMetadata$arn": "<p>The full Amazon Resource Name (ARN) for the resource.</p>\n <note>\n <p>After you create a virtual node, set this value (either the full ARN or the\n truncated resource name, for example, <code>mesh/default/virtualNode/simpleapp</code>,\n as the <code>APPMESH_VIRTUAL_NODE_NAME</code> environment variable for your task group's\n Envoy proxy container in your task definition or pod spec. This is then mapped to the\n <code>node.id</code> and <code>node.cluster</code> Envoy parameters.</p>\n <p>If you require your Envoy stats or tracing to use a different name, you can override\n the <code>node.cluster</code> value that is set by\n <code>APPMESH_VIRTUAL_NODE_NAME</code> with the\n <code>APPMESH_VIRTUAL_NODE_CLUSTER</code> environment variable.</p>\n </note>", |
419 | | - "ResourceMetadata$createdAt": "<p>The Unix epoch timestamp in seconds for when the cluster was created.</p>", |
420 | | - "ResourceMetadata$lastUpdatedAt": "<p>The Unix epoch timestamp in seconds for when the cluster was last updated.</p>", |
| 423 | + "ResourceMetadata$createdAt": "<p>The Unix epoch timestamp in seconds for when the resource was created.</p>", |
| 424 | + "ResourceMetadata$lastUpdatedAt": "<p>The Unix epoch timestamp in seconds for when the resource was last updated.</p>", |
421 | 425 | "ResourceMetadata$uid": "<p>The unique identifier for the resource.</p>", |
422 | 426 | "ResourceMetadata$version": "<p>The version of the resource. Resources are created at version 1, and this version is\n incremented each time they are updated.</p>" |
423 | 427 | } |
|
0 commit comments