Amazon S3 Features

-

Amazon S3 Features

Topics
This section describes important Amazon S3 features.

Storage Classes

Amazon S3 offers a range of storage classes designed for different use cases. These include Amazon S3 STANDARD for general-purpose storage of frequently accessed data, Amazon S3 STANDARD_IA for long-lived, but less frequently accessed data, and GLACIER for long-term archive.
For more information, see Storage Classes.

Bucket Policies

Bucket policies provide centralized access control to buckets and objects based on a variety of conditions, including Amazon S3 operations, requesters, resources, and aspects of the request (e.g., IP address). The policies are expressed in our access policy language and enable centralized management of permissions. The permissions attached to a bucket apply to all of the objects in that bucket.
Individuals as well as companies can use bucket policies. When companies register with Amazon S3 they create an account. Thereafter, the company becomes synonymous with the account. Accounts are financially responsible for the Amazon resources they (and their employees) create. Accounts have the power to grant bucket policy permissions and assign employees permissions based on a variety of conditions. For example, an account could create a policy that gives a user write access:
  • To a particular S3 bucket
  • From an account's corporate network
  • During business hours
An account can grant one user limited read and write access, but allow another to create and delete buckets as well. An account could allow several field offices to store their daily reports in a single bucket, allowing each office to write only to a certain set of names (e.g., "Nevada/*" or "Utah/*") and only from the office's IP address range.
Unlike access control lists (described below), which can add (grant) permissions only on individual objects, policies can either add or deny permissions across all (or a subset) of objects within a bucket. With one request an account can set the permissions of any number of objects in a bucket. An account can use wildcards (similar to regular expression operators) on Amazon resource names (ARNs) and other values, so that an account can control access to groups of objects that begin with a common prefix or end with a given extension such as .html.
Only the bucket owner is allowed to associate a policy with a bucket. Policies, written in the access policy language, allow or deny requests based on:
  • Amazon S3 bucket operations (such as PUT ?acl), and object operations (such as PUT Object, or GET Object)
  • Requester
  • Conditions specified in the policy
An account can control access based on specific Amazon S3 operations, such as GetObject, GetObjectVersion, DeleteObject, or DeleteBucket.
The conditions can be such things as IP addresses, IP address ranges in CIDR notation, dates, user agents, HTTP referrer and transports (HTTP and HTTPS).
For more information, see Using Bucket Policies and User Policies.

AWS Identity and Access Management

For example, you can use IAM with Amazon S3 to control the type of access a user or group of users has to specific parts of an Amazon S3 bucket your AWS account owns.
For more information about IAM, see the following:

Access Control Lists

For more information, see Managing Access with ACLs

Versioning

For more information, see Object Versioning.

Operations

Following are the most common operations you'll execute through the API.
Common Operations
  • Create a Bucket – Create and name your own bucket in which to store your objects.
  • Write an Object – Store data by creating or overwriting an object. When you write an object, you specify a unique key in the namespace of your bucket. This is also a good time to specify any access control you want on the object.
  • Read an Object – Read data back. You can download the data via HTTP or BitTorrent.
  • Deleting an Object – Delete some of your data.
  • Listing Keys – List the keys contained in one of your buckets. You can filter the key list based on a prefix.
Details on this and all other functionality are described in detail later in this guide.

Amazon S3 Application Programming Interfaces (API)

The Amazon S3 architecture is designed to be programming language-neutral, using our supported interfaces to store and retrieve objects.
Amazon S3 provides a REST and a SOAP interface. They are similar, but there are some differences. For example, in the REST interface, metadata is returned in HTTP headers. Because we only support HTTP requests of up to 4 KB (not including the body), the amount of metadata you can supply is restricted.
Note
SOAP support over HTTP is deprecated, but it is still available over HTTPS. New Amazon S3 features will not be supported for SOAP. We recommend that you use either the REST API or the AWS SDKs.

The REST Interface

The REST API is an HTTP interface to Amazon S3. Using REST, you use standard HTTP requests to create, fetch, and delete buckets and objects.
You can use any toolkit that supports HTTP to use the REST API. You can even use a browser to fetch objects, as long as they are anonymously readable.
The REST API uses the standard HTTP headers and status codes, so that standard browsers and toolkits work as expected. In some areas, we have added functionality to HTTP (for example, we added headers to support access control). In these cases, we have done our best to add the new functionality in a way that matched the style of standard HTTP usage.

