Cloud Native 8 min read

How to Integrate Alibaba Cloud AppStack with Serverless SAE for Seamless DevOps

This guide explains how to connect Alibaba Cloud's Cloud Effect AppStack with the Serverless Application Engine (SAE), covering role creation, trust policy configuration, service connection setup, cluster linking, application template usage, deployment orchestration, and pipeline execution to achieve low‑cost, high‑quality, and efficient continuous delivery.

Alibaba Cloud Native
Alibaba Cloud Native
Alibaba Cloud Native
How to Integrate Alibaba Cloud AppStack with Serverless SAE for Seamless DevOps

Background

For large R&D teams, balancing cost, quality, and efficiency in application development and operations is challenging, especially when managing many applications, a big team, and fast delivery cycles. Traditional K8s cluster management incurs high operational costs and can become a bottleneck.

Why Use SAE and AppStack

SAE (Serverless Application Engine) is an adaptive, elastic, fully managed application hosting platform that offers automatic scaling, pay‑as‑you‑go billing, and eliminates the need to manage K8s clusters, thereby reducing resource and maintenance costs. Cloud Effect AppStack provides a unified lifecycle management solution for development, deployment, and operations, enabling self‑service operations for development teams.

Key Benefits

Cost reduction through serverless, elastic scaling and pay‑per‑use model.

Efficiency gains via reusable application templates and parameterized deployment orchestration.

Quality assurance with standardized development processes, strict environment permissions, and production‑environment admission rules.

Integration Steps

1. Create RAM Role

Create a RAM role named sae-${accountId} and attach the AliyunSAEFullAccess policy.

2. Modify Trust Policy

{
  "Statement": [
    {
      "Action": "sts:AssumeRole",
      "Effect": "Allow",
      "Principal": {
        "Service": ["sae.aliyuncs.com"]
      }
    }
  ],
  "Version": "1"
}

3. Create SAE Service Connection

In Cloud Effect Flow, go to Global Settings → Service Connection Management and add a new SAE service connection.

4. Add SAE Cluster to AppStack

In Cloud Effect AppStack → Resource Pool, add a new SAE cluster, selecting the appropriate region.

5. Create Application and Link SAE Environment

Create a new application in AppStack, bind the code repository, then add an SAE environment under “Environment”. Set the environment label (dev/test/prod), choose SAE deployment, and select the previously added SAE cluster.

6. Configure Deployment Orchestration

In Application Settings → Deployment Orchestration, edit the YAML to include only the necessary parameters, as SAE will also apply its own settings.

7. Define Deployment Steps in the Pipeline

In the pipeline editor, add an “AppStack Deploy” task, select the SAE environment, and specify the image artifact produced by the build task.

8. Run the Pipeline

Execute the pipeline; the build task creates the container image, and the AppStack deploy task creates a deployment order that triggers SAE deployment. After successful deployment, the SAE application name matches the AppStack deployment name, and multiple SAE applications are created for different environments.

Conclusion

The integration of Cloud Effect AppStack with Alibaba Cloud SAE provides a cost‑effective, high‑quality, and efficient DevOps solution, especially suited for organizations with many applications, large teams, and rapid delivery cycles.

serverlessCI/CDDevOpsAlibaba Cloudsaeappstack
Alibaba Cloud Native
Written by

Alibaba Cloud Native

We publish cloud-native tech news, curate in-depth content, host regular events and live streams, and share Alibaba product and user case studies. Join us to explore and share the cloud-native insights you need.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.