You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(client-app-mesh): This release updates the existing Create and Update APIs for meshes and virtual nodes by adding a new IP preference field. This new IP preference field can be used to control the IP versions being used with the mesh and allows for IPv6 support within App Mesh.
Copy file name to clipboardExpand all lines: clients/client-app-mesh/README.md
+10-8
Original file line number
Diff line number
Diff line change
@@ -9,15 +9,17 @@
9
9
10
10
AWS SDK for JavaScript AppMesh Client for Node.js, Browser and React Native.
11
11
12
-
<p>App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and
13
-
control microservices. App Mesh standardizes how your microservices communicate, giving you
14
-
end-to-end visibility and helping to ensure high availability for your applications.</p>
15
-
<p>App Mesh gives you consistent visibility and network traffic controls for every
16
-
microservice in an application. You can use App Mesh with Amazon Web Services Fargate, Amazon ECS, Amazon EKS,
17
-
Kubernetes on Amazon Web Services, and Amazon EC2.</p>
12
+
<p>App Mesh is a service mesh based on the Envoy proxy that makes it easy to
13
+
monitor and control microservices. App Mesh standardizes how your microservices
14
+
communicate, giving you end-to-end visibility and helping to ensure high availability for
15
+
your applications.</p>
16
+
<p>App Mesh gives you consistent visibility and network traffic controls for
17
+
every microservice in an application. You can use App Mesh with Amazon Web Services Fargate, Amazon ECS, Amazon EKS, Kubernetes on Amazon Web Services, and
18
+
Amazon EC2.</p>
18
19
<note>
19
-
<p>App Mesh supports microservice applications that use service discovery naming for their
20
-
components. For more information about service discovery on Amazon ECS, see <ahref="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service Discovery</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes
20
+
<p>App Mesh supports microservice applications that use service discovery
21
+
naming for their components. For more information about service discovery on Amazon ECS, see <ahref="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
22
+
Discovery</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes
21
23
<code>kube-dns</code> and <code>coredns</code> are supported. For more information,
22
24
see <ahref="https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/">DNS
23
25
for Services and Pods</a> in the Kubernetes documentation.</p>
Copy file name to clipboardExpand all lines: clients/client-app-mesh/src/AppMesh.ts
+20-18
Original file line number
Diff line number
Diff line change
@@ -158,15 +158,17 @@ import {
158
158
}from"./commands/UpdateVirtualServiceCommand";
159
159
160
160
/**
161
-
* <p>App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and
162
-
* control microservices. App Mesh standardizes how your microservices communicate, giving you
163
-
* end-to-end visibility and helping to ensure high availability for your applications.</p>
164
-
* <p>App Mesh gives you consistent visibility and network traffic controls for every
165
-
* microservice in an application. You can use App Mesh with Amazon Web Services Fargate, Amazon ECS, Amazon EKS,
166
-
* Kubernetes on Amazon Web Services, and Amazon EC2.</p>
161
+
* <p>App Mesh is a service mesh based on the Envoy proxy that makes it easy to
162
+
* monitor and control microservices. App Mesh standardizes how your microservices
163
+
* communicate, giving you end-to-end visibility and helping to ensure high availability for
164
+
* your applications.</p>
165
+
* <p>App Mesh gives you consistent visibility and network traffic controls for
166
+
* every microservice in an application. You can use App Mesh with Amazon Web Services Fargate, Amazon ECS, Amazon EKS, Kubernetes on Amazon Web Services, and
167
+
* Amazon EC2.</p>
167
168
* <note>
168
-
* <p>App Mesh supports microservice applications that use service discovery naming for their
169
-
* components. For more information about service discovery on Amazon ECS, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service Discovery</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes
169
+
* <p>App Mesh supports microservice applications that use service discovery
170
+
* naming for their components. For more information about service discovery on Amazon ECS, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
171
+
* Discovery</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes
170
172
* <code>kube-dns</code> and <code>coredns</code> are supported. For more information,
171
173
* see <a href="https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/">DNS
172
174
* for Services and Pods</a> in the Kubernetes documentation.</p>
@@ -272,10 +274,9 @@ export class AppMesh extends AppMeshClient {
272
274
/**
273
275
* <p>Creates a virtual gateway.</p>
274
276
* <p>A virtual gateway allows resources outside your mesh to communicate to resources that
275
-
* are inside your mesh. The virtual gateway represents an Envoy proxy running in an Amazon ECS
276
-
* task, in a Kubernetes service, or on an Amazon EC2 instance. Unlike a virtual node, which
277
-
* represents an Envoy running with an application, a virtual gateway represents Envoy
278
-
* deployed by itself.</p>
277
+
* are inside your mesh. The virtual gateway represents an Envoy proxy running in an Amazon ECS task, in a Kubernetes service, or on an Amazon EC2 instance. Unlike a
278
+
* virtual node, which represents an Envoy running with an application, a virtual gateway
279
+
* represents Envoy deployed by itself.</p>
279
280
* <p>For more information about virtual gateways, see <a href="https://docs.aws.amazon.com/app-mesh/latest/userguide/virtual_gateways.html">Virtual gateways</a>. </p>
280
281
*/
281
282
publiccreateVirtualGateway(
@@ -309,10 +310,10 @@ export class AppMesh extends AppMeshClient {
309
310
310
311
/**
311
312
* <p>Creates a virtual node within a service mesh.</p>
312
-
* <p> A virtual node acts as a logical pointer to a particular task group, such as an Amazon ECS
313
-
* service or a Kubernetes deployment. When you create a virtual node, you can specify the
314
-
* service discovery information for your task group, and whether the proxy running in a task
315
-
* group will communicate with other proxies using Transport Layer Security (TLS).</p>
313
+
* <p> A virtual node acts as a logical pointer to a particular task group, such as an Amazon ECS service or a Kubernetes deployment. When you create a virtual node, you can
314
+
* specify the service discovery information for your task group, and whether the proxy
315
+
* running in a task group will communicate with other proxies using Transport Layer Security
316
+
* (TLS).</p>
316
317
* <p>You define a <code>listener</code> for any inbound traffic that your virtual node
317
318
* expects. Any virtual service that your virtual node expects to communicate to is specified
318
319
* as a <code>backend</code>.</p>
@@ -329,8 +330,9 @@ export class AppMesh extends AppMeshClient {
329
330
* <code>APPMESH_RESOURCE_CLUSTER</code> environment variable with your own name.</p>
330
331
* </note>
331
332
* <p>For more information about virtual nodes, see <a href="https://docs.aws.amazon.com/app-mesh/latest/userguide/virtual_nodes.html">Virtual nodes</a>. You must be using <code>1.15.0</code> or later of the Envoy image when
332
-
* setting these variables. For more information aboutApp Mesh Envoy variables, see <a href="https://docs.aws.amazon.com/app-mesh/latest/userguide/envoy.html">Envoy image</a> in
333
-
* the AWS App Mesh User Guide.</p>
333
+
* setting these variables. For more information aboutApp Mesh Envoy variables, see
* <p>App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and
381
-
* control microservices. App Mesh standardizes how your microservices communicate, giving you
382
-
* end-to-end visibility and helping to ensure high availability for your applications.</p>
383
-
* <p>App Mesh gives you consistent visibility and network traffic controls for every
384
-
* microservice in an application. You can use App Mesh with Amazon Web Services Fargate, Amazon ECS, Amazon EKS,
385
-
* Kubernetes on Amazon Web Services, and Amazon EC2.</p>
380
+
* <p>App Mesh is a service mesh based on the Envoy proxy that makes it easy to
381
+
* monitor and control microservices. App Mesh standardizes how your microservices
382
+
* communicate, giving you end-to-end visibility and helping to ensure high availability for
383
+
* your applications.</p>
384
+
* <p>App Mesh gives you consistent visibility and network traffic controls for
385
+
* every microservice in an application. You can use App Mesh with Amazon Web Services Fargate, Amazon ECS, Amazon EKS, Kubernetes on Amazon Web Services, and
386
+
* Amazon EC2.</p>
386
387
* <note>
387
-
* <p>App Mesh supports microservice applications that use service discovery naming for their
388
-
* components. For more information about service discovery on Amazon ECS, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service Discovery</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes
388
+
* <p>App Mesh supports microservice applications that use service discovery
389
+
* naming for their components. For more information about service discovery on Amazon ECS, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-discovery.html">Service
390
+
* Discovery</a> in the <i>Amazon Elastic Container Service Developer Guide</i>. Kubernetes
389
391
* <code>kube-dns</code> and <code>coredns</code> are supported. For more information,
390
392
* see <a href="https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/">DNS
391
393
* for Services and Pods</a> in the Kubernetes documentation.</p>
* <p>A virtual gateway allows resources outside your mesh to communicate to resources that
28
-
* are inside your mesh. The virtual gateway represents an Envoy proxy running in an Amazon ECS
29
-
* task, in a Kubernetes service, or on an Amazon EC2 instance. Unlike a virtual node, which
30
-
* represents an Envoy running with an application, a virtual gateway represents Envoy
31
-
* deployed by itself.</p>
28
+
* are inside your mesh. The virtual gateway represents an Envoy proxy running in an Amazon ECS task, in a Kubernetes service, or on an Amazon EC2 instance. Unlike a
29
+
* virtual node, which represents an Envoy running with an application, a virtual gateway
30
+
* represents Envoy deployed by itself.</p>
32
31
* <p>For more information about virtual gateways, see <a href="https://docs.aws.amazon.com/app-mesh/latest/userguide/virtual_gateways.html">Virtual gateways</a>. </p>
33
32
* @example
34
33
* Use a bare-bones client and the command you need to make an API call.
* <p>Creates a virtual node within a service mesh.</p>
27
-
* <p> A virtual node acts as a logical pointer to a particular task group, such as an Amazon ECS
28
-
* service or a Kubernetes deployment. When you create a virtual node, you can specify the
29
-
* service discovery information for your task group, and whether the proxy running in a task
30
-
* group will communicate with other proxies using Transport Layer Security (TLS).</p>
27
+
* <p> A virtual node acts as a logical pointer to a particular task group, such as an Amazon ECS service or a Kubernetes deployment. When you create a virtual node, you can
28
+
* specify the service discovery information for your task group, and whether the proxy
29
+
* running in a task group will communicate with other proxies using Transport Layer Security
30
+
* (TLS).</p>
31
31
* <p>You define a <code>listener</code> for any inbound traffic that your virtual node
32
32
* expects. Any virtual service that your virtual node expects to communicate to is specified
* <code>APPMESH_RESOURCE_CLUSTER</code> environment variable with your own name.</p>
45
45
* </note>
46
46
* <p>For more information about virtual nodes, see <a href="https://docs.aws.amazon.com/app-mesh/latest/userguide/virtual_nodes.html">Virtual nodes</a>. You must be using <code>1.15.0</code> or later of the Envoy image when
47
-
* setting these variables. For more information aboutApp Mesh Envoy variables, see <a href="https://docs.aws.amazon.com/app-mesh/latest/userguide/envoy.html">Envoy image</a> in
48
-
* the AWS App Mesh User Guide.</p>
47
+
* setting these variables. For more information aboutApp Mesh Envoy variables, see
0 commit comments