Amazon S3 Logging (bucket-level)

openapi: 3.1.0
info:
  title: Amazon S3 Logging (bucket-level)
  description: '2 operations from the Amazon S3 REST API, generated from the authoritative service model.


    S3 identifies these operations by the `logging` query subresource, which is declared as a required
    query parameter on each one because an OpenAPI path cannot carry a query string.


    Generated from boto/botocore `service-2.json` at `aeb03fc4ae530e0b3f47d588b6021581db870c8c` (Apache-2.0).
    Responses are XML.'
  version: '2006-03-01'
  contact:
    name: AWS Support
    url: https://aws.amazon.com/premiumsupport/
externalDocs:
  description: Amazon S3 API Reference
  url: https://docs.aws.amazon.com/AmazonS3/latest/API/
servers:
- url: https://s3.{region}.amazonaws.com
  variables:
    region:
      default: us-east-1
tags:
- name: logging
paths:
  /{Bucket}:
    get:
      operationId: GetBucketLogging
      summary: 'This operation is not supported for directory buckets. Returns the logging status of a
        bucket and the permissions users '
      description: 'This operation is not supported for directory buckets. Returns the logging status
        of a bucket and the permissions users have to view and modify that status. The following operations
        are related to GetBucketLogging: CreateBucket PutBucketLogging You must URL encode any signed
        header values that contain spaces. For example, if your header value is my file.txt, containing
        two spaces after my, you must URL encode this value to my%20%20file.txt.'
      tags:
      - logging
      parameters:
      - name: logging
        in: query
        required: true
        description: Selects this operation. S3 identifies it by the `logging` subresource.
        schema:
          type: string
      - name: Bucket
        in: path
        required: true
        description: The bucket name for which to get the logging information.
        schema:
          type: string
      - name: x-amz-expected-bucket-owner
        in: header
        required: false
        description: The account ID of the expected bucket owner. If the account ID that you provide does
          not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden
          (access denied)
        schema:
          type: string
      responses:
        '200':
          description: Success. S3 answers in XML, not JSON.
          x-output-shape: GetBucketLoggingOutput
        '403':
          description: AccessDenied. S3 validates the signature before it routes the operation, so this
            does not distinguish an unsupported operation from an unauthorised one.
    put:
      operationId: PutBucketLogging
      summary: 'End of support notice: As of October 1, 2025, Amazon S3 has discontinued support for Email
        Grantee Access Control Lists '
      description: 'End of support notice: As of October 1, 2025, Amazon S3 has discontinued support for
        Email Grantee Access Control Lists (ACLs). If you attempt to use an Email Grantee ACL in a request
        after October 1, 2025, the request will receive an HTTP 405 (Method Not Allowed) error. This change
        affects the following Amazon Web Services Regions: US East (N. Virginia), US West (N. California),
        US West (Oregon), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe
        (Ireland), and South America (São Paulo). This operation is not supported for directory buckets.
        Set the logging parameters for a bucket and to specify permissions for who can view and modify
        the logging parameters. All logs are saved to buckets in the same Amazon Web Services Region as
        the source bucket. To set the logging status of a bucket, you must be the bucket owner. The bucket
        owner is automatically granted FULL_CONTROL to all logs. You use the Grantee request element to
        grant access to other people. The Permissions request element specifies the kind of access the
        grantee has to the logs. If the target bucket for log delivery uses the bucket owner enforced
        setting for S3 Object Ownership, you can''t use th'
      tags:
      - logging
      parameters:
      - name: logging
        in: query
        required: true
        description: Selects this operation. S3 identifies it by the `logging` subresource.
        schema:
          type: string
      - name: Bucket
        in: path
        required: true
        description: The name of the bucket for which to set the logging parameters.
        schema:
          type: string
      - name: Content-MD5
        in: header
        required: false
        description: The MD5 hash of the PutBucketLogging request body. For requests made using the Amazon
          Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated
          automatically.
        schema:
          type: string
      - name: x-amz-sdk-checksum-algorithm
        in: header
        required: false
        description: Indicates the algorithm used to create the checksum for the request when you use
          the SDK. This header will not provide any additional functionality if you don't use the SDK.
          When you send this header,
        schema:
          type: string
          enum:
          - CRC32
          - CRC32C
          - SHA1
          - SHA256
          - CRC64NVME
          - SHA512
          - MD5
          - XXHASH64
          - XXHASH3
          - XXHASH128
      - name: x-amz-expected-bucket-owner
        in: header
        required: false
        description: The account ID of the expected bucket owner. If the account ID that you provide does
          not match the actual owner of the bucket, the request fails with the HTTP status code 403 Forbidden
          (access denied)
        schema:
          type: string
      responses:
        '200':
          description: Success. S3 answers in XML, not JSON.
        '403':
          description: AccessDenied. S3 validates the signature before it routes the operation, so this
            does not distinguish an unsupported operation from an unauthorised one.