2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Generally, StreamAggregatedResources gRPC config stream to appmesh-envoy-management.eu-west-1.amazonaws.com:443 closed: 13 error is related to the envoy container that is unable to communicate with the appmesh-envoy-management endpoint.
You can consider using the following test from inside a container:
curl -v -k -H 'Content-Type: application/grpc' -X POST https://appmesh-envoy-management.eu-west-1.amazonaws.com:443/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources
In the event you receive a connection refused warning or timeout, consider reviewing the VPC settings or using a VPC Endpoint to the service.
https://docs.aws.amazon.com/app-mesh/latest/userguide/vpc-endpoints.html
con risposta 9 mesi fa
0
Hello,
Thank you for your answer,
I tried to put a command on my container as shown below
"command" : [
"curl -v -k -H 'Content-Type: application/grpc' -X POST https://appmesh-envoy-management.eu-west-1.amazonaws.com:443/envoy.service.discovery.v3.AggregatedDiscoveryService/StreamAggregatedResources"
]
But I got
CannotStartContainerError: ResourceInitializationError: failed to create new container runtime task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "curl -v .. : no such file or directory: unknown,
Would be helpful if I can get an example, I don't see what's the problem exactly,
Thanks,
Ghassen.
con risposta 9 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa