我在使用 Terraform (v0.9.2) 向 ELB 添加服务时遇到问题(我正在使用:https://github.com/segmentio/stack/blob/master/s3-logs/main.tf) .
当我运行
terraform apply
我得到这个错误:
* module.solr.module.elb.aws_elb.main: 1 error(s) occurred:
* aws_elb.main: Failure configuring ELB attributes:
InvalidConfigurationRequest: Access Denied for bucket: my-service-
logs. Please check S3bucket permission
status code: 409, request id: xxxxxxxxxx-xxxx-xxxx-xxxxxxxxx
我的服务是这样的:
module "solr" {
source = "github.com/segmentio/stack/service"
name = "${var.prefix}-${terraform.env}-solr"
environment = "${terraform.env}"
image = "123456789876.dkr.ecr.eu-west-2.amazonaws.com/my-docker-image"
subnet_ids = "${element(split(",", module.vpc_subnets.private_subnets_id), 3)}"
security_groups = "${module.security.apache_solr_group}"
port = "8983"
cluster = "${module.ecs-cluster.name}"
log_bucket = "${module.s3_logs.id}"
iam_role = "${aws_iam_instance_profile.ecs.id}"
dns_name = ""
zone_id = "${var.route53_zone_id}"
}
我的 s3-logs 存储桶如下所示:
module "s3_logs" {
source = "github.com/segmentio/stack/s3-logs"
name = "${var.prefix}"
environment = "${terraform.env}"
account_id = "123456789876"
}
我检查了 S3,存储桶策略如下所示:
{
"Version": "2012-10-17",
"Id": "log-bucket-policy",
"Statement": [
{
"Sid": "log-bucket-policy",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789876:root"
},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::my-service-logs/*"
}
]
}
据我所知,ELB 应该可以访问 S3 存储桶来存储日志(它在同一个 AWS 帐户中运行)。
桶和ELB都在
eu-west-2
.
任何关于问题可能是什么的想法将不胜感激。
ELB 访问日志的docs 说您希望允许特定的 Amazon 帐户能够写入 S3,而不是您的帐户。
因此你想要这样的东西:
{
"Id": "Policy1429136655940",
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1429136633762",
"Action": [
"s3:PutObject"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::my-loadbalancer-logs/my-app/AWSLogs/123456789012/*",
"Principal": {
"AWS": [
"652711504416"
]
}
}
]
}
在 Terraform 中,您可以使用 aws_elb_service_account 数据源 自动获取用于写入日志的帐户 ID,如文档中的示例所示:
data "aws_elb_service_account" "main" {}
resource "aws_s3_bucket" "elb_logs" {
bucket = "my-elb-tf-test-bucket"
acl = "private"
policy = <<POLICY
{
"Id": "Policy",
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:PutObject"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::my-elb-tf-test-bucket/AWSLogs/*",
"Principal": {
"AWS": [
"${data.aws_elb_service_account.main.arn}"
]
}
}
]
}
POLICY
}
resource "aws_elb" "bar" {
name = "my-foobar-terraform-elb"
availability_zones = ["us-west-2a"]
access_logs {
bucket = "${aws_s3_bucket.elb_logs.bucket}"
interval = 5
}
listener {
instance_port = 8000
instance_protocol = "http"
lb_port = 80
lb_protocol = "http"
}
}
即使文档提供了所有内容,我仍不断收到“存储桶访问被拒绝”错误。从存储桶中删除加密对我有用。
在bucket policy中,账号必须不是你的。相反,它属于 AWS,对于每个区域,您应该在存储桶策略中使用的帐号列在:https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-access-logs。 html#attach-bucket-policy
例如
us-east-1
地区的帐号是127311923021
.
虽然问题是关于 Terraform 的,但我发布了 CloudFormation 片段 created a bucket for ELB's access logs its Bucket policy:
MyAccessLogsBucket:
Type: AWS::S3::Bucket
DeletionPolicy: Retain
MyAllowELBAccessBucketPolicy:
Type: AWS::S3::BucketPolicy
Properties:
Bucket: !Ref MyAccessLogsBucket
PolicyDocument:
Version: "2012-10-17"
Statement:
- Effect: "Allow"
Principal:
AWS: "arn:aws:iam::127311923021:root"
Action:
- "s3:PutObject"
Resource: !Sub "arn:aws:s3:::${MyAccessLogsBucket}/AWSLogs/*"
原则上使用
127311923021
,因为这是AWS帐号,应该用于us-east-1
中的帐号。
桶权限 当您启用访问日志记录时,您必须为访问日志指定一个 S3 存储桶。桶必须满足以下要求。 要求 存储桶必须位于与负载均衡器相同的区域中。 需要 Amazon S3 托管加密密钥 (SSE-S3)。不支持其他加密选项。 存储桶必须具有授予 Elastic Load Balancing 将访问日志写入您的存储桶的权限的存储桶策略。存储桶策略是用访问策略语言编写的 JSON 语句的集合,用于定义存储桶的访问权限。每条语句都包含有关单个权限的信息,并包含一系列元素。
使用以下选项之一准备用于访问日志记录的 S3 存储桶。
Amazon S3 托管加密密钥 (SSE-S3) 是必需的。不支持其他加密选项。
所以 AWS 文档说 KMS 不受支持...
就我而言,这是
request_payer
选项设置为 Requester
。需要设置为BucketOwner
才能工作。
请点赞。这是一个完整的工作示例。
data "aws_caller_identity" "current" {}
data "aws_elb_service_account" "elb_account_id" {}
resource "aws_s3_bucket" "lb_logs" {
bucket = "${local.name}-loadbalancer-logs"
}
resource "aws_s3_bucket_policy" "lb_logs" {
bucket = aws_s3_bucket.lb_logs.id
policy = data.aws_iam_policy_document.allow_lb.json
}
data "aws_iam_policy_document" "allow_lb" {
statement {
effect = "Allow"
resources = [
"arn:aws:s3:::${aws_s3_bucket.lb_logs.bucket}/AWSLogs/${data.aws_caller_identity.current.account_id}/*",
]
actions = ["s3:PutObject"]
principals {
type = "AWS"
identifiers = ["arn:aws:iam::${data.aws_elb_service_account.elb_account_id.id}:root"]
}
}
statement {
effect = "Allow"
resources = [
"arn:aws:s3:::${aws_s3_bucket.lb_logs.bucket}/AWSLogs/${data.aws_caller_identity.current.account_id}/*",
]
actions = ["s3:PutObject"]
principals {
type = "Service"
identifiers = ["delivery.logs.amazonaws.com"]
}
condition {
test = "StringEquals"
variable = "s3:x-amz-acl"
values = ["bucket-owner-full-control"]
}
}
statement {
effect = "Allow"
resources = [
"arn:aws:s3:::${aws_s3_bucket.lb_logs.bucket}",
]
actions = ["s3:GetBucketAcl"]
principals {
type = "Service"
identifiers = ["delivery.logs.amazonaws.com"]
}
}
}
resource "aws_alb" "lb" {
name = "${local.name}-lb"
load_balancer_type = "application"
subnets = var.subnet_ids
security_groups = [
aws_security_group.lb.id
]
access_logs {
bucket = aws_s3_bucket.lb_logs.id
enabled = true
}
lifecycle {
create_before_destroy = true
}
tags = {
Name = "${local.name}-lb"
}
}