Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions,
see Getting Started with Amazon Web Services in China
(PDF).
Upload an object to an S3 on Outposts
bucket
Objects are the fundamental entities stored in Amazon S3 on Outposts. Every object is contained in a bucket.
You must use access points to access any object in an Outpost bucket. When you specify the bucket for object operations, you use the
access point Amazon Resource Name (ARN) or the access point alias. For more information about access point aliases, see Using a bucket-style alias for your
S3 on Outposts bucket access point.
The following example shows the
ARN format for S3 on Outposts access points, which includes the Amazon Web Services Region code for the Region that the Outpost is homed to, the Amazon Web Services account ID,
the Outpost ID, and the access point name:
arn:aws-cn:s3-outposts:region
:account-id
:outpost/outpost-id
/accesspoint/accesspoint-name
For more information about S3 on Outposts ARNs, see Resource ARNs for S3 on Outposts.
With Amazon S3 on Outposts, object data is always stored on the Outpost. When Amazon installs an Outpost rack, your data stays local to
your Outpost to meet data-residency requirements. Your objects never leave your
Outpost and are not in an Amazon Web Services Region. Because the Amazon Web Services Management Console is hosted in-Region, you can't use the console to upload or manage objects in
your Outpost. However, you can use the REST API, Amazon Command Line Interface (Amazon CLI), and Amazon SDKs to upload and manage your objects through your access points.
The following Amazon CLI and Amazon SDK for Java examples show you how to upload an object to an
S3 on Outposts bucket by using an access point.
- Amazon CLI
-
The following example puts an object named sample-object.xml
into
an S3 on Outposts bucket (s3-outposts:PutObject
) by using the Amazon CLI. To use this
command, replace each user input placeholder
with
your own information. For more information about this command, see put-object in the Amazon CLI Reference.
aws s3api put-object --bucket arn:aws-cn:s3-outposts:Region
:123456789012
:outpost/op-01ac5d28a6a232904
/accesspoint/example-outposts-access-point
--key sample-object.xml
--body sample-object.xml
- SDK for Java
-
The following example puts an object into an S3 on Outposts bucket by using the SDK for Java.
To use this example, replace each user input
placeholder
with your own information.
import com.amazonaws.AmazonServiceException;
import com.amazonaws.SdkClientException;
import com.amazonaws.services.s3.AmazonS3;
import com.amazonaws.services.s3.AmazonS3ClientBuilder;
import com.amazonaws.services.s3.model.ObjectMetadata;
import com.amazonaws.services.s3.model.PutObjectRequest;
import java.io.File;
public class PutObject {
public static void main(String[] args) {
String accessPointArn = "*** access point ARN ***";
String stringObjKeyName = "*** String object key name ***
";
String fileObjKeyName = "*** File object key name ***
";
String fileName = "*** Path to file to upload ***
";
try {
// This code expects that you have Amazon credentials set up per:
// https://docs.amazonaws.cn/sdk-for-java/v1/developer-guide/setup-credentials.html
AmazonS3 s3Client = AmazonS3ClientBuilder.standard()
.enableUseArnRegion()
.build();
// Upload a text string as a new object.
s3Client.putObject(accessPointArn, stringObjKeyName, "Uploaded String Object");
// Upload a file as a new object with ContentType and title specified.
PutObjectRequest request = new PutObjectRequest(accessPointArn, fileObjKeyName, new File(fileName));
ObjectMetadata metadata = new ObjectMetadata();
metadata.setContentType("plain/text");
metadata.addUserMetadata("title", "someTitle");
request.setMetadata(metadata);
s3Client.putObject(request);
} catch (AmazonServiceException e) {
// The call was transmitted successfully, but Amazon S3 couldn't process
// it, so it returned an error response.
e.printStackTrace();
} catch (SdkClientException e) {
// Amazon S3 couldn't be contacted for a response, or the client
// couldn't parse the response from Amazon S3.
e.printStackTrace();
}
}
}