s3-put bad request error about terraform-aws-next-js

[ofhouse]

Yes Windows is currently not supported since we rely internally on some Bash scripts that are executed during terraform apply.
Bash is not supported on Windows and that's the reason why you see those errors.

Windows support is not a top priority for this project. Do you have the possibility to use a Linux-Subsystem (WSL), or a CI (e.g. Terraform Cloud) for making the deployments?

[ofhouse]

No problem,
every customer-facing route ("all incoming traffic") is served by the CDN (CloudFront).

CloudFront uses two different sources (three with image optimization) where a request is served from.
S3 and API-Gateway + Lambda are sources where CloudFront forwards the incoming traffic to when no copy is in the CloudFront cache.
The request from a viewer itself is terminated by CloudFront, so no customer will request (or see) the S3 or API-Gateway resources directly but they are initiated (and signed for S3 sources) by CloudFront.

[otekdo]

It does not let me deploy the website, that mistake is still happening!

module.tf_next.module.statics_deploy.null_resource.static_s3_upload (local-exec): Executing: ["cmd" "/C" "./s3-put -r us-east-1 -T C:/apps/web/mynextapp/client/.next-tf/static-website-files.zip /next-tf-deploy-source20210331135505030700000001/static-website-files.zip"] module.tf_next.module.statics_deploy.null_resource.static_s3_upload (local-exec): '.' is not recognized as an internal or external command, module.tf_next.module.statics_deploy.null_resource.static_s3_upload (local-exec): operable program or batch file.

[otekdo]

Thanks for these details, did not know that!
I'll give a try with Terraform Cloud!

[otekdo]

@ofhouse This is a off-topic question...

The /_next/static/chunks/ or /_next/static/ files,
are they served from the S3 Bucket directly
or
are they served from the CDN?

I did not understand these statements properly!

[otekdo]

Wow, amazing!
Thanks for the deep explanation!