2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
Can we use the "useDualstackEndpoint" described in the following document to solve this problem?
https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-rekognition/interfaces/endpointsinputconfig.html
0
UseDualStackEndpoint=true is broken for Amazon SES too. The resulting DNS names do not resolve (at least not outside AWS' network). E.g., "email.us-west-2.api.aws" or "email.us-west-1.api.aws". Several DNS servers have been tried. Here's Google saying it doesn't resolve: https://dnschecker.org/all-dns-records-of-domain.php?query=email.us-west-2.api.aws&rtype=ALL&dns=google
The answer seem to be that AWS doesn't actually work with IPv6 ("UseDualStackEndpoint=true").
respondido hace un año
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 3 años
Setting "UseDualStackEndpoint" to true is what causes the AWS SDK to try to use the address "rekognition.us-west-1.api.aws". Since that address does not resolve to anything in DNS, the client cannot reach Rekognition. Setting it to false for the Rekognition service (only) is our current work-around for this problem. Either the "endpoints.json" in the AWS SDK is wrong or the corresponding DNS records need to be added.