This PR adds CDK config to stand up all the bits required for a Lambda/APIGateway web server to work, to include s3 bucket for the pages, the function and gateway themselves, and domain mapping.
This is noted in the readme, but depending on the developer's domain registrar (i.e. if the registrar is anyone but AWS), a manual step will be required to input custom NS records to point to AWS nameservers -- these records can be found in the AWS Route 53 Hosted Zone once the Stack has been stood up. NB that many registrars put the time to populate custom NS records at up to 48 hours, so tearing down/standing up stacks/hosted zones during development is not recommended.
Also note that this PR does not quite get the web server 100% working, as adjustments need to be made to the github action which builds the artifacts required by the client, as well as to the lambda and/or s3 bucket to allow serving static pages.
This PR adds CDK config to stand up all the bits required for a Lambda/APIGateway web server to work, to include s3 bucket for the pages, the function and gateway themselves, and domain mapping.
This is noted in the readme, but depending on the developer's domain registrar (i.e. if the registrar is anyone but AWS), a manual step will be required to input custom NS records to point to AWS nameservers -- these records can be found in the AWS Route 53 Hosted Zone once the Stack has been stood up. NB that many registrars put the time to populate custom NS records at up to 48 hours, so tearing down/standing up stacks/hosted zones during development is not recommended.
Also note that this PR does not quite get the web server 100% working, as adjustments need to be made to the github action which builds the artifacts required by the client, as well as to the lambda and/or s3 bucket to allow serving static pages.