AWS 混合雲架構 - AWS Hybrid Cloud

# AWS 與 CDN (On-Premise) 混合雲邊緣節點架構
# AWS Hybrid Cloud Edge Node Architecture with On-Premise CDN

Description:
應對突發大流量，建立混合雲調度機制，結合 AWS 公有雲資源與實體機房 CDN 架構。透過自動化腳本與 AMI 模板實現邊緣節點 (Edge Node) 的快速配置與動態擴展，縮短資源上線時間。
To handle burst traffic, I established a hybrid cloud orchestration mechanism integrating AWS public cloud resources with on-premise CDN infrastructure. By leveraging automated scripts and AMI templates, the system enables rapid provisioning and dynamic scaling of edge nodes.

Tech Stack:

• Python (FastAPI / boto3)
• Systemd Service
• AWS EC2 (AMI & Launch Templates)
• Networking: BYOIP / ENI / A10 Load Balancer

Features:

• AMI 與啟動模板 (AMI & Launch Template)
  預建置客製化 AMI 與啟動模板 (Launch Template)，確保所有動態擴展之節點具備一致的運行環境與配置。
  Pre-configured customized AMIs and Launch Templates to ensure a consistent runtime environment across all dynamically scaled nodes.
• Systemd 自動化腳本 (Bootstrap Script)
  開發 Systemd 整合腳本，透過 AWS Instance Metadata (IMDS) 自動配置節點身分 (Hostname)，並在開機後自動註冊回 CDN 叢集。
  Developed a Systemd-integrated bootstrap script that leverages AWS IMDS for automated hostname configuration and self-registration.
• boto3 自動化配置 (Automated Provisioning)
  後端系統透過 boto3 自動根據 IP 前綴 (IP Prefix) 序號建立 EC2 與彈性網路介面 (ENI)，並管理自帶 IP (BYOIP) 之分配。
  The backend orchestrates EC2 and ENI creation via boto3, automatically assigning IP addresses based on IP Prefixes and managing BYOIP resources.
• 混合雲流量導流 (Hybrid Traffic Steering)
  結合地端 A10 負載均衡器，將特定網段流量精準導向至 AWS 雲端邊緣節點，實現無縫的流量卸載。
  Integrated with on-premise A10 Load Balancers to steer specific traffic segments toward AWS cloud edge nodes.

Results:

• 針對突發大流量可秒級加開雲端邊緣節點，相較於傳統虛擬機 (VM) 配置更簡單且節省部署時間。
  Enabled second-level provisioning of cloud edge nodes during peak traffic.
• 雲端節點可根據需求隨時切換為一般節點 (Normal Edge) 或防護節點 (Protect Edge)，最大化資源利用率。
  Cloud nodes can be dynamically repurposed as either Normal or Protect Edges based on demand.
• 突破實體機房資源限制，省去伺服器採購與實體上架的等待週期，大幅提升基礎設施的擴充性。
  Overcame physical datacenter limitations and eliminated lead times for server procurement.

Architecture Overview:

sequenceDiagram
    participant User as Operator
    participant Platform as FastAPI Backend
    participant AWS as AWS (boto3)
    participant EC2 as EC2 Instance
    participant CDN as CDN Cluster
    
    User->>Platform: Create Edge EC2 Request
    Platform->>AWS: Launch from AMI/Template
    Platform->>AWS: Create ENI & Assign BYOIP
    AWS-->>Platform: EC2 Instance Created
    EC2->>EC2: Systemd Bootstrap (IMDS)
    EC2->>EC2: Configure Hostname
    EC2->>CDN: Auto Register to Cluster
    CDN-->>EC2: Registration Complete
                

sequenceDiagram
    participant Client as Client
    participant A10 as A10 Load Balancer
    participant EC2 as AWS EC2 Edge
    participant Origin as Origin Server
    
    Client->>A10: Request (Specific IP Range)
    A10->>EC2: Route to AWS Edge
    EC2->>Origin: Fetch Content
    Origin-->>EC2: Response
    EC2-->>A10: Return Content
    A10-->>Client: Response