LIBSAFE Flexible Intake
  • What is Flexible Intake
  • Flexible Intake Benefits
  • CONCEPTS
    • Overview
    • Organize your content
    • OAIS and ISO 16363
      • Understanding OAIS and ISO 16363
      • Flexible Intake support for OAIS Conformance
      • Planning for preservation
      • ISO 16363 certification guide
  • GET STARTED
    • Create a data container
    • Upload content
    • Download content
    • Introduction to metadata
    • Search
    • File versioning and recovery
    • Work with data containers
    • Functions
    • Storage mode transitions
    • Jupyter Notebooks
  • CONFIGURATION
    • Archive organization
    • Container templates
    • Configure metadata
    • Users and Permissions
  • REPORTS
    • Introduction
    • Data Analytics Reports
    • Container Tab Reports
  • DEVELOPER'S GUIDE
    • Functions
    • Using the API
    • Functions gallery
  • COOKBOOK
    • AWS CLI with Flexible Intake
    • Using S3 Browser
    • Using FileZilla Pro
    • Getting your S3 bucket name
    • Getting your S3 storage credentials
    • Advanced API File Search
    • Tips for faster uploads
    • Configuring Azure SAML-based authentication
    • Create a manifest before transferring files
  • File Browser
    • Supported formats for preview
    • Known issues and limitations
    • Changelog and Release Notes
Powered by GitBook
On this page
  • Using the Management Interface
  • Using the API

Was this helpful?

  1. COOKBOOK

Getting your S3 storage credentials

PreviousGetting your S3 bucket nameNextAdvanced API File Search

Last updated 3 years ago

Was this helpful?

Using the Management Interface

  1. Sign in to the Flexible Intake Management Interface

  2. Click on your name and select Access Methods

  3. In the S3 compatible protocol section, click Regenerate

  4. Copy your Access Keys and Secret Keys and store them in a safe location. Note that more than one set of credentials may exist.

Please note that the Secret Key will only be displayed once. It is possible to regenerate a key, but the old key will be invalidated and any process that uses it will receive an "access denied" error.

Using the API

  1. Use the following method to retrieve your credentials:

curl --request GET \
      --url "$your_platform_url/api/user/internal/access_methods" \
      --header "authorization: Bearer $your_platform_api_key"