AWS Client Stack Deployment

Note: The information on this page applies to Content Mover and Business Continuity.

CAM AWS Stack utilizes Amazon AWS services and resources to provide the ability to move documents and content and sync metadata between multiple Document Management Systems (DMS). CAM Content Mover and Data Sync (Content Sync) use S3 storage blobs as an intermediary place while moving content between the supported Document Management Systems.

To deploy the CAM AWS Stack, you need to deploy the AWS template into your environment. The template deploys a complete solution that contains multiple resources such as function apps, MySQL instances, Blob Storages, and others. These resources are provided and hosted by AWS in your AWS account to provide more control over moving content.

AWS Stack Creation

Create SQS Queues

Create 2 SQS queues manually as follows:

content sync-prod-job-process-v1

Description

Description
Standard Queue
Receive Message Wait Time: 0 seconds
Message Retention Period: 14 days
Maximum Message Size: 256 (kB)
Don't use redrive policy
Don't use SSE (Server-Side Encryption)
Delivery Delay: 0 seconds
Default Visibility Timeout: 16 minutes

2. contentsync-prod-etl-process-v1

Description

Description
Standard Queue
Receive Message Wait Time: 0 seconds
Message Retention Period: 14 days
Maximum Message Size: 256 (kB)
Don't use redrive policy
Don't use SSE (Server-Side Encryption)
Delivery Delay: 0 seconds
Default Visibility Timeout: 16 minutes

Create S3 Buckets

Create 2 buckets manually:

content-sync-configuration-$subdomain - This bucket will use to share the AWS setup script to the user.

$subdomain-prosperoware-io-encrypted-bucket - This bucket will use to store the client's content. Set default encryption to AES-256

Note: $subdomain Specify your subdomain name.

Create the VPC

Litera will share the scripts to create VPC.
Download the scripts will be available at content-sync-configuration-$subdomain/vpc-configuration/.
Configure AWS CLI. Follow instructions provided at AWS: AWS CLI.
Execute below command on the terminal to create VPC:
sh deploy.script create-stack --region us-east-1

Note: --region Specify which AWS Region to send this command's AWS request to.

Create the Lambda Security Group

Head over to VPC
Under Security Group click Create Security Group:

Set the security group name to Lambda-SG
Select the VPC created from the previous step.
Add a rule for inbound and outbound as All Trafic and Source 0.0.0.0/0 or Destination as 0.0.0.0/0

Upload the shared content to the S3 bucket

Update the below 2 files

Open params-prod.yml available at S3Content/serverless/params/us-east-1
- LambdaRole (update the AWSACCOUNTID to your AWSACCOUNTID)
- SecurityGroup (Lambda-SG created in the previous step)
- SubnetIds (please update the SubnetIds to the private subnet IDs of the VPC created earlier)
- ContentSyncJobProcessQueue (update the AWSACCOUNTID value to your AWSACCOUNTID)
Open appconfig-prod.yml available at S3Content/config/ymls
- CS_JOB_QUEUE (Update the AWSACCOUNTID value to your AWSACCOUNTID
Upload these files in S3 bucket content-sync-configuration-$subdomain

Stack Updates

Upgrades to the stack consist of these steps:

AWS at Client Security Configuration and Validation

Configure Content Mover (ETL) within CAM

Click here for details how to proceed updating the Content Mover sync in CAM using the new stack.

Download A Document with Business Continuity

Login as the BC user.
Go to Documents tab.
Search for a document.

4. Open the resulting document. Click the download icon in the details.