使用EC2时，ECS群集不能在私有子网中运行任务

Question

我有一个任务定义，它配置为使用awsvpc网络模式。根据这

对于awsvpc网络模式，只支持私有子网。由于任务不接收公共IP地址，出站internet访问需要NAT网关，而入站互联网流量应通过负载均衡器路由。

我在公共子网(有internet网关)中设置了NAT网关，并在私有子网中设置了配置路由表，以便将流量发送到NAT网关。但是，当我想要创建驻留在私有子网中的任务时，我得到：

Run tasks failed Reasons : ["ATTRIBUTE"]. Learn more

如果我选择EC2本身使用的公共子网，它将创建该任务。但我不能在我的任务中访问互联网。

我的最后一个目标是从EC2的任务中访问互联网。

更新:我的任务定义：

{
"ipcMode": null,
"executionRoleArn": "arn:aws:iam::783294628224:role/ecsTaskExecutionRole",
"containerDefinitions": [
{
"dnsSearchDomains": null,
"logConfiguration": {
"logDriver": "awslogs",
"options": {
"awslogs-group": "/ecs/TEST-Task-Definition",
"awslogs-region": "us-west-2",
"awslogs-stream-prefix": "ecs"
}
},
"entryPoint": null,
"portMappings": [
{
"hostPort": 8500,
"protocol": "tcp",
"containerPort": 8500
},
{
"hostPort": 8501,
"protocol": "tcp",
"containerPort": 8501
}
],
"command": null,
"linuxParameters": null,
"cpu": 0,
"environment": [],
"resourceRequirements": null,
"ulimits": null,
"dnsServers": null,
"mountPoints": [],
"workingDirectory": null,
"secrets": null,
"dockerSecurityOptions": null,
"memory": null,
"memoryReservation": 500,
"volumesFrom": [],
"stopTimeout": null,
"image": "<MY ECR REPOSITORY ADDRESS FOR IMAGE 1>",
"startTimeout": null,
"dependsOn": null,
"disableNetworking": null,
"interactive": null,
"healthCheck": null,
"essential": true,
"links": null,
"hostname": null,
"extraHosts": null,
"pseudoTerminal": null,
"user": "root",
"readonlyRootFilesystem": null,
"dockerLabels": null,
"systemControls": null,
"privileged": true,
"name": "backend"
},
{
"dnsSearchDomains": null,
"logConfiguration": {
"logDriver": "awslogs",
"options": {
"awslogs-group": "/ecs/TEST-Task-Definition",
"awslogs-region": "us-west-2",
"awslogs-stream-prefix": "ecs"
}
},
"entryPoint": null,
"portMappings": [
{
"hostPort": 80,
"protocol": "tcp",
"containerPort": 80
}
],
"command": null,
"linuxParameters": null,
"cpu": 0,
"environment": [],
"resourceRequirements": null,
"ulimits": null,
"dnsServers": null,
"mountPoints": [],
"workingDirectory": null,
"secrets": null,
"dockerSecurityOptions": null,
"memory": null,
"memoryReservation": 500,
"volumesFrom": [],
"stopTimeout": null,
"image": "<MY ECR REPOSITORY ADDRESS FOR IMAGE 2>",
"startTimeout": null,
"dependsOn": null,
"disableNetworking": null,
"interactive": null,
"healthCheck": null,
"essential": true,
"links": null,
"hostname": null,
"extraHosts": null,
"pseudoTerminal": null,
"user": "root",
"readonlyRootFilesystem": null,
"dockerLabels": null,
"systemControls": null,
"privileged": true,
"name": "frontend"
}
],
"memory": null,
"taskRoleArn": "arn:aws:iam::783294628224:role/ecsTaskExecutionRole",
"family": "TEST-Task-Definition",
"pidMode": null,
"requiresCompatibilities": [
"EC2"
],
"networkMode": "awsvpc",
"cpu": null,
"proxyConfiguration": null,
"volumes": [],
"placementConstraints": []
}

Answer 1

我终于解决了我的问题。据我所知，在任务定义中使用awsvpc网络模式时，任务(或服务)必须在EC2子网中创建。此外，如果您希望任务能够访问internet，则应该在另一个子网中创建NAT网关，该子网具有驻留在VPC中的到Internet网关的默认路由。在任务/service/ec2子网中，必须向NAT网关添加默认路由。唯一发生的问题是，您不能再对EC2进行ssh操作了。如果您想对您的EC2进行ssh，我认为您应该设置一个负载均衡器。

Answer 2

如果你不使用AMI.html

确保将代理参数环境键ECS_ENABLE_TASK_ENI设置为true