Merge branch 'master' into dev-guides-589

Author: yashtandon113

.github/workflows/deploy.yml

@@ -40,7 +40,6 @@ jobs:
         apt install -y openssh-client -y
     - name: Make changes
       run: |
-        sed -i "s^baseUrl:.*^baseUrl:'/docs',^" docusaurus.config.js
         sed -i "s^appId.*^appId: '${{ secrets.ALGOLIA_APP_ID }}',^" docusaurus.config.js
         sed -i "s^apiKey.*^apiKey: '${{ secrets.ALGOLIA_API_KEY }}',^" docusaurus.config.js
 
@@ -68,8 +67,8 @@ jobs:
 
     - name: Connect and upload
       run: |
-        ssh -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa ${{ secrets.SSH_USER }}@${{ secrets.SSH_HOST }} "find /home/antmedia.io/public_html/docs/ -type f -not -name "*.tar" -not -path "/home/antmedia.io/public_html/docs/.ssh/*" -exec rm {} \;" 
-        ssh -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa ${{ secrets.SSH_USER }}@${{ secrets.SSH_HOST }} "find /home/antmedia.io/public_html/docs/ -type d -empty -not -path "/home/antmedia.io/public_html/docs/.ssh*" -delete"
+        ssh -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa ${{ secrets.SSH_USER }}@${{ secrets.SSH_HOST }} "find /home/docs.antmedia.io/public_html/ -type f -not -name "*.tar" -not -path "/home/docs.antmedia.io/public_html/.ssh/*" -exec rm {} \;" 
+        ssh -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa ${{ secrets.SSH_USER }}@${{ secrets.SSH_HOST }} "find /home/docs.antmedia.io/public_html/ -type d -empty -not -path "/home/docs.antmedia.io/public_html/.ssh*" -delete"
         scp -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa -r docs.tar ${{ secrets.SSH_USER }}@${{ secrets.SSH_HOST }}":"
         ssh -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa ${{ secrets.SSH_USER }}@${{ secrets.SSH_HOST }} "tar -zxvf docs.tar && rm -rf docs.tar"
 

docs/guides/adaptive-bitrate/enforcing-stream-quality.md

@@ -103,7 +103,7 @@ For example, if your HLS playlist has multiple bit rates:
 Here is the HLS URL format for specific bitrate and resolution:
 
 ```
-https://domain:port/AppName/streams/[streamid]_[quality].m3u8
+https://domain:5443/AppName/streams/[streamid]_[quality].m3u8
 ```
 For example:
 

docs/guides/advanced-usage/overcoming-restricted-networks-webrtc-ams.md

@@ -25,6 +25,9 @@ sed -i -e 's/^User=.*/User=root/' -e 's/^Group=.*/Group=root/' /etc/systemd/syst
 
 systemctl daemon-reload
 ```
+```
+sudo setcap 'cap_net_bind_service=+ep' /usr/bin/turnserver
+```
 
 3. Get a certificate for your domain. (TLS/TCP does not work in Let's Encrpyt Coturn due to socket buffer operation error) 
 
@@ -35,7 +38,7 @@ lt-cred-mech
 user=your-username:your-password
 realm=your-server-host-name
 listening-port=80
-listening-tls-port=443
+tls-listening-port=443
 alt-listening-port=3478
 alt-tls-listening-port=5349
 proto=tcp

docs/guides/clustering-and-scaling/aws/aws-auto-managed/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "AWS Auto Managed Service",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "description": "Deploy Ant Media Server Auto-managed Live Streaming Service on AWS."
+  }
+}

docs/guides/clustering-and-scaling/aws/aws-auto-managed/auto-managed-service-on-aws.md

@@ -0,0 +1,147 @@
+---
+title: Auto Managed Service on AWS
+description: Deploy Ant Media Server Auto Managed Service on AWS
+keywords: [Auto Managed Service, Pay As You Go, Ant Media Server Documentation, Ant Media Server Tutorials]
+sidebar_position: 1
+---
+
+# Auto-Managed Service: Live Streaming, Simplified
+Live streaming is powerful — but managing it is not. Scaling infrastructure, handling peak traffic, ensuring low latency, and paying for idle servers can quickly become overwhelming. Many teams spend more time managing infrastructure than building their product.
+
+**Ant Media’s Auto‑Managed Live Streaming Service** solves these challenges. It provides a fully managed, scalable, pay-only-when-you-use platform on **AWS** that gives you complete control over your content — without the operational overhead.
+
+Whether you are a developer, a product team, or a streaming company, this service allows you to focus on what matters: delivering seamless, real-time streaming experiences to your users.
+
+## Why Auto‑Managed Live Streaming Service Matters
+Modern live streaming faces three main pain points:
+
+1. **Operational Complexity**
+    Scaling servers, handling failures, and managing clusters is time-consuming and error-prone.
+
+2. **Hidden Costs**
+    Traditional platforms bill continuously, even when streams are idle, leading to wasted resources.
+
+3. **Limited Control & Flexibility**
+    Many solutions lock your data or restrict how you can build custom workflows, analytics, or integrations.
+
+Auto‑Managed Live Streaming Service addresses all three: it **automatically scales**, **charges only for active usage**, and provides **full ownership and flexibility** over your streaming workflows.
+
+## Why Use Auto-Managed Service
+
+| Feature                     | Why It Matters                                                   |
+| --------------------------- | ---------------------------------------------------------------- |
+| **Automatic Scaling**       | Spin up resources on demand; no manual server setup required.    |
+| **Usage-Based Billing**     | Idle periods cost nothing; you pay only when streaming.          |
+| **Full Content Ownership**  | Streams are encrypted and fully under your control.              |
+| **SDKs & APIs**             | Easy integration with web and mobile apps.                       |
+| **Custom Workflow Support** | Add AI, analytics, recording, or moderation pipelines as needed. |
+| **24/7 Developer Support**  | Help is always available for implementation or troubleshooting.  |
+
+**Result**: Teams can achieve up to **5× cost savings** compared to always-on setups, without sacrificing quality or control.
+
+## How It Works: Step-by-Step
+Here’s a clear path to enable and use the Auto‑Managed Live Streaming Service.
+
+### Step 1: Subscribe Ant Media Server via AWS Marketplace
+- Visit the [Ant Media Server listing](https://aws.amazon.com/marketplace/pp/prodview-464ritgzkzod6) in **AWS Marketplace** and click `View purchase options`.
+
+    ![](/img/auto-managed/subscription.webp)
+
+- Click `Subscribe` — no charges are incurred until usage begins.
+
+    ![](/img/auto-managed/purchase-details.webp)
+
+- Wait for confirmation that your subscription is active.
+
+### Step 2: Deploy with CloudFormation
+- Download the [CloudFormation template](https://auto-managed-ant-media-lambda-bucket-us-east-1.s3.us-east-1.amazonaws.com/Auto-Managed-Ant-Media-Server-Stack-latest.json) from Ant Media.
+
+- In the AWS Console, go to **AWS CloudFormation > Stacks**.
+
+- Click `Create Stack` with `New Resources` option.
+
+- Focus on `Specify Template` and choose `Upload a Template File` and Upload the CloudFormation Template you have just downloaded. Then click `Next`.
+
+    ![](/img/auto-managed/create-stack-name.webp)
+
+- Fill in required parameters (`Stack name`, Web Panel `Email`, `Password`, etc.) and click `Next`.
+
+Note: The `Period` value specifies the time after which the `instance` will `stop/terminate` if there is no stream on the server.
+    For example, the default value is 3, which implies that if there is no stream for 3 minutes, the server would stop/terminate.
+
+![](/img/auto-managed/provide-stack-name.webp)
+
+- click `Next` for the other pages, and `Submit`.
+
+- Deployment takes ~5 minutes.
+
+- Copy the **Lambda URL endpoint** from the **stack outputs**.
+
+    ![](/img/auto-managed/ant-media-paas.webp)
+
+- Visiting this URL triggers a backend instance (first spin-up **~60 seconds**; subsequent **~20 seconds**).
+
+    ![](/img/auto-managed/geting-ready.webp)
+
+- Congratulations, your backend is ready! Log in to the Web Panel to confirm everything is ready.
+
+### Step 3: Start Streaming with Auto-Managed Service
+
+#### Option 1: Using JavaScript SDK
+
+Integrate the Lambda URL into your WebRTC or JS SDK:
+
+```js
+var webRTCAdaptor = new WebRTCAdaptor({
+  httpEndpointUrl: "<REPLACE_WITH_LAMBDA_URL>",
+  localVideoElement: document.getElementById("localVideo"),
+  callback: (info, obj) => {
+   console.log("callback info: " + info);
+   if (info == "initialized")
+   {
+      webRTCAdaptor.publish("myStream")
+   }
+   else if (info == "publish_started") {
+      console.log("publish started");
+   }
+   else if (info == "publish_finished") {
+      console.log("publish finished")
+   }
+  }
+}
+```
+
+Check out the AMS [Javascript SDK](https://docs.antmedia.io/category/javascript-sdk/) guide for the integration.
+
+#### Option 2: Direct URL (Browser)
+
+Open the Lambda URL in a browser to access the Web Panel and start streaming. 
+
+Check out the [stream publishing section](https://docs.antmedia.io/category/publish-live-stream/) to publish streams using different protocols and ways.
+
+### Step 4: Configure Persistence & Recording
+
+- **Data Persistence**: Metadata and settings are stored in ElastiCache; they survive instance spin-ups.
+- **Recording**: Enable [S3 recording](https://antmedia.io/docs/category/s3-recording-and-integration/) to ensure your streams are saved even if instances terminate. Local disk recording may be lost when instances spin down.
+
+### Step 5: Stop or Terminate Instances
+
+- **Stop**: Preserves Elastic IP and EBS volumes; minimal storage cost; fast spin-ups.
+- **Terminate**: Deletes the instance completely; no idle cost; slower spin-ups.
+- Use CloudFormation to delete stacks when no longer needed.
+
+## Best Practices & Tips
+- Set a sensible **idle timeout** (~3 minutes recommended).
+- Prefer **S3-based recording** for important streams.
+- Monitor usage regularly to optimize cost and performance.
+- Combine Auto‑Managed instances with your existing pipelines for AI moderation, analytics, or custom workflows.
+
+## Real Impact: Before vs After
+
+| Problem            | Traditional Approach                | Auto‑Managed Streaming                 |
+| ------------------ | ----------------------------------- | -------------------------------------- |
+| Scaling            | Manual, slow, error-prone           | Automatic, fast, hands-free            |
+| Costs              | Always-on servers, wasted resources | Pay only when streaming                |
+| Content Control    | Limited, vendor-controlled          | Full ownership & encryption            |
+| Flexibility        | Locked workflows                    | Customizable SDKs, APIs, and pipelines |
+| Operational Burden | High                                | Minimal, backend fully managed         |

docs/guides/clustering-and-scaling/aws/aws-cloudformation/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "AWS CloudFormation",
-  "position": 1,
+  "position": 2,
   "link": {
     "type": "generated-index",
     "description": "Deploy Ant Media Server at AWS with AWS CloudFormation."