AWS三层Web应用架构：S3存静态资源仍需Web服务器？求全环节示例

Great question! Let's break this down clearly—first explaining the role of a web server alongside S3, then walking through a real-world e-commerce platform example that ties all four components together.

Why a Web Server Is Still Necessary When Using S3 for Static Content #

S3 is fantastic for hosting static assets like images, CSS, and pre-built HTML, but it has limitations that a web server solves:

• Smart Request Routing: S3 can't differentiate between static requests (like loading a product image) and dynamic requests (like fetching a user's order history). A web server (e.g., Nginx) acts as a traffic cop, sending static requests to S3 and forwarding dynamic API calls to your application server.
• Centralized Security & SSL: While S3 supports HTTPS, a web server lets you handle SSL termination in one place, enforce WAF rules to block attacks (like SQL injection or XSS), and add authentication layers (e.g., basic auth for admin static pages) that S3's bucket-level permissions can't easily manage.
• Unified User Experience: A web server provides a single domain for your entire app. Users don't need to visit separate URLs for static and dynamic content—everything flows through your main domain.
• Edge Logic & Caching: You can configure caching rules on the web server to reduce S3 traffic (e.g., cache product images for 24 hours) or use server-side includes (SSI) to inject dynamic content into static pages.

Example Application: E-Commerce Product Showcase Platform #

Here's how S3, Web Server, Application Server, and Database work together in a functional e-commerce app:

1. S3: Static Resource Repository #

• What it stores:
  • Product images (JPG/PNG) and promotional videos
  • Frontend bundle files (React/Vue compiled JS/CSS)
  • Static pages (About Us, Help Center, Privacy Policy)
• Key configurations:
  • Enabled static website hosting (set to private, accessed only via web server proxy)
  • Version control turned on to recover accidentally deleted assets
  • Lifecycle rule to archive old, unused product images to S3 Glacier for cost savings

2. Web Server (Nginx) #

Acts as the entry point for all user requests. Here's a simplified Nginx config snippet to show its role:

server {
    listen 443 ssl;
    server_name my-shop.com;

    # SSL certificate from Let's Encrypt
    ssl_certificate /etc/nginx/certs/fullchain.pem;
    ssl_certificate_key /etc/nginx/certs/privkey.pem;

    # Proxy static assets to S3 with caching
    location /static/ {
        proxy_pass https://my-shop-static.s3.amazonaws.com/;
        proxy_set_header Host my-shop-static.s3.amazonaws.com;
        expires 1d;
        add_header Cache-Control "public, max-age=86400";
    }

    # Forward API requests to application server cluster
    location /api/ {
        proxy_pass http://app-server-cluster:8080/;
        proxy_set_header X-Real-IP $remote_addr;
        # Rate limiting to prevent abuse
        limit_req zone=api burst=10 nodelay;
    }

    # Serve main app entry point (React SPA)
    location / {
        proxy_pass https://my-shop-static.s3.amazonaws.com/index.html;
    }
}

• Core jobs: SSL termination, request routing, caching, rate limiting, and WAF integration.

3. Application Server (Node.js/Express) #

Handles all dynamic business logic. Here's a sample API endpoint for fetching active products:

const express = require('express');
const mysql = require('mysql2/promise');
const app = express();

// Connect to AWS RDS MySQL database
const dbConnection = async () => {
  return await mysql.createConnection({
    host: 'my-shop-db.cxxxxxx.us-east-1.rds.amazonaws.com',
    user: 'db-admin',
    password: 'secure-password-123',
    database: 'shop_db'
  });
};

// Get active products API
app.get('/api/products', async (req, res) => {
  try {
    const conn = await dbConnection();
    const [products] = await conn.execute(
      'SELECT id, name, price, image_url FROM products WHERE is_active = 1'
    );
    await conn.end();
    res.status(200).json({ success: true, data: products });
  } catch (err) {
    console.error(err);
    res.status(500).json({ success: false, message: 'Failed to load products' });
  }
});

app.listen(8080, () => console.log('App server running on port 8080'));

• Core jobs: Database interactions, user authentication (JWT), order processing, and integrating AWS services like SNS for order notifications.

4. Database (AWS RDS MySQL) #

Stores all structured business data:

• What it holds: Product catalog, user profiles, order history, inventory levels
• Key configurations:
  • Multi-AZ deployment for high availability (automatic failover if primary instance fails)
  • Read replica to offload product list queries from the primary database
  • Automated daily backups with 30-day retention
  • Security group restricted to only allow traffic from the application server cluster

内容的提问来源于stack exchange，提问作者k''