There is presently a chicken & egg situation with the CloudFront-Auth Lambda and the CloudFront distribution both requiring TF outputs from each other. Work-around at this time is to just:
Details about the code layout.
Code layout based on Terragrunt recommendations
├── env # Environments or Deployments
│ ├── prod # Production
│ │ ├── terraform.tfvars #
│ │ └── terragrunt.hcl # Use Terragrunt to get DRY code
<snip>
├── modules # Terraform modules, ideally standalone, no Terragrunt
│ ├── infra-cicd #
│ │ ├── README.md #
│ │ ├── data.tf # All TF data sources in one place
│ │ ├── files #
│ │ │ └── # Static files …Details about the design & AWS resources used to build & host this site.
A Terraform module to deploy AWS resources serving a static website over HTTPS, with a directory secured by AWS Cognito.
A Terraform module deploying a CI/CD pipeline to publish updates to the …
read moreI’m a big fan of meta SQL, what I call it when you use SQL to write SQL. Something like:
SELECT
'INSERT INTO zzzdba.rowcount_census SELECT now(), ' ||
table_name || ', count(*) AS kount FROM '||
table_schema ||'.' || table_name || ';' AS metasql
FROM
information_schema.tables
WHERE
table_schema = 'accounts'
AND table_name ~ 'current_account_\d …Here's a technique I recently learned to get revertable deploys when using CloudFront in front of an S3 hosted website.
The cornerstone is manipulating the CloudFront OriginPath attribute.
With a few tweaks, this technique could be used in a CI/CD pipeline to publish with blue/green deployments.