尝试使用Terraform创建AWS VPC安全组时出现周期错误

Kos*_*ris 3 amazon-web-services amazon-vpc terraform

我想创建2个VPC安全组.

一个用于VPC的Bastion主机,一个用于私有子网.

# BASTION # 
resource "aws_security_group" "VPC-BastionSG" {
  name        = "VPC-BastionSG"
  description = "The sec group for the Bastion instance"
  vpc_id      = "aws_vpc.VPC.id"

  ingress {
      from_port = 22
      to_port   = 22
      protocol  = "tcp"
      cidr_blocks = ["my.super.ip/32"]
  } 

  egress {
      # Access to the Private subnet from the bastion host[ssh]
      from_port = 22
      to_port   = 22
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-PrivateSG.id}"]
  }
  egress {
      # Access to the Private subnet from the bastion host[jenkins]
      from_port = 8686
      to_port   = 8686
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-PrivateSG.id}"]
  }

  tags = {
    Name = "VPC-BastionSG"
  }
}

# PRIVATE #
resource "aws_security_group" "VPC-PrivateSG" {
  name        = "VPC-PrivateSG"
  description = "The sec group for the private subnet"
  vpc_id      = "aws_vpc.VPC.id"

  ingress {
      from_port = 22
      to_port   = 22
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-BastionSG.id}"]
  }
  ingress {
      from_port = 80
      to_port   = 80
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-PublicSG.id}"]
  }
  ingress {
      from_port = 443
      to_port   = 443
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-PublicSG.id}"]
  }
  ingress {
      from_port = 3306
      to_port   = 3306
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-PublicSG.id}"]
  }
  ingress {
      from_port = 8686
      to_port   = 8686
      protocol  = "tcp"
      security_groups = ["${aws_security_group.VPC-BastionSG.id}"]
  }
  ingress {
      # ALL TRAFFIC from the same subnet
      from_port = 0
      to_port   = 0
      protocol  = "-1"
      self      = true
  }
  egress {
      # ALL TRAFFIC to outside world
      from_port = 0
      to_port   = 0
      protocol  = "-1"
      cidr_blocks = ["0.0.0.0/0"]
  }
  tags = {
    Name = "VPC-PrivateSG"
  }
}
Run Code Online (Sandbox Code Playgroud)

terraform plan它,我返回此错误:

**`Error configuring: 1 error(s) occurred:
* Cycle: aws_security_group.VPC-BastionSG, aws_security_group.VPC-PrivateSG`**
Run Code Online (Sandbox Code Playgroud)

如果我从PrivateSG中注释掉BastionSG的入口规则,那么计划就可以了.

此外,如果我从BastionSG注释掉PrivateSG的出口规则,它也会执行正常.

用于构建具有公共/私有子网和Bastion主机的VPCAWS方案2描述了我尝试设置的体系结构.

我有通过AWS控制台配置的完全相同的设置,它可以正常播放.

为什么Terraform不接受它?是否有另一种方法将Bastion安全组与私有安全组连接?

编辑

据我所知,两个组之间存在一个循环引用,即使在AWS中它是有效的,它仍然需要打破.

因此,我考虑允许来自Bastion sec组的所有出站流量(0.0.0.0/0),而不是将其指定给各个安全组.

它会对安全性造成不良影响吗?

yda*_*coR 14

Terraform尝试为其正在处理的文件夹中定义的所有资源构建依赖关系链.这样做可以使它在需要按特定顺序构建事物时解决,并且对于它如何工作非常关键.

显然,你的例子会失败,因为你有一个循环依赖(正如Terraform帮助指出的那样),每个安全组依赖于已经创建的另一个安全组.

有时这些可能很难解决,可能意味着你需要重新考虑你想要做的事情(正如你所提到的,一个选择是简单地允许所有出口流量从堡垒主机输出,并且仅限制私有的入口流量实例)但在这种情况下,您可以选择将aws_security_group_rule资源与aws_security_group资源结合使用.

这意味着我们可以首先定义没有规则的空安全组,然后我们可以将其用作我们为组创建的安全组规则的目标.

一个简单的示例可能如下所示:

resource "aws_security_group" "bastion" {
  name = "bastion"
  description = "Bastion security group"
}

resource "aws_security_group_rule" "bastion-to-private-ssh-egress" {
    type = "egress"
    from_port = 22
    to_port = 22
    protocol = "tcp"
    security_group_id = "${aws_security_group.bastion.id}"
    source_security_group_id = "${aws_security_group.private.id}"
}

resource "aws_security_group" "private" {
  name = "private"
  description = "Private security group"
}

resource "aws_security_group_rule" "private-from-bastion-ssh-ingress" {
    type = "ingress"
    from_port = 22
    to_port = 22
    protocol = "tcp"
    security_group_id = "${aws_security_group.private.id}"
    source_security_group_id = "${aws_security_group.bastion.id}"
}
Run Code Online (Sandbox Code Playgroud)

现在,Terraform可以看到依赖链表示必须在这些安全组规则之前创建两个安全组,因为它们都依赖于已经创建的组.

  • 它还为您提供了更精细的控制,这可能是好事还是坏事,具体取决于您如何看待它。使用单独的规则资源意味着您可以随意向 Terraform 之外的组添加额外的规则,并且 Terraform 不会在您下次运行时删除它们。当然,您可能认为这是一件坏事,因为您可能希望 Terraform 强制执行特定的安全配置文件。 (2认同)