ALinkServer by Sol4Cloud is a fully containerized implementation of the SAP ArchiveLink 4.6 interface, purpose-built for archiving data and documents from SAP ECC and S/4HANA systems directly to your own Amazon S3 buckets. Unlike traditional SAP content servers that require dedicated infrastructure, complex licensing, and vendor-managed storage, ALinkServer runs entirely within your AWS account using cloud-native services.
Key Benefits
- Data sovereignty - All archived documents remain in your own S3 buckets. No data leaves your AWS account or passes through third-party storage.
- Pay-per-use model - No upfront license fees or content server hardware. You are charged only for the number of requests processed.
- Minimal infrastructure - Uses a single DynamoDB table for application and SAP repository configuration. No databases to manage, no file systems to provision.
- Simple deployment - Deploy on Amazon ECS using either Fargate or EC2 launch types.
Architecture and AWS Integration
ALinkServer leverages the following AWS services within your account:
- Amazon S3 - Primary storage for all archived SAP documents and data
- Amazon DynamoDB - Stores application configuration and SAP content repository definitions
- AWS Secrets Manager - Manages credentials and sensitive configuration securely
- Amazon CloudWatch - Provides logging and monitoring for operational visibility
- Amazon ECS - Runs the ALinkServer container on Fargate (serverless) or EC2 infrastructure
Security
Because ALinkServer operates entirely within your AWS account, you retain full control over encryption, access policies, and network configuration. Documents stored in S3 can be encrypted at rest using S3 server-side encryption (SSE-S3 or SSE-KMS with your own keys). All communication between SAP and ALinkServer can be secured with TLS. IAM policies control access to S3 buckets, DynamoDB tables, and Secrets Manager entries, enabling least-privilege configurations aligned with your organization's security standards.
Deployment
ALinkServer is deployed as a container image on Amazon ECS. The deployment involves configuring an ECS task definition, setting up the DynamoDB configuration table, creating S3 buckets for document storage, and configuring SAP content repositories (transaction OAC0) to point to your ALinkServer endpoint. The solution supports multi-system landscapes (DEV, QA, PRD) through separate content repository configurations.
Getting Started
Subscribe through AWS Marketplace to begin. See the ALinkServer documentation providing details about ALinkServer deployment and initial configuration.
