Repository files navigation

Motivation: replace Apache & Nginx rewrite rules and make them cloud and "business" friendly.

Key parts:

• Cloudfront +Lambda@Edge
• S3 Select to query rules and regexp.

    $ cd [project folder]    $ npm --prefix ./functions install ./functions    $ sls deploy

You can setup different rules:

• simple rules (rules.csv)
• complex rules (regexp.csv)

Complex rules are the fallback when a path is not found.

Other variables are available insetup.demo.json:

• Cloudfront TTL
• Bucket and files names
• x-api-key to invalidate cache
• a fake origin that never will be reached
• TTL for regexp file (avoid continuous S3 select)

You can have serveral DNS over a distribution, and rules and regexp are dependant on host domain.

• /{whatever} > it will search for {whatever} and the host requested into the CSV
  • first search is into simple rules csv. If not found, it maps query against regexp file (default cache 300000 millis / 5 minutes). You can setup it in setup.demo.json.
  • if a path is found, a 301 redirect is returned. If not, 404.
• /invalidate/ --> POST. It will generate a invalidation request. Params
  • x-api-key: defined in setup.demo.json
  • x-invalidatepaths: a string containing the paths to invalidate, comma separated

• Distribution id has to be set manually in setup.demo.json after a first deploy of the stack...

• https://medium.com/@mnylen/lambda-edge-gotchas-and-tips-93083f8b4152