Using AWS OpenSearch With Serverless Alfresco Content Services

This repository contains files that accompany an AWS Partner Network (APN) blog of the same title.

The blog written in collaboration with Hyland, seeks to demonstrate a deployment of Alfresco Content Services (ACS) 7.3 on Amazon Elastic Kubernetes Service (Amazon EKS) using AWS Fargate as the serverless compute engine. Amazon OpenSearch Service is used to provide Elasticsearch services to Alfresco Search Enterprise 3.2.

Note that the AWS account used for deployment should be provided, at minimum, with the IAM policies listed in eksctl's Minimum IAM policies page.

The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Fargate or using Amazon Elastic File System (Amazon EFS) storage.

Update

Since the publishing of the blog on APN, enhancements has been made to the deployment to enable sticky sessions. The generated template should be updated with the following snippets before step 10 of the APN blog.

1. Sticky session on the Application Load Balancer is configured with the alb.ingress.kubernetes.io/target-group-attributes annotation in Ingress snippet file. The need for sticky sessions is prescribed in Hyland's configuration document for Alfresco Content Services.
2. Sticky session within the k8s cluster for the repository pod is configured with the spec.sessionAffinity=ClientIP directive in repository Service snippet file. The need for sticky sessions is prescribed in Hyland's configuration document for Alfresco Share.