|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
Before you can upload data into Amazon S3, you must create a bucket to store the data in. Buckets have configuration properties, including their geographical region, who has access to the objects in the bucket, and other metadata, such as the storage class of the objects in the bucket.
The console enables you to use folders, which you can store objects in. Folders, like objects, must reside in a bucket. For more information about using folders, see Working With Folders.
Use the following procedure to create a bucket.
You are not charged for creating a bucket; you are only charged for storing objects in the bucket and for transferring objects out of the bucket.
To create a bucket
Sign into the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3.
Click Create Bucket.
In the Create Bucket dialog box, in the Bucket Name box, type a name for your bucket.
The name that you choose must be unique across all existing bucket names in Amazon S3. One way to help ensure uniqueness is to prefix your bucket names with the name of your organization.
The bucket name is visible in the URL that points to the objects that you're going to put in your bucket. For that reason, choose a bucket name that reflects the objects in the bucket.
Bucket names must comply with the following requirements.
Can contain lowercase letters, numbers, periods (.), underscores (_), and dashes (-).
Must start with a number or letter.
Must be between 3 and 255 characters long.
Must not be formatted as an IP address (e.g., 192.168.5.4) .
To conform with DNS requirements, we recommend the following, additional guidelines when creating bucket names. Bucket names:
Should not contain underscores (_)
Should be between 3 and 63 characters long
Should not end with a dash
Cannot contain two, adjacent periods
Cannot contain dashes next to periods (e.g.,
my.-bucket are invalid)
If you want to use your S3 bucket as an origin for an Amazon CloudFront
distribution, the requirements for naming S3 buckets are more restrictive.
For more information, see the
DNSName element in the "S3Origin
Child Elements" table in the DistributionConfig Complex Type section of the
Amazon CloudFront API Reference.
To take advantage of Amazon S3's CNAME support, you should name your bucket
the same as your website's base address (e.g.
www.mysite.com). For more information about CNAME, go
to Virtual Hosting in the Amazon S3 Developer Guide.
Once you create a bucket, you cannot change the name of it. Make sure the bucket name you choose is appropriate.
In the Region box, click the region where you want the bucket to reside.
You should choose a region close to you to optimize latency, minimize costs, or to address regulatory requirements. Objects stored in a region never leave that region unless you explicitly transfer them to another region. For more information about regions, see Regions.
In the next step, you have the opportunity to set up logging. Server access logging provides detailed records for the requests made against your bucket. An access log record contains details about the request, such as the request type, the resources specified in the request worked, and the time and date the request was processed. Server access logs are useful for many applications because they give bucket owners insight into the nature of requests made by clients not under their control. Amazon S3 delivers access logs to your bucket. By default, Amazon S3 does not collect server access logs.
Do one of the following.
|Create a bucket without setting up logging||Click Create|
|Set up server access logging for the bucket you're creating||Click Set Up Logging|
There is no extra charge for enabling server access logging on an Amazon S3 bucket. However, any log files the system delivers to you will accrue the usual charges for storage. (You can delete log files at any time.) We do not assess data transfer charges for delivering log files to your bucket, but we do charge the normal data transfer rate for accessing the log files. For more information, go to Amazon S3 Pricing.
If you clicked Set Up Logging in the Create a Bucket - Set Up Logging dialog box, do the following:
Select the Enabled check box.
In the Target Bucket box, select the bucket where you want the log files stored.
(Optional In Target Prefix box, specify a prefix for the name of the log files.
Amazon S3 adds the prefix to the log file names when storing them in
your bucket. For example, if you specify the prefix "logs/," all logs
stored in the target bucket are prefixed with
logs/, so, all the logs will be stored in the
If Amazon S3 successfully creates your bucket, the console displays your empty bucket.