Overview
Overview
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 expensive databases and file systems to provision and manage.
- Simple deployment - Deploy on Amazon ECS/EKS 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, working natively with S3 API, avoiding the hidden cost of S3 File Gateway
- 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/EKS - 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.
Use Cases
- SAP data archiving for database reduction - Archive completed fiscal year documents (FI, MM, SD) to reduce SAP database size before or after S/4HANA migration.
- Regulatory compliance - Retain SAP documents in immutable S3 storage with versioning and Object Lock to meet government or industry-specific retention requirements.
- System decommissioning - Archive documents from legacy SAP systems being retired while maintaining retrieval access through S3.
Deployment
ALinkServer is deployed as two container images on Amazon ECS or Amazon EKS. The deployment involves configuring an ECS/EKS task/pod 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. After subscription, deploy your ECS cluster using CloudFormation Stack configuration or deploy to your EKS cluster using provided HELM chart. Configure your SAP system's ArchiveLink content repositories to connect to ALinkServer.
Visit sol4cloud.com to learn more about ALinkServer and Sol4Cloud.
(SAP is a registered trademark of SAP SE in Germany and other countries. Amazon Web Services, AWS, and Amazon S3 are trademarks of Amazon.com, Inc. or its affiliates.)
Highlights
- Eliminates traditional SAP content server infrastructure - ALinkServer replaces dedicated archiving servers with a lightweight container that runs on Amazon ECS or Amazon EKS (Fargate or EC2). No file systems to provision, no content server licenses to purchase, no relational database to maintain, and no vendor-managed storage. Your archived SAP documents are stored directly in your own S3 buckets, giving you full control over data residency, encryption policies, and access permissions.
- True pay-per-use pricing with no upfront investment - Unlike legacy SAP archiving solutions that require perpetual licenses and dedicated hardware, ALinkServer charges only for requests processed. There are no minimum commitments and no storage fees beyond standard S3 rates. This model aligns archiving costs directly with actual usage volume from your SAP ECC or S/4HANA systems.
- Complete data sovereignty within your own AWS account - ALinkServer uses only services running in your AWS account: S3 for document storage, DynamoDB for configuration, Secrets Manager for credentials, and CloudWatch for monitoring. No archived data passes through or is stored in third-party systems. You maintain full ownership of IAM policies, encryption keys, network controls, and retention rules for all archived SAP content.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/unit |
|---|---|---|
ALinkServer processed requests - Tier 1 (0-100K) | Applies to the first 100,000 processed SAP ArchiveLink requests per year in one AWS region | $0.04 |
ALinkServer processed requests - Tier 2 (>100K in region) | Discounted rate for SAP ArchiveLink requests exceeding 100,000 per year in one AWS region | $0.01 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
We do not offer refunds.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Only containers - custom deployment
- Amazon EKS
- Amazon ECS
Container image
Containers are lightweight, portable execution environments that wrap server application software in a filesystem that includes everything it needs to run. Container applications run on supported container runtimes and orchestration services, such as Amazon Elastic Container Service (Amazon ECS) or Amazon Elastic Kubernetes Service (Amazon EKS). Both eliminate the need for you to install and operate your own container orchestration software by managing and scheduling containers on a scalable cluster of virtual machines.
Version release notes
Changed CloudFormation template to custom "least privilege" policy instead of previously used AWS "Full" policies
Additional details
Usage instructions
Quick Start & Installation Guide
1. Custom Deployment Overview
Note: This guide assumes that you've purchased ALinkServer on AWS Marketplace and you're starting the installation. For a detailed architecture and a step-by-step deployment and configuration guide, refer to the documentation linked in the Deployment templates section or go to ALinkServer documentation .
High level "container only" instructions:
- Provision Compute Cluster: Create an Amazon ECS or EKS cluster.
- Configure Networking: Set up NAT Gateways or VPC Endpoints to secure AWS API traffic within your VPC (CloudFormation template for VPC edpoints can be downloaded from the Deployment Templates link on the right).
- Configure Containers: Set up your ECS Task Definitions or EKS Pods using the following image URIs:
- Admin UI: 709825985650.dkr.ecr.us-east-1.amazonaws.com/sol4cloud/sol4cloud-alinkserveradmin:1.0.10
- Worker: 709825985650.dkr.ecr.us-east-1.amazonaws.com/sol4cloud/sol4cloud-alinkserver:1.0.10 Note: Make sure that both running tasks/images have access to AWS region and AWS account details. E.g. by setting AWS_REGION and AWS_DEFAULT_REGION environment variables and letting AWS libraries fetch user details automatically.
- Attach IAM Policies: Ensure the IAM Task Role / Pod Execution Role includes these AWS managed policies or see "least privilege" custom policy in our CloudFormation template:
- AWSMarketplaceMeteringFullAccess
- AWSMarketplaceMeteringRegisterUsage
- AWSLicenseManagerConsumptionPolicy
- AmazonDynamoDBFullAccess_v2
- AmazonS3FullAccess
- SecretsManagerReadWrite
- Set Resource Sizing & Scaling:
- Admin Server: Assign 1 vCPU and 2 GB RAM. Limit execution to strictly 1 replica (active/standalone).
- Worker Servers: Assign 4 vCPUs and at least 8 GB RAM. Scale horizontally based on traffic demands.
- Network Connectivity: Ensure worker pods/tasks can reach the admin server over the internal network (used by workers to pull runtime configurations).
2. Configure ALinkServer Admin UI
- Start the alinkserveradmin service in your cluster and wait ~2 minutes for container initialization.
- Access the Admin Server via your Application Load Balancer:
(Or http://<YOUR_ALB_DNS_NAME>/admin if using path-based routing on port 80/443)
- Complete the initial setup wizard (SAP Runtime IDs, Administrator Account, Log Levels).
- Log in to the Admin UI, go to Repositories, and configure at least one storage repository.
3. Start ALinkServer Worker Service
- Start the alinkserver worker service and wait ~2 minutes for health checks to pass.
- Verify access to the primary worker endpoint:
- Test Admin-Worker connectivity by clicking ServerInfo for your repository in the Admin UI. Seeing repository details confirms a successful deployment.
4. Connect SAP System
- Log in to your target SAP system and launch transaction OAC0.
- Create a new SAP Content Repository, use ArchiveLink version 0046.
- Set the HTTP Server field to the hostname/IP of your ALinkServer load balancer.
- Copy the HTTP Script path from your repository's configuration page in the ALinkServer Admin UI and paste it into SAP.
- Save, run Test Connection, and send the SAP security certificate from OAC0 to ALinkServer.
Status: Your SAP Content Repository is now active and ready for data or document archiving scenarios.
Support
Vendor support
Contact Support
For technical support, deployment assistance, or general inquiries, contact Sol4Cloud at support@sol4cloud.com . Please include details of your issue such as error messages, log excerpts, and your ALinkServer version.
Support Hours
Support is available Monday through Friday, 8:00 AM to 6:00 PM Central European Time (CET/CEST). Requests received outside business hours will be addressed on the next business day.
What We Support
- Troubleshooting ALinkServer container deployment and configuration
- SAP ArchiveLink content repository setup guidance (OAC0 configuration)
- AWS service integration issues (S3, DynamoDB, Secrets Manager, CloudWatch)
- Request processing errors and performance questions
- Subscription and billing inquiries
Getting Started
For new customers seeking deployment guidance, proof-of-concept assistance, or a walkthrough of ALinkServer configuration with your SAP environment, reach out to the same support address. We can arrange a guided session to help you get up and running.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
