listener for any inbound traffic that your virtual node
/// expects. Any virtual service that your virtual node expects to communicate to is specified
/// as a backend.
/// arn that
/// is associated with the virtual node. Set this value to the full ARN; for example,
/// arn:aws:appmesh:us-west-2:123456789012:myMesh/default/virtualNode/myApp)
/// as the APPMESH_RESOURCE_ARN 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.
/// APPMESH_RESOURCE_ARN
/// when Envoy is referring to itself in metrics and traces. You can override this behavior
/// by setting the APPMESH_RESOURCE_CLUSTER environment variable with your
/// own name.
/// 1.15.0 or later of the Envoy image when
/// setting these variables. For more information aboutApp Mesh Envoy variables, see Envoy image
/// in the App Mesh User Guide.
/// True, if a value isn't
/// specified./dev/stdout to send
/// access logs to standard out and configure your Envoy container to use a log driver,
/// such as awslogs, to export the access logs to a log storage service such
/// as Amazon CloudWatch Logs. You can also specify a path in the Envoy container's file
/// system to write the files to disk. <note> <p>The Envoy process must have write permissions to
/// the path that you specify here. Otherwise, Envoy fails to bootstrap properly.</p>
/// </note>
///