Before you begin, make sure that you have completed the following prerequisites.
In Dropbox, make sure you have:
-
Created a Dropbox Advanced account and set up an admin user.
-
Created a Dropbox app with a unique App name, activated Scoped Access. For more information, see Dropbox documentation on creating an app
on the Dropbox website. -
Activated Full Dropbox permissions on the Dropbox console and added the following permissions:
-
files.content.read -
files.metadata.read -
sharing.read -
file_requests.read -
groups.read -
team_info.read -
team_data.content.read -
team_data_member
-
-
Noted your Dropbox app key, Dropbox app secret, and Dropbox access token for basic authentication credentials.
-
Generated and copied a temporary Oauth 2.0 access token for your Dropbox app. This token is temporary and expires after 4 hours. For more information, see Dropbox documentation on OAuth authentication
on the Dropbox website.
In your AWS account, make sure you have:
-
Created a Amazon Q Business application.
-
Created an IAM role for your data source and, if using the Amazon Q API, noted the ARN of the IAM role.
-
Stored your Dropbox authentication credentials in an AWS Secrets Manager secret and, if using the Amazon Q API, noted the ARN of the secret.
Note
If you’re a console user, you can create the IAM role and Secrets Manager secret as part of configuring your Amazon Q application on the console.
For a list of things to consider while configuring your data source, see Data source connector configuration best practices.
