Step 1: Create an S3 bucket Step 2: Attach a policy to your S3 bucket Step 3: Configure access logs Step 4: Verify bucket permissions Troubleshooting

Enable access logs for your Application Load Balancer

When you enable access logs for your load balancer, you must specify the name of the S3 bucket where the load balancer will store the logs. The bucket must have a bucket policy that grants Elastic Load Balancing permission to write to the bucket.

Tasks

Step 1: Create an S3 bucket
Step 2: Attach a policy to your S3 bucket
Step 3: Configure access logs
Step 4: Verify bucket permissions
Troubleshooting

Step 1: Create an S3 bucket

When you enable access logs, you must specify an S3 bucket for the access logs. You can use an existing bucket, or create a bucket specifically for access logs. The bucket must meet the following requirements.

Requirements

The bucket must be located in the same Region as the load balancer. The bucket and the load balancer can be owned by different accounts.
The only server-side encryption option that's supported is Amazon S3-managed keys (SSE-S3). For more information, see Amazon S3-managed encryption keys (SSE-S3).

To create an S3 bucket using the Amazon S3 console

Open the Amazon S3 console at https://console.aws.amazon.com/s3/.
Choose Create bucket.
On the Create bucket page, do the following:
1. For Bucket name, enter a name for your bucket. This name must be unique across all existing bucket names in Amazon S3. In some Regions, there might be additional restrictions on bucket names. For more information, see Bucket restrictions and limitations in the Amazon Simple Storage Service User Guide.
2. For AWS Region, select the Region where you created your load balancer.
3. For Default encryption, choose Amazon S3-managed keys (SSE-S3).
4. Choose Create bucket.

Step 2: Attach a policy to your S3 bucket

Your S3 bucket must have a bucket policy that grants Elastic Load Balancing permission to write the access logs to the bucket. Bucket policies are a collection of JSON statements written in the access policy language to define access permissions for your bucket. Each statement includes information about a single permission and contains a series of elements.

If you're using an existing bucket that already has an attached policy, you can add the statement for Elastic Load Balancing access logs to the policy. If you do so, we recommend that you evaluate the resulting set of permissions to ensure that they are appropriate for the users that need access to the bucket for access logs.

Available bucket policies

The bucket policy that you'll use depends on the AWS Region and the type of zone. Each expandable section below contains a bucket policy and information about when to use that policy.

This policy grants permissions to the specified log delivery service. Use this policy for load balancers in Availability Zones and Local Zones in the following Regions:

Asia Pacific (Hyderabad)
Asia Pacific (Malaysia)
Asia Pacific (Melbourne)
Canada West (Calgary)
Europe (Spain)
Europe (Zurich)
Israel (Tel Aviv)
Middle East (UAE)


{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "logdelivery.elasticloadbalancing.amazonaws.com"
      },
      "Action": "s3:PutObject",
      "Resource": "s3-bucket-arn"
    }
  ]
}

Replace s3-bucket-arn with the ARN of the location for your access logs. The ARN that you specify depends on whether you plan to include a prefix when you enable access logs in step 3.

Example S3 bucket ARN with a prefix

The bucket name is amzn-s3-demo-logging-bucket, the prefix is logging-prefix, and the ID of the AWS account with the load balancer is 111122223333.


