Creates a virtual node within a service mesh.
appmesh_create_virtual_node(clientToken, meshName, spec, tags,
virtualNodeName)
Unique, case-sensitive identifier that you provide to ensure the idempotency of the request. Up to 36 letters, numbers, hyphens, and underscores are allowed.
[required] The name of the service mesh to create the virtual node in.
[required] The virtual node specification to apply.
Optional metadata that you can apply to the virtual node to assist with categorization and organization. Each tag consists of a key and an optional value, both of which you define. Tag keys can have a maximum character length of 128 characters, and tag values can have a maximum length of 256 characters.
[required] The name to use for the virtual node.
svc$create_virtual_node( clientToken = "string", meshName = "string", spec = list( backends = list( list( virtualService = list( virtualServiceName = "string" ) ) ), listeners = list( list( healthCheck = list( healthyThreshold = 123, intervalMillis = 123, path = "string", port = 123, protocol = "grpc"|"http"|"http2"|"tcp", timeoutMillis = 123, unhealthyThreshold = 123 ), portMapping = list( port = 123, protocol = "grpc"|"http"|"http2"|"tcp" ) ) ), logging = list( accessLog = list( file = list( path = "string" ) ) ), serviceDiscovery = list( awsCloudMap = list( attributes = list( list( key = "string", value = "string" ) ), namespaceName = "string", serviceName = "string" ), dns = list( hostname = "string" ) ) ), tags = list( list( key = "string", value = "string" ) ), virtualNodeName = "string" )
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 specify the service discovery information for your task group.
Any inbound traffic that your virtual node expects should be specified
as a listener
. Any outbound traffic that your virtual node expects to
reach should be specified as a backend
.
The response metadata for your new virtual node contains the arn
that
is associated with the virtual node. Set this value (either the full ARN
or the truncated resource name: for example,
mesh/default/virtualNode/simpleapp
) as the APPMESH_VIRTUAL_NODE_NAME
environment variable for your task group\'s Envoy proxy container in
your task definition or pod spec. This is then mapped to the node.id
and node.cluster
Envoy parameters.
If you require your Envoy stats or tracing to use a different name, you
can override the node.cluster
value that is set by
APPMESH_VIRTUAL_NODE_NAME
with the APPMESH_VIRTUAL_NODE_CLUSTER
environment variable.