aws-static-landing-pages

Deploys static landing pages to AWS with silent edge routing and performance optimizations.

1|1|Updated Mar 6, 2026

Search Tags:#performance #deployment #aws #landing-pages #static-site #cloudfront #edge-routing

Ready to run

npx skills add https://github.com/eymass/swe-plugin --skill aws-static-landing-pages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aws-static-landing-pages
Source: https://github.com/eymass/swe-plugin/tree/main/skills/aws-static-landing-pages
Command: npx skills add https://github.com/eymass/swe-plugin --skill aws-static-landing-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires aws-cli, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a production-grade workflow to deploy static landing pages to AWS with centralized, edge-accelerated routing and zero-downtime updates for paid-social campaigns.

Core Features & Use Cases

Silent multi-variant routing on a single domain using CloudFront Functions and S3 prefixes (no redirects), enabling multiple page variants under one URL.
Two-tier caching and performance tuning (HTML short TTL, hashed assets long TTL, HTTP/3, Brotli) to maximize ad-traffic conversion.
Security and operations hardening (OAC, TLS, security headers, Route 53 aliasing, CI integration, observability) with guided deployment workflows.

Quick Start

Follow the nine-step deployment workflow to publish a static landing page to AWS (S3 + CloudFront) with silent edge routing and verification.

Frequently Asked Questions about aws-static-landing-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I deploy static landing pages to AWS with silent edge routing for paid-social campaigns?▼

Deploy static landing pages to AWS using a nine-step workflow that builds your site, configures a private S3 bucket, sets up ACM certs, OAC, and a CloudFront distribution for silent edge routing. This ensures fast TTFB and zero-downtime updates for paid-social campaigns.

How does CloudFront Functions handle multi-variant routing on a single domain?▼

CloudFront Functions handle multi-variant routing by silently routing requests to S3 prefixes without redirects. This allows multiple page variants to be served under one URL based on geo, cookie, or UTM parameters for optimized ad-traffic conversion.

What's the best way to optimize TTFB for static sites on AWS CloudFront?▼

Optimize TTFB for static sites on AWS CloudFront by applying two-tier caching with short HTML TTLs and long hashed asset TTLs. Enabling HTTP/3 and Brotli compression further maximizes ad-traffic conversion through faster edge delivery.

Do I need aws-cli and jq to deploy a static site to S3 and CloudFront?▼

Yes, you need aws-cli and jq to execute the deployment workflow. These tools are required dependencies for automating the configuration of S3 buckets, CloudFront distributions, cache policies, and Route 53 aliasing.

What security hardening is included when deploying landing pages with AWS CloudFront?▼

Security hardening for AWS CloudFront landing pages includes Origin Access Control (OAC), TLS configuration, and security headers. The deployment workflow also enforces Route 53 aliasing and CI integration for secure, observable operations.

Can I serve geo-based or UTM-based landing page variants from a single S3 bucket?▼

Yes, you can serve geo-based, cookie-based, or UTM-based landing page variants from a single S3 bucket. CloudFront Functions silently route requests to specific S3 prefixes, enabling one-domain multi-variant routing without URL redirects.