Features
FAQ
Pricing
Docs
Blog
Features
FAQ
Pricing
Docs
Blog
Sign up
Sign up
  1. Help Center
  2. Releasing
NOTE: This article has been superseded.
Go to Documentation Home.
NOTE: You're viewing an article about a prerelease feature.
The information here is still being tweaked and may change.
As always, contact support if you have any questions.

AWS Lambda@Edge

By 
Tom Trinca
Last updated: 
May 7, 2020
  1. Create empty Lambda@Edge form on Linc
  2. Create an SSL/TLS certificate
  3. Apply Cloudformation template in us-east-1
  4. Create access/secret keys for user
  5. Copy remaining settings into Linc

Create empty Lambda@Edge form on Linc

Navigate to the Settings page of your Linc site and scroll to the Deploy Config section. Click the Create Lambda@Edge config button to create an empty Lambda@Edge config form for you to complete. Keep this tab open as we'll be returning here periodically to fill it in.

Create a SSL/TLS certificate

Navigate to Certificate Manager in AWS Console. Make sure the region is set to North Virginia (us-east-1).

  1. Create an SSL/TLS certificate for your domain *.example.com
  2. You have two options for domain ownership validation: email and DNS. We recommend DNS validation because it's automatically renewed.
  3. Create DNS entries for validation in the overview of the certificate manager. If your DNS is hosted on Route 53, press the Create record in Route 53 button. If your DNS is hosted elsewhere then make the appropriate change.
  4. Once you've created the certificate, navigate to the details section of the new certificate and copy the certificate ARN to your clipboard.

Apply Cloudformation template in us-east-1

Having copied your certificate ARN to the clipboard, navigate to Cloudformation, then:

  1. Create a stack by clicking the Create Stack button. Under the Choose a template section, select the Upload a template to Amazon S3 option and upload this lambda@edge cloud formation template we prepared earlier.
  2. In the next screen, specify your stack name, then fill out the Paramaters section as follows:
  3. Aliases - add all your domain names delimited by commas
  4. Certificate ARN - paste your certificate ARN from before here
  5. Sitename - enter the name of your Linc site name, for example: how-to-linc or linc-front-end

Create access/secret keys for user

Once you've created your stack, navigate to its' Stack Details page and expand the Resources section. Click on the DeployUser link under the Physical ID column, then in the Security Credentials tab, click the Create access key button. A modal will appear displaying your Access Key Id and Secret Access Key.

Copy and paste both the Access Key Id and Secret Access Key into their respective fields in the empty Linc Lambda@Edge form you have open in another tab.

Copy remaining settings into Linc

Return to the Resources section in your stack's Stack Details page, then fill in the remaining fields of the Linc Lambda@Edge config form as follows:

  • CF Distribution ID - Copy paste the CloudfrontDistribution Physical ID
  • Lambda Arn - Click the RenderLambda link under the Physical ID column. This will navigate you to the Lambda Management Console where you can copy the lambda ARN at the top of the page straight to the clipboard.

Your Lambda@Edge form on Linc is now complete, so you can go ahead and click Save. Your most recent FAB from your release branch should be automatically deployed to Lambda@Edge.

‍

Related Articles
Release Retries
Retry a failed release.
Release Rollbacks
Rollback instantly to a prior release.
Cloudflare Workers
Instantly deploy to 200 locations worldwide
Need additional support?
email us
contact@linc.sh
Twitter
@linc_bot
SLACK
lincbot.slack.com

The Perfect CI/CD Pipeline for your Frontend

Linc
  • Home
  • Pricing
  • Sign In
  • Sign Up
  • Live Demo
Learn More
  • Documentation
  • Blog
Get Help
  • Support
  • Contact
Legal
  • Terms & Conditions
  • Privacy Policy
© Bitgenics Pty Ltd 2019
M/710 Collins Street
Docklands
VIC 3008
AUSTRALIA