s3deploy | simple tool to deploy static websites | Cloud Storage library

Yes you should have a separate bucket for website deployment and data storage. The bucket you use for website will usually be a public one (unless you are using it with cloudfront).

Your website doesn't feel like 100% (client side) static website. By that I mean every HTML page is pre-generated and everything is static on client side. If that's the case then /work/1 should not load any html page as it's not a html resource. For it to be HTML resource it should be like /work/1.html

With that being said, it looks like you're using React or some other technology which translates the routing when previous page is known. / -> /work/1

As you have CloudFront already in your stack. Just set the error pages to redirect back to home page and then it should work fine. Attaching the solution for my react app hosted on S3+CloudFront.

The lambda responsible for unzipping the archive and copying the contents to the destination crashed because it ran out of memory.

Increase its memory with memoryLimit when creating your BucketDeployment construct. By default, the lambda gets 128MB of memory, which is insufficient in your case.

You can extend Step and implement ICodePipelineActionFactory. It's an interface that gets codepipeline.IStage and adds whatever actions you need to add.

Once you have the factory step, you pass it as either pre or post options of the addStage() method option.

Something close to the following should work:

Try to pass env into the Bucket Stack props.

Code snippet:

This should be located under bin folder when you decalre stacks.

Unfortunately, it is not possible, as the necessary references are only available after deploy and therefore after you try to write the file (the file will contain cdk tokens).

I personally have solved this problem by telling cdk to output the apigateway URLs to a file and then parse it after the deploy to upload it so a S3 bucket, to do it you need:

• deploy with the output file options, for example: cdk deploy -O ./cdk.out/deploy-output.json
• In ./cdk.out/deploy-output.json you will find a JSON object with a key for each stack that produced an output (e.g. your stack that contains an API gateway)
• manually parse that JSON to get your apigateway url
• create your configuration file and upload it to S3 (you can do it via aws-sdk)

Of course, you have the last steps in a custom script, which means that you have to wrap your cdk deploy. I suggest to do so with a nodejs script, so that you can leverage aws-sdk to upload your file to S3 easily.

Here is a sample deploy step for S3