使用私有子网中的Route53的ECS中的Intranet通信问题 [英] Intranet communication issue in ECS with Route53 in private subnet

查看:101
本文介绍了使用私有子网中的Route53的ECS中的Intranet通信问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已将应用程序托管在私有子网中的ECS群集(EC2模式)上.我正面临服务间通信的问题.

I have hosted our applications on ECS Cluster (EC2 Mode) in a private subnet. I am facing problem with inter-service communication.

  • 我已将任务联网模式设置为桥接.
  • 取决于Route53专用托管区域进行服务发现.
  • 服务已在Route53下以 SRV 记录类型进行注册.
  • 使用.指向我们的托管服务.例如,我托管了名称空间为"local"且服务名称为"redisdb"的redis容器,然后在应用程序中将该服务称为"redisdb.local"
  • I have set task networking mode as bridge.
  • Depending on Route53 private hosted zone for service discovery.
  • The services are getting registered under Route53 with SRV record type.
  • Using . for pointing to our hosted service. For example, I have hosted redis container with namespace "local" and service name as "redisdb" then referring that service in application as "redisdb.local"

但是我在我们的应用程序中收到一条错误消息:名称或服务未知".我还尝试了使用记录类型为 A 的AWSVPC模式.但是我仍然面临着同样的问题.

But I am getting an error in our application saying: "Name or Service not known". I have also tried with AWSVPC mode with A record type. But still I am facing same issue.

我在这里错过了什么吗?任何帮助将不胜感激.

Am I missing anything here? Any help would be appreciated.

推荐答案

hmm,最后通过启用dns主机名解决了该问题

hmm, finally the issue was resolved by enabling the dns hostname

这篇关于使用私有子网中的Route53的ECS中的Intranet通信问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