{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::${bucket_name}/*/AWSLogs/*/*",
      "Principal": {
        "AWS": "arn:aws:iam::${principal}:root"
      }
    }
  ]
}

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": "s3:PutObject",
      "Resource": "arn:aws:s3:::${bucket_name}/*/AWSLogs/*",
      "Principal": {
        "AWS": "arn:aws:iam::${principal}:root"
      }
    }
  ]
}

Update ELB log bucket policy
Update ELB log bucket policy

This commit updates the policy in place for ELB log writing access to S3
in order to remove the false positives recently seen in Trusted Advisor.

I have elected to use the option that AWS indicated in their last
response to the support ticket to solve this issue as it is a more
straightforward approach and keeps the flexibility in place to add
additional ELB's using our exsisting approaches.
