[@fab/deployer-aws-lambda] Origin update? about fab HOT 5 CLOSED

Hey @thejuan, you have stumbled on an interesting conundrum. Because the Lambda@Edge will create the responses to all requests, there are no request that will ever go to the origin. So we don't need it, but CloudFront needs to have an origin set.

So we have settled for the using a static domain that basically says "If you can see this page, something is wrong in your FAB config".. We would have used a fab.dev domain, but then we get into trouble if it is called from another Cloudflare Workers sometimes.

But we can probably add a bit of explanation to the CF template why there is a Linc specific thing in there.

Did you get your FAB running on Lambda@Edge?

from fab.

Ahh! I should have just tried it :)
It is indeed working.

I had to remove the lambda association from the CF template as was getting a permissions error.
The fab deploy associated it fine for me.

Then had to monkey patch the aws cred stuff from #180

from fab.

Which is a good point actually. We can just remove the entire CF template and just call the API endpoints directly in the deployer.

from fab.

It is nice to have some finer grain control over the CF, like cnames. But if that was still exposed somehow in the advanced scenario, it would make setup much quicker

from fab.

Yeah, we can absolutely surface that in some way or another.

from fab.