Skip to content

/AWS1/IF_S3=>RENAMEOBJECT()

About RenameObject

Renames an existing object in a directory bucket that uses the S3 Express One Zone storage class. You can use RenameObject by specifying an existing object’s name as the source and the new name of the object as the destination within the same directory bucket.

RenameObject is only supported for objects stored in the S3 Express One Zone storage class.

To prevent overwriting an object, you can use the If-None-Match conditional header.

  • If-None-Match - Renames the object only if an object with the specified name does not already exist in the directory bucket. If you don't want to overwrite an existing object, you can add the If-None-Match conditional header with the value ‘*’ in the RenameObject request. Amazon S3 then returns a 412 Precondition Failed error if the object with the specified name already exists. For more information, see RFC 7232.

Permissions

To grant access to the RenameObject operation on a directory bucket, we recommend that you use the CreateSession operation for session-based authorization. Specifically, you grant the s3express:CreateSession permission to the directory bucket in a bucket policy or an IAM identity-based policy. Then, you make the CreateSession API call on the directory bucket to obtain a session token. With the session token in your request header, you can make API requests to this operation. After the session token expires, you make another CreateSession API call to generate a new session token for use. The Amazon Web Services CLI and SDKs will create and manage your session including refreshing the session token automatically to avoid service interruptions when a session expires. In your bucket policy, you can specify the s3express:SessionMode condition key to control who can create a ReadWrite or ReadOnly session. A ReadWrite session is required for executing all the Zonal endpoint API operations, including RenameObject. For more information about authorization, see CreateSession . To learn more about Zonal endpoint API operations, see Authorizing Zonal endpoint API operations with CreateSession in the Amazon S3 User Guide.

HTTP Host header syntax

Directory buckets - The HTTP Host header syntax is Bucket-name.s3express-zone-id.region-code.amazonaws.com.

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.

Method Signature

METHODS /AWS1/IF_S3~RENAMEOBJECT
  IMPORTING
    !IV_BUCKET TYPE /AWS1/S3_BUCKETNAME OPTIONAL
    !IV_KEY TYPE /AWS1/S3_OBJECTKEY OPTIONAL
    !IV_RENAMESOURCE TYPE /AWS1/S3_RENAMESOURCE OPTIONAL
    !IV_DESTINATIONIFMATCH TYPE /AWS1/S3_IFMATCH OPTIONAL
    !IV_DESTINATIONIFNONEMATCH TYPE /AWS1/S3_IFNONEMATCH OPTIONAL
    !IV_DSTIFMODIFIEDSINCE TYPE /AWS1/S3_IFMODIFIEDSINCE OPTIONAL
    !IV_DSTIFUNMODIFIEDSINCE TYPE /AWS1/S3_IFUNMODIFIEDSINCE OPTIONAL
    !IV_SOURCEIFMATCH TYPE /AWS1/S3_RENAMESOURCEIFMATCH OPTIONAL
    !IV_SOURCEIFNONEMATCH TYPE /AWS1/S3_RENAMESRCIFNONEMATCH OPTIONAL
    !IV_SOURCEIFMODIFIEDSINCE TYPE /AWS1/S3_RENAMESRCIFMODSINCE OPTIONAL
    !IV_SOURCEIFUNMODIFIEDSINCE TYPE /AWS1/S3_RENAMESRCIFUNMODSINCE OPTIONAL
    !IV_CLIENTTOKEN TYPE /AWS1/S3_CLIENTTOKEN OPTIONAL
  RETURNING
    VALUE(OO_OUTPUT) TYPE REF TO /aws1/cl_s3_renameobjectoutput
  RAISING
    /AWS1/CX_S3_IDEMPOTENCYPRMMI00
    /AWS1/CX_S3_CLIENTEXC
    /AWS1/CX_S3_SERVEREXC
    /AWS1/CX_RT_TECHNICAL_GENERIC
    /AWS1/CX_RT_SERVICE_GENERIC.

IMPORTING

Required arguments:

iv_bucket TYPE /AWS1/S3_BUCKETNAME /AWS1/S3_BUCKETNAME

The bucket name of the directory bucket containing the object.

You must use virtual-hosted-style requests in the format Bucket-name.s3express-zone-id.region-code.amazonaws.com. Path-style requests are not supported. Directory bucket names must be unique in the chosen Availability Zone. Bucket names must follow the format bucket-base-name--zone-id--x-s3 (for example, amzn-s3-demo-bucket--usw2-az1--x-s3). For information about bucket naming restrictions, see Directory bucket naming rules in the Amazon S3 User Guide.

