Fire Insights allows you to access your files on S3. This page describes S3 integration when Fire Insights is running in standalone mode.
We recommend controlling access to S3 using IAM Roles. Run the EMR cluster with the appropriate S3 IAM Role.
If you are running Fire Insights on a independent machine, you can also use
aws configure to set the AWS Access Key and Secret Access Key on the machine.
Installing aws cli¶
- pip install awscli –upgrade –user
Configuring AWS access key and password¶
aws configure to configure your credentials on the machine on which Fire Insights is running.
Access S3 in fire-ui¶
In Fire Insights, you can browse S3 under the menu Browser/S3.
- Click on AWS s3 then we will get File available in it.
Protecting Data Using Server Side Encryption¶
Data encryption settings on S3 buckets: https://docs.aws.amazon.com/AmazonS3/latest/dev/serv-side-encryption.html
REFERENCE : Creating Access Key & Secret Key¶
- You’ll need create a user with programmatic access by following the steps here (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_users_create.html).
- Next, you’ll create an IAM policy that defines what this user has access to in your AWS account. It’s important to only grant this user minimal access within your account. See this documentation for how to create IAM policies (https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html).
- Finally, you’ll create an access key and secret key for this user (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey).
Note It’s important to regularly rotate your access and secret keys. See this documentation for more information (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#rotating_access_keys_console)