Access Data on S3
Amazon S3 is not supported as a default file system, but access to data in Amazon S3 is possible via the s3a connector.
To use S3 storage, you must have one or more S3 buckets on your AWS account. For instructions on how to create a bucket on S3, refer to AWS documentation.
Create a Bucket (External)
Creating an IAM Role for S3 Access
In order to configure access from your cluster to Amazon S3, you must have an existing IAM role which determines what actions can be performed on which S3 buckets. If you do not have an existing IAM role, use these steps to create one.
Navigate to the IAM console > Roles and click Create Role.
In the "Create Role" wizard, select AWS service role type and then select EC2 service and EC2 use case.
When done, click Next: Permissions to navigate to the next page in the wizard.
Select an existing S3 access policy or click Create policy to define a new policy. If you are just getting started, you can select a built-in policy called "AmazonS3FullAccess", which provides full access to S3 buckets that are part of your account:
When done attaching the policy, click Next: Review.
In the Roles name field, enter a name for the role that you are creating:
Click Create role to finish the role creation process.
Configuring Access to S3
Amazon S3 is not supported as a default file system, but access to data in S3 from your cluster VMs can be automatically configured by attaching an instance profile allowing access to S3. You can optionally create or attach an existing instance profile during cluster creation on the File System page.
To configure access to S3 with an instance profile, follow these steps.
- You or your AWS admin must create an IAM role with an S3 access policy which can be used by cluster instances to access one or more S3 buckets. Refer to Creating an IAM Role for S3 Access.
- On the File System page in the advanced cluster wizard view, select Use existing instance profile.
Select an existing IAM role created in step 1:
During the cluster creation process, Cloudbreak assigns the IAM role and its associated permissions to the EC2 instances that are part of the cluster so that applications running on these instances can use the role to access S3.
Testing Access to S3
To tests access to S3, SSH to a cluster node and run a few hadoop fs shell commands against your existing S3 bucket.
Amazon S3 access path syntax is:
For example, to access a file called "mytestfile" in a directory called "mytestdir", which is stored in a bucket called "mytestbucket", the URL is:
The following FileSystem shell commands demonstrate access to a bucket named "mytestbucket":
hadoop fs -ls s3a://mytestbucket/ hadoop fs -mkdir s3a://mytestbucket/testDir hadoop fs -put testFile s3a://mytestbucket/testFile hadoop fs -cat s3a://mytestbucket/testFile test file content
Working with S3
For more information about configuring the S3 connector and working with data stored on S3, refer to Cloud Data Access documentation.
Cloud Data Access (Hortonworks)