arn:aws:s3:::amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/111122223333/*

Example S3 bucket ARN with no prefix

The bucket name is amzn-s3-demo-logging-bucket and the ID of the AWS account with the load balancer is 111122223333.


arn:aws:s3:::amzn-s3-demo-logging-bucket/AWSLogs/111122223333/*

Using NotPrincipal when Effect is Deny

If the Amazon S3 bucket policy uses Effect with the value Deny and includes NotPrincipal as shown in the example below, ensure that logdelivery.elasticloadbalancing.amazonaws.com is included in the Service list.


{
  "Effect": "Deny",
  "NotPrincipal": {
    "Service": [
       "logdelivery.elasticloadbalancing.amazonaws.com",
       "example.com"
    ]
  }
},

This policy grants permissions to the specified Elastic Load Balancing account ID. Use this policy for load balancers in Availability Zones or Local Zones in the Regions in the list below.


{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::elb-account-id:root"
      },
      "Action": "s3:PutObject",
      "Resource": "s3-bucket-arn"
    }
  ]
}

Replace elb-account-id with the ID of the AWS account for Elastic Load Balancing for your Region:

US East (N. Virginia) – 127311923021
US East (Ohio) – 033677994240
US West (N. California) – 027434742980
US West (Oregon) – 797873946194
Africa (Cape Town) – 098369216593
Asia Pacific (Hong Kong) – 754344448648
Asia Pacific (Jakarta) – 589379963580
Asia Pacific (Mumbai) – 718504428378
Asia Pacific (Osaka) – 383597477331
Asia Pacific (Seoul) – 600734575887
Asia Pacific (Singapore) – 114774131450
Asia Pacific (Sydney) – 783225319266
Asia Pacific (Tokyo) – 582318560864
Canada (Central) – 985666609251
Europe (Frankfurt) – 054676820928
Europe (Ireland) – 156460612806
Europe (London) – 652711504416
Europe (Milan) – 635631232127
Europe (Paris) – 009996457667
Europe (Stockholm) – 897822967062
Middle East (Bahrain) – 076674570225
South America (São Paulo) – 507241528517

Replace s3-bucket-arn with the ARN of the location for your access logs. The ARN that you specify depends on whether you plan to include a prefix when you enable access logs in step 3.

Example S3 bucket ARN with a prefix

The bucket name is amzn-s3-demo-logging-bucket, the prefix is logging-prefix, and the ID of the AWS account with the load balancer is 111122223333.


arn:aws:s3:::amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/111122223333/*

Example S3 bucket ARN with no prefix

The bucket name is amzn-s3-demo-logging-bucket and ID of the AWS account with the load balancer is 111122223333.


arn:aws:s3:::amzn-s3-demo-logging-bucket/AWSLogs/111122223333/*

Using NotPrincipal when Effect is Deny


{
  "Effect": "Deny",
  "NotPrincipal": {
    "Service": [
       "logdelivery.elasticloadbalancing.amazonaws.com",
       "example.com"
    ]
  }
},

This policy grants permissions to the specified Elastic Load Balancing account ID. Use this policy for load balancers in Availability Zones or Local Zones in the AWS GovCloud (US) Regions in the list below.


{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws-us-gov:iam::elb-account-id:root"
      },
      "Action": "s3:PutObject",
      "Resource": "s3-bucket-arn"
    }
  ]
}

Replace elb-account-id with the ID of the AWS account for Elastic Load Balancing for your AWS GovCloud (US) Region:

AWS GovCloud (US-West) – 048591011584
AWS GovCloud (US-East) – 190560391635

Replace s3-bucket-arn with the ARN of the location for your access logs. The ARN that you specify depends on whether you plan to include a prefix when you enable access logs in step 3.

Example S3 bucket ARN with a prefix

The bucket name is amzn-s3-demo-logging-bucket, the prefix is logging-prefix, and the ID of the AWS account with the load balancer is 111122223333.


arn:aws-us-gov:s3:::amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/111122223333/*

Example S3 bucket ARN with no prefix

The bucket name is amzn-s3-demo-logging-bucket and the ID of the AWS account with the load balancer is 111122223333.


arn:aws-us-gov:s3:::amzn-s3-demo-logging-bucket/AWSLogs/111122223333/*

Using NotPrincipal when Effect is Deny


{
  "Effect": "Deny",
  "NotPrincipal": {
    "Service": [
       "logdelivery.elasticloadbalancing.amazonaws.com",
       "example.com"
    ]
  }
},

The following policy grants permissions to the specified log delivery service. Use this policy for load balancers in Outposts Zones.


{
    "Effect": "Allow",
    "Principal": {
        "Service": "logdelivery.elb.amazonaws.com"
    },
    "Action": "s3:PutObject",
    "Resource": "s3-bucket-arn,
    "Condition": {
        "StringEquals": {
            "s3:x-amz-acl": "bucket-owner-full-control"
        }
    }
}

Replace s3-bucket-arn with the ARN of the location for your access logs. The ARN that you specify depends on whether you plan to include a prefix when you enable access logs in step 3.

Example S3 bucket ARN with a prefix

The bucket name is amzn-s3-demo-logging-bucket, the prefix is logging-prefix, and the ID of the AWS account with the load balancer is 111122223333.


arn:aws:s3:::amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/111122223333/*

Example S3 bucket ARN with no prefix

The bucket name is amzn-s3-demo-logging-bucket and the ID of the AWS account with the load balancer is 111122223333.


arn:aws:s3:::amzn-s3-demo-logging-bucket/AWSLogs/111122223333/*

Using NotPrincipal when Effect is Deny


{
  "Effect": "Deny",
  "NotPrincipal": {
    "Service": [
       "logdelivery.elasticloadbalancing.amazonaws.com",
       "example.com"
    ]
  }
},

To attach a bucket policy for access logs to your bucket using the Amazon S3 console

Open the Amazon S3 console at https://console.aws.amazon.com/s3/.
Select the name of the bucket to open its details page.
Choose Permissions and then choose Bucket policy, Edit.
Update the bucket policy to grant the required permissions.
Choose Save changes.

Step 3: Configure access logs

Use the following procedure to configure access logs to capture request information and deliver log files to your S3 bucket.

Requirements

The bucket must meet the requirements described in step 1, and you must attach a bucket policy as described in step 2. If you include a prefix, it must not include the string "AWSLogs".

To enable access logs for your load balancer using the console

Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
In the navigation pane, choose Load Balancers.
Select the name of your load balancer to open its details page.
On the Attributes tab, choose Edit.
For Monitoring, turn on Access logs.
For S3 URI, enter the S3 URI for your log files. The URI that you specify depends on whether you're using a prefix.
- URI with a prefix: s3://amzn-s3-demo-logging-bucket/logging-prefix
- URI without a prefix: s3://amzn-s3-demo-logging-bucket
Choose Save changes.

To enable access logs using the AWS CLI

Use the modify-load-balancer-attributes command.

To manage the S3 bucket for your access logs

Be sure to disable access logs before you delete the bucket that you configured for access logs. Otherwise, if there is a new bucket with the same name and the required bucket policy but created in an AWS account that you don't own, Elastic Load Balancing could write the access logs for your load balancer to this new bucket.

Step 4: Verify bucket permissions

After access logs are enabled for your load balancer, Elastic Load Balancing validates the S3 bucket and creates a test file to ensure that the bucket policy specifies the required permissions. You can use the Amazon S3 console to verify that the test file was created. The test file is not an actual access log file; it doesn't contain example records.

To verify a test file was created in your bucket using the Amazon S3 console

Open the Amazon S3 console at https://console.aws.amazon.com/s3/.
Select the name of the bucket that you specified for access logs.
Navigate to the test file, ELBAccessLogTestFile. The location depends on whether you're using a prefix.
- Location with a prefix: amzn-s3-demo-logging-bucket/logging-prefix/AWSLogs/123456789012/ELBAccessLogTestFile
- Location without a prefix: amzn-s3-demo-logging-bucket/AWSLogs/123456789012/ELBAccessLogTestFile

Troubleshooting

If you receive an access denied error, the following are possible causes:

The bucket policy does not grant Elastic Load Balancing permission to write access logs to the bucket. Verify that you are using the correct bucket policy for the Region. Verify that the resource ARN uses the same bucket name that you specified when you enabled access logs. Verify that the resource ARN does not include a prefix if you did not specify a prefix when you enabled access logs.
The bucket uses an unsupported server-side encryption option. The bucket must use Amazon S3-managed keys (SSE-S3).

Warning Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Document Conventions

Access logs

Disable access logs