iv_key TYPE /AWS1/S3_OBJECTKEY /AWS1/S3_OBJECTKEY

Key name of the object to rename.

iv_renamesource TYPE /AWS1/S3_RENAMESOURCE /AWS1/S3_RENAMESOURCE

Specifies the source for the rename operation. The value must be URL encoded.

Optional arguments:

iv_destinationifmatch TYPE /AWS1/S3_IFMATCH /AWS1/S3_IFMATCH

Renames the object only if the ETag (entity tag) value provided during the operation matches the ETag of the object in S3. The If-Match header field makes the request method conditional on ETags. If the ETag values do not match, the operation returns a 412 Precondition Failed error.

Expects the ETag value as a string.

iv_destinationifnonematch TYPE /AWS1/S3_IFNONEMATCH /AWS1/S3_IFNONEMATCH

Renames the object only if the destination does not already exist in the specified directory bucket. If the object does exist when you send a request with If-None-Match:, the S3 API will return a 412 Precondition Failed error, preventing an overwrite. The If-None-Match header prevents overwrites of existing data by validating that there's not an object with the same key name already in your directory bucket.

Expects the character (asterisk).

iv_dstifmodifiedsince TYPE /AWS1/S3_IFMODIFIEDSINCE /AWS1/S3_IFMODIFIEDSINCE

Renames the object if the destination exists and if it has been modified since the specified time.

iv_dstifunmodifiedsince TYPE /AWS1/S3_IFUNMODIFIEDSINCE /AWS1/S3_IFUNMODIFIEDSINCE

Renames the object if it hasn't been modified since the specified time.

iv_sourceifmatch TYPE /AWS1/S3_RENAMESOURCEIFMATCH /AWS1/S3_RENAMESOURCEIFMATCH

Renames the object if the source exists and if its entity tag (ETag) matches the specified ETag.

iv_sourceifnonematch TYPE /AWS1/S3_RENAMESRCIFNONEMATCH /AWS1/S3_RENAMESRCIFNONEMATCH

Renames the object if the source exists and if its entity tag (ETag) is different than the specified ETag. If an asterisk (*) character is provided, the operation will fail and return a 412 Precondition Failed error.

iv_sourceifmodifiedsince TYPE /AWS1/S3_RENAMESRCIFMODSINCE /AWS1/S3_RENAMESRCIFMODSINCE

Renames the object if the source exists and if it has been modified since the specified time.

iv_sourceifunmodifiedsince TYPE /AWS1/S3_RENAMESRCIFUNMODSINCE /AWS1/S3_RENAMESRCIFUNMODSINCE

Renames the object if the source exists and hasn't been modified since the specified time.

iv_clienttoken TYPE /AWS1/S3_CLIENTTOKEN /AWS1/S3_CLIENTTOKEN

A unique string with a max of 64 ASCII characters in the ASCII range of 33 - 126.

RenameObject supports idempotency using a client token. To make an idempotent API request using RenameObject, specify a client token in the request. You should not reuse the same client token for other API requests. If you retry a request that completed successfully using the same client token and the same parameters, the retry succeeds without performing any further actions. If you retry a successful request using the same client token, but one or more of the parameters are different, the retry fails and an IdempotentParameterMismatch error is returned.

RETURNING

oo_output TYPE REF TO /aws1/cl_s3_renameobjectoutput /AWS1/CL_S3_RENAMEOBJECTOUTPUT

Domain /AWS1/RT_ACCOUNT_ID
Primitive Type NUMC

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.

DATA(lo_result) = lo_client->renameobject(
  iv_bucket = |string|
  iv_clienttoken = |string|
  iv_destinationifmatch = |string|
  iv_destinationifnonematch = |string|
  iv_dstifmodifiedsince = '20150101000000.0000000'
  iv_dstifunmodifiedsince = '20150101000000.0000000'
  iv_key = |string|
  iv_renamesource = |string|
  iv_sourceifmatch = |string|
  iv_sourceifmodifiedsince = '20150101000000.0000000'
  iv_sourceifnonematch = |string|
  iv_sourceifunmodifiedsince = '20150101000000.0000000'
).

This is an example of reading all possible response values

lo_result = lo_result.
IF lo_result IS NOT INITIAL.
ENDIF.