Cloud Storage Security Help Docs
Release Notes
  • Introduction
  • Getting Started
    • How to Subscribe
      • Pay-As-You-Go (PAYG)
      • Bring Your Own License/GovCloud (BYOL)
      • AWS Transfer Family
    • How to Deploy
      • Steps to Deploy
      • Advanced Deployment Considerations
      • AWS Transfer Family
    • How to Configure
  • Console Overview
    • Dashboard
    • Malware Scanning
      • AWS
        • Buckets
        • Amazon EBS Volumes
        • Amazon EFS Volumes
        • Amazon FSx Volumes
        • WorkDocs Connections
      • Azure
        • Blob Containers
      • GCP
        • GCP Buckets
    • See What's Infected
      • Findings
      • Malware History
      • Results
    • Schedules
    • Monitoring
      • Error Logs
      • Bucket Settings
      • Deployment
      • Jobs
      • Notifications
      • Storage Assessment
      • Usage
    • Configuration
      • Classification Rule Sets
      • Classification Custom Rules
      • Scan Settings
      • Console Settings
      • AWS Integrations
      • Job Networking
      • API Agent Settings
      • Proactive Notifications
      • License Management
      • Event Agent Settings
    • Access Management
      • Manage Users
      • Manage Accounts
        • Linking an AWS Account
        • Linking an Azure Account
        • Linking a GCP Account
      • Manage Groups
    • Support
      • Getting Started
      • Stay Connected
      • Contact Us
      • Documentation
  • Product Updates
  • How It Works
    • Scanning Overview
      • Event Driven Scanning for New Files
      • Retro Scanning for Pre-Existing Files
      • API Driven Scanning
    • Architecture Overview
    • Deployment Details
    • Sizing Discussion
    • Integrations
      • AWS Security Hub
      • AWS CloudTrail Lake
      • AWS Transfer Family
      • Amazon GuardDuty
      • Amazon Bedrock
    • Demo Videos
    • Scanning APIs
    • SSO Integrations
      • Entra ID SSO Integration
      • Okta SSO Integration
  • Frequently Asked Questions
    • Getting Started
    • Product Functionality
    • Architecture Related
    • Supported File Types
  • Troubleshooting
    • CloudFormation Stack failures
    • Cross-Region Scanning on with private network
    • API Scanning: Could not connect to SSL/TLS (v7)
    • Password not received after deployment
    • Conflicted buckets
    • Modifying scaling info post-deployment
    • Objects show unscannable with access denied
    • Remote account objects not scanning
    • My scanning agents keep starting up and immediately shutting down
    • I cannot access the management console
    • Linked Account Out of Date
    • Rebooting the Management Console
    • Error when upgrading to the latest major version
    • I Cannot Create/Delete an API Agent
  • Release Notes
    • Latest (v8)
    • v7
    • v6 and older
  • Contact Us & Support
  • Data Processing Agreement
  • Privacy Policy
Powered by GitBook
On this page
  • Authorize the console role to add subscriptions to WorkDocs
  • Create WorkDocs connections
  • Removing WorkDocs connections
  1. Console Overview
  2. Malware Scanning
  3. AWS

WorkDocs Connections

In addition to Amazon S3 buckets, EBS, and EFS scanning we also support the scanning of files uploaded to Amazon WorkDocs.

PreviousAmazon FSx VolumesNextAzure

Last updated 5 months ago

Before you setup a WorkDocs Connection, make sure you have a VPC and 2 subnets set for the region your WorkDocs directory is in. You can learn more about staging regions in the page.

Authorize the console role to add subscriptions to WorkDocs

In the WorkDocs console, select the site, then go to Actions > Manage notifications.

If you don't see our console role ARN in the table, Create a Notification and put in the console ARN from the modal in the Antivirus for Amazon S3 console.

If you overrode our default name in the CloudFormation template the console ARN will be different in the dialog. You'll need to grab the correct ARN from IAM.

Create WorkDocs connections

To create a WorkDocs connection you can select Add Connection.

  1. In the popup dialog, enter the Organization ID you would like to link. This is usually the Directory ID related to this WorkDocs connection in AWS Directory Service.

  2. Choose the Account this WorkDocs organization is in. Finally, Choose the region the WorkDocs organization is in.

  3. Optionally, enter a nickname for this connection (i.e. "Shared Files"). If you do not enter one, it will be set to the Organization ID.

  4. Click the "Create Connection" button.

Removing WorkDocs connections

You must have access to the AWS account that contains the WorkDocs repository and it must already be linked to this application. If you need assistance with linking accounts you can .

Due to a limitation in AWS, currently you cannot remove a WorkDocs connection if it is in a Linked Account. Please if you run into this issue.

learn more here
Contact Us
Event Agent Settings
Click Manage Notifications
New Notification
Add a WorkDocs Connection
Enter the necessary information