Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

You can use the Threat Analytics Manager to connect to Amazon S3 storage with Datasiftthe Twitter Search API.

Using the wizard, it is easy to input your credentials and Amazon s3 storage bucketadd you Twitter API access token and secret, as well as a list of Twitter accounts to query against.

Connecting to the Web Page

To connect to the Datasift data at the s3 bucketTwitter Search API

  1. From the Treat Analytics Dashboard, click on Data Sources (top right).
  2. Under "What kind of source would you like to create?" specify "Datasift from S3Twitter Search API."
  3. Click on Next.
  4. Specify the the fields as defined in the table below

    FieldDescriptionNote
    Username"Access Key ID" for Amazon s3 bucketAPI Consumer KeyAPI Key associated with the registered Twitter application. eg. L8qq9PZyRg6ieKGEKhZolGC0vJWLw8iEJ88DRdyOg Note: Will not work on real requests. Password
    API Secret"Secret Access Key" for Amazon s3 bucketSecret Key that corresponds to the Consumer Key for the Twitter registration. L8qq9PZyRg6ieKGEKhZolGC0vJWLw8iEJ88DRdyOg Note: Will not work on real requests. 
    File locationMust include a / at the end of the path. eg. s3://nsight.ikanow.com/africa/nigeria/Twitter Accounts to HarvestTwitter account names to harvest eg. @andrewjtech 



  5. Click on Next.

Configuring and Testing

Once you have made the input settings, you will need to perform additional configuration and testing.

To configure and test

  1. Provide a name for the source.
  2. Select the previously created Data Group.
  3. Select the Media Type.
  4. Specify the frequency at which the source should be harvested (eg. Once per day).Review cost information.
  5. Click on Test Source.

About

Cost

Yahoo Search is a paid API service.  You should review and understand your daily cost before proceeding.

About Testing

If the source has been configured properly testing with return test results, and you will be able to move forward with Publishing the new source.  Otherwise, a failure message is generated which can be used for troubleshooting (currently it only says FAIL).  You can always Save your source and come back to fix any testing errors later.

Saving or Publishing

Saving 

To save the source after testing

  • Click on Save.

The source is saved and you are re-directed to the Source Manager.

Publishing

To publish the source after testing

  • Click on Publish.

The source is published and you are re-directed to the list Source Manager.

Panel

In this section:

Panel

Related Documentation: