简体   繁体   English

AWS ECS上的dockerized Jenkins的DNS问题和入站规则

[英]DNS problem and inbound rules for dockerized Jenkins on AWS ECS

I'm setting up a dockerized Jenkins server on AWS using ECS. 我正在使用ECS在AWS上设置dockerized Jenkins服务器。

Here is what I have now. 这就是我现在所拥有的。

  1. A dockerized Jenskins Master running on a EC2 instance. 在EC2实例上运行的dockerized Jenskins Master。

  2. A ECS cluster for dockerized Linux agents. 用于dockerized Linux代理的ECS集群。

  3. A ECS cluster for dockerized Windosw agents. 用于Docker化的Windosw代理的ECS集群。

  4. Both Linux and Windows agents can connect to master by jnlp using Jenkins ECS plugin. Linux和Windows代理都可以使用Jenkins ECS插件通过jnlp连接到master。

Questions: 问题:

  1. How can I set a security group for Master ec2 instance to allow the IP of all ECS cluster instances, now I manually set the IPs of Linux and Windows instances of ECS cluster to the inbound rules so containers can connect to master on port 8080, but those IPs change. 如何为Master ec2实例设置安全组以允许所有ECS群集实例的IP,现在我手动将Linux和Windows ECS群集实例的IP设置为入站规则,以便容器可以在端口8080上连接到master这些IP发生了变化。

  2. The container agent for code building launched from ECS cluster can not parse the company's DNS (Server host name and SVN link of my company are reported as unknown), what is the right way to resolve this problem? 从ECS群集启动的用于代码构建的容器代理无法解析公司的DNS(报告我公司的服务器主机名和SVN链接未知),什么是解决此问题的正确方法?

Thanks. 谢谢。

Why don't you use the private ip addresses instead of going via public internet. 您为什么不使用私有IP地址而不是通过公共Internet访问。 The EC2 instance's security group can allow a private ip subnet such 10.1.0/24. EC2实例的安全组可以允许一个私有IP子网,例如10.1.0 / 24。 The ECS instances can connect to the EC2's private ip address for eg 10.2.1.1. ECS实例可以连接到EC2的私有IP地址,例如10.2.1.1。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM