1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
You're configuring your target group as HTTPS so this is probalbly why you're receiving this error. You can configure your target group to be HTTP and this should allow to connect succesfully :
HubTargetGroup:
Type: "AWS::ElasticLoadBalancingV2::TargetGroup"
Properties:
Port: 50051
Protocol: HTTP #Changed from HTTPS
ProtocolVersion: GRPC
HealthCheckEnabled: true
HealthCheckPath: "/grpc.health.v1.Health/Check"
HealthCheckPort: "traffic-port"
HealthCheckProtocol: HTTP
TargetType: ip
Matcher:
GrpcCode: 0
VpcId: !Ref VpcId
For reference, this blog post is doing pretty match the setup you describe but through the console: https://aws.amazon.com/blogs/aws/new-application-load-balancer-support-for-end-to-end-http-2-and-grpc/
répondu il y a 2 ans
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 5 mois
- AWS OFFICIELA mis à jour il y a 2 ans
Thank you, I was somehow stuck thinking it needed to be HTTPS end-to-end due to a different error message I received concerning ALB listener configuration earlier...