I am trying to configure access logs for AWS Network ELB following this doc https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-access-logs.html
I specified bucket name & prefix, then selected Create this location for me
Following bucket policy was auto generated for the bucket
{
"Version": "2012-10-17",
"Id": "AWSConsole-AccessLogs-Policy-xxxxxxxxxxxxx",
"Statement": [
{
"Sid": "AWSConsoleStmt-xxxxxxxxxxxxx",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::xxxxxxxxxxxx:root"
},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::bucket_name/prefix/AWSLogs/123456789012/*"
},
{
"Sid": "AWSLogDeliveryWrite",
"Effect": "Allow",
"Principal": {
"Service": "delivery.logs.amazonaws.com"
},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::bucket_name/prefix/AWSLogs/123456789012/*",
"Condition": {
"StringEquals": {
"s3:x-amz-acl": "bucket-owner-full-control"
}
}
},
{
"Sid": "AWSLogDeliveryAclCheck",
"Effect": "Allow",
"Principal": {
"Service": "delivery.logs.amazonaws.com"
},
"Action": "s3:GetBucketAcl",
"Resource": "arn:aws:s3:::bucket_name"
}
]
}
Bucket is created, but under AWSLogs/xxxxxxxx
there aren't any log files generated. Anything I am missing here ?
Go to the command prompt and type "wlbs query", as you can see HOST 1 and HOST 2 converged successfully on the cluster. This means things are working well. Ping each server locally and remotely. Ping the virtual IP locally and remotely, you should do this three times to test the NLB working.
From : https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-access-logs.html
Access logs are created only if the load balancer has a TLS listener and they contain information only about TLS requests.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With