The SOAP Interface

Note
SOAP support over HTTP is deprecated, but it is still available over HTTPS. New Amazon S3 features will not be supported for SOAP. We recommend that you use either the REST API or the AWS SDKs.
The SOAP API provides a SOAP 1.1 interface using document literal encoding. The most common way to use SOAP is to download the WSDL (go to http://doc.s3.amazonaws.com/2006-03-01/AmazonS3.wsdl), use a SOAP toolkit such as Apache Axis or Microsoft .NET to create bindings, and then write code that uses the bindings to call Amazon S3.

Paying for Amazon S3

Pricing for Amazon S3 is designed so that you don't have to plan for the storage requirements of your application. Most storage providers force you to purchase a predetermined amount of storage and network transfer capacity: If you exceed that capacity, your service is shut off or you are charged high overage fees. If you do not exceed that capacity, you pay as though you used it all.
Amazon S3 charges you only for what you actually use, with no hidden fees and no overage charges. This gives developers a variable-cost service that can grow with their business while enjoying the cost advantages of Amazon's infrastructure.
Before storing anything in Amazon S3, you need to register with the service and provide a payment instrument that will be charged at the end of each month. There are no set-up fees to begin using the service. At the end of the month, your payment instrument is automatically charged for that month's usage.

Comments

Post a Comment

Popular posts from this blog

Styling Bottom Navigation

-
Image
Styling Bottom Navigation Off the bat, the library provides considerable styling options. But after recent updates, there has been a lot more. Some of these additions include notification badges and coordinating behaviors. It also includes  on-scroll Quick Return pattern . Its all that one could ever want with the Bottom Navigation. This library is much more feature-rich than  what Android Design Support Library offers . So if you want more customization options and more control, you know what to use. Before we get to that, here’s a heads-up. We’ll be using and referencing a lot of colors. Normally, we reference colors in Android like this: ContextCompat.getColor(context, R.id.yourcolor); Now I’m no fan of writing such a lengthy line for fetching a simple color resource. So I’ll write a simple method that shortens what I have to type. private int fetchColor( @ColorRes int color) { return ContextCompat.getColor(this, color); } Great! From now on I don’t have
Read more

Lottie Animation in Android

-
Gradle is the only supported build configuration, so just add the dependency to your project  build.gradle  file: dependencies { ... compile 'com.airbnb.android:lottie:2.2.5' ... } Lottie supports ICS (API 14) and above. The simplest way to use it is with LottieAnimationView: <com.airbnb.lottie.LottieAnimationView android:id="@+id/animation_view" android:layout_width="wrap_content" android:layout_height="wrap_content" app:lottie_fileName="hello-world.json" app:lottie_loop="true" app:lottie_autoPlay="true" /> Or you can load it programmatically in multiple ways. From a json asset in app/src/main/assets: LottieAnimationView animationView = ( LottieAnimationView ) findViewById ( R . id . animation_view ) ; animationView . setAnimation ( "hello-world.json" ) ; animationView . loop ( true ) ; animationView . playAnimation ( ) ;
Read more

Set Up the AWS Mobile SDK for Android

-
Prerequisites # Before you can use the AWS Mobile SDK for Android, you will need the following: An  AWS Account Android 2.3.3 (API Level 10) or higher (for more information about the Android platform, see  Android Developers ) Android Studio  or  Android Development Tools for Eclipse After completing the prerequisites, you will need to do the following to get started: Get the AWS Mobile SDK for Android. Set permissions in your  AndroidManifest.xml  file. Obtain AWS credentials using Amazon Cognito. Step 1: Get the AWS Mobile SDK for Android There are three ways to get the AWS Mobile SDK for Android. Option 1: Using Gradle with Android Studio # If you are using Android Studio, add the  aws-android-sdk-core  dependency to your app/build.gradle  file, along with the dependencies for the individual services that your project will use, as shown below. dependencies { compile 'com.amazonaws:aws-android-sdk-core:2.2.+' compile 'com.
Read more