Skip to content

/AWS1/CL_S3=>PUTBUCKETWEBSITE()

About PutBucketWebsite

This operation is not supported for directory buckets.

Sets the configuration of the website that is specified in the website subresource. To configure a bucket as a website, you can add this subresource on the bucket with website configuration information such as the file name of the index document and any redirect rules. For more information, see Hosting Websites on Amazon S3.

This PUT action requires the S3:PutBucketWebsite permission. By default, only the bucket owner can configure the website attached to a bucket; however, bucket owners can allow other users to set the website configuration by writing a bucket policy that grants them the S3:PutBucketWebsite permission.

To redirect all website requests sent to the bucket's website endpoint, you add a website configuration with the following elements. Because all requests are sent to another website, you don't need to provide index document name for the bucket.

  • WebsiteConfiguration

  • RedirectAllRequestsTo

  • HostName

  • Protocol

If you want granular control over redirects, you can use the following elements to add routing rules that describe conditions for redirecting requests and information about the redirect destination. In this case, the website configuration must provide an index document for the bucket, because some requests might not be redirected.

  • WebsiteConfiguration

  • IndexDocument

  • Suffix

  • ErrorDocument

  • Key

  • RoutingRules

  • RoutingRule

  • Condition

  • HttpErrorCodeReturnedEquals

  • KeyPrefixEquals

  • Redirect

  • Protocol

  • HostName

  • ReplaceKeyPrefixWith

  • ReplaceKeyWith

  • HttpRedirectCode

Amazon S3 has a limitation of 50 routing rules per website configuration. If you require more than 50 routing rules, you can use object redirect. For more information, see Configuring an Object Redirect in the Amazon S3 User Guide.

The maximum request length is limited to 128 KB.

Method Signature

IMPORTING

Required arguments:

iv_bucket TYPE /AWS1/S3_BUCKETNAME /AWS1/S3_BUCKETNAME

The bucket name.

io_websiteconfiguration TYPE REF TO /AWS1/CL_S3_WEBSITECONF /AWS1/CL_S3_WEBSITECONF

Container for the request.

Optional arguments:

iv_contentmd5 TYPE /AWS1/S3_CONTENTMD5 /AWS1/S3_CONTENTMD5

The Base64 encoded 128-bit MD5 digest of the data. You must use this header as a message integrity check to verify that the request body was not corrupted in transit. For more information, see RFC 1864.

For requests made using the Amazon Web Services Command Line Interface (CLI) or Amazon Web Services SDKs, this field is calculated automatically.

iv_checksumalgorithm TYPE /AWS1/S3_CHECKSUMALGORITHM /AWS1/S3_CHECKSUMALGORITHM

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, there must be a corresponding x-amz-checksum or x-amz-trailer header sent. Otherwise, Amazon S3 fails the request with the HTTP status code 400 Bad Request. For more information, see Checking object integrity in the Amazon S3 User Guide.

If you provide an individual checksum, Amazon S3 ignores any provided ChecksumAlgorithm parameter.

iv_expectedbucketowner TYPE /AWS1/S3_ACCOUNTID /AWS1/S3_ACCOUNTID

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).

Examples

Syntax Example

This is an example of the syntax for calling the method. It includes every possible argument and initializes every possible value. The data provided is not necessarily semantically accurate (for example the value "string" may be provided for something that is intended to be an instance ID, or in some cases two arguments may be mutually exclusive). The syntax shows the ABAP syntax for creating the various data structures.

lo_client->/aws1/if_s3~putbucketwebsite(
  io_websiteconfiguration = new /aws1/cl_s3_websiteconf(
    io_errordocument = new /aws1/cl_s3_errordocument( |string| )
    io_indexdocument = new /aws1/cl_s3_indexdocument( |string| )
    io_redirectallrequeststo = new /aws1/cl_s3_redirallrequeststo(
      iv_hostname = |string|
      iv_protocol = |string|
    )
    it_routingrules = VALUE /aws1/cl_s3_routingrule=>tt_routingrules(
      (
        new /aws1/cl_s3_routingrule(
          io_condition = new /aws1/cl_s3_condition(
            iv_httperrorcoderetdequals = |string|
            iv_keyprefixequals = |string|
          )
          io_redirect = new /aws1/cl_s3_redirect(
            iv_hostname = |string|
            iv_httpredirectcode = |string|
            iv_protocol = |string|
            iv_replacekeyprefixwith = |string|
            iv_replacekeywith = |string|
          )
        )
      )
    )
  )
  iv_bucket = |string|
  iv_checksumalgorithm = |string|
  iv_contentmd5 = |string|
  iv_expectedbucketowner = |string|
).

Set website configuration on a bucket

The following example adds website configuration to a bucket.

lo_client->/aws1/if_s3~putbucketwebsite(
  io_websiteconfiguration = new /aws1/cl_s3_websiteconf(
    io_errordocument = new /aws1/cl_s3_errordocument( |error.html| )
    io_indexdocument = new /aws1/cl_s3_indexdocument( |index.html| )
  )
  iv_bucket = |examplebucket|
  iv_contentmd5 = ||
).