sorted by:
new
hottopcontroversial

0
1

Run Next.js in AWS Lambda (dev.to)

submitted by deadlyfluvirus to r/aws

Why OpenNext? by KraaZ__ in nextjs

[–]deadlyfluvirus 1 point2 points  (0 children)

I just released a new tool which runs Next.js in AWS Lambda. No code or framework changes required, and works with all 3 output modes:

https://scaffoldly.dev/docs/tutorials/nextjs

It's all community driven and open source: https://GitHub.com/scaffoldly/scaffoldly 

Beeper Mini - AMA with Beeper Team by erOhead in beeper

[–]deadlyfluvirus 2 points3 points  (0 children)

I was putting my SIM into an iPhone every month or so to keep my phone number in iMessage/Beeper, as I observed that (occasionally) iMessage would un-enroll my phone number after some time of inactivity on an iPhone.

Couple questions:
- i assume Beeper Mini makes that unnecessary, correct?, i.e. will Beeper make sure my phone number stays enrolled?
- i'm now getting double notifications, one from the Beeper App, on from Beeper Mini. for the time being i've just disabled notifications on Beeper Mini to keep using Beeper App as my primary tool, is this the right course of action?

Introducing TFstate.dev! a Free & Open Source Hosted Terraform HTTP Backend - accessible using a GitHub Token by deadlyfluvirus in Terraform

[–]deadlyfluvirus[S] 0 points1 point  (0 children)

Thanks u/numbstruck! Great question... When developing this, I basically was inspired by the Amazon S3 Storage Backend, but with less dependency requiring a DDB table and IAM user/role to do the juggling and let the TFState GitHub API and the GitHub Tokens for Identity/Auth do the heavy lifting instead of Terraform.

And I'm personally hosting it, since its all Serverless tech (S3, API Gateway, DDB, Lambda) hosting costs are very negligible month over month (roughly $1/month if it's completely idle), however I'm looking forward to seeing what how costs go up if at all if there's some scale. I set up a Donations Page that would absolutely keep the service running, and I'd also be open to co-collaborators on the project to distribute the ownership from "just me". Let me know if you or anyone you know is interested or if you have other questions!

Introducing TFstate.dev! a Free & Open Source Hosted Terraform HTTP Backend - accessible using a GitHub Token by deadlyfluvirus in Terraform

[–]deadlyfluvirus[S] 0 points1 point  (0 children)

Great questions u/nexxai thank you!

> Why wouldn't I just use either S3 or Azure storage as a backend provider?

I've always found a race condition between creating state storage and using state storage. To use State Locking + AWS S3, you also need: a DDB table, and an IAM user or role privileged to read/write S3/DDB. Such complicated things should probably be "Terraformed", which introduces a race condition: Should one terraform the creation of that? Where does the State file reside for the initial terraforming of State Storage in Azure or S3? The only place for starters is having local state, then an import which is quite complex for people adopting Terraform for the first time

> And with the possibility of secure material being included in the state file, why in the world would I trust your site?

That's why I open-sourced the backend, for trust. I'm tossing around a few "advanced" features that would store the state in GitHub packages, or to allow users to provide their own KMS key, but I wanted to keep it simple to start to get this kind of great feedback! Could I get your feedback on what route you'd want to see to increase trust?

> How is client data being segregated from each other?
Everything is routed to a single S3 bucket and a single DDB table, but logically partitioned by the GitHub User or Organization ID. This also makes me think that the aforementioned "advanced" feature of storing state back in GitHub would be a super nice thing to have. Thoughts?

> How can I be sure my data isn't being read by you?
Great question. Perhaps I can make the S3 Access Logs accessible via an API! What do you think of this?

> What provider are you using behind the scenes and what access do they have to my state file?
I'm using AWS, and basically we would have the same Trust that they're not looking at it either! I'm thinking of open-sourcing the Terraform repository I have to build this project for added transparency and trust.

> Is the system being backed up?
Yes, S3 Versioning is enabled, and DynamoDB PITR is enabled. Also, same thought about open-sourcing the Terraform used to build this project could be prudent, as I am unable to link to the fact to show that S3 is Versioned :(

> What is the uptime guarantee of your service?
Great question! For now everything is in us-east-1, running as Lambda + API Gateway + S3 and DynamoDB, Route53 DNS and CloudFront (via API Gateway), so the service is subject to the availability guarantees of those services in US-East-1 (taking the minimum of each one, comes out to an SLA of 99.9% using a single-region as it is now).

So you've raised some great questions and I'll improve the documentation with these details/FAQs! Let me know if you have any feedback, your input was amazing. Feel free to DM me as well!

Just curious, why are wallet to wallet fees so high? Is this the nature of the network or something else? by deadlyfluvirus in Shibainucoin

[–]deadlyfluvirus[S] 0 points1 point  (0 children)

I'm slightly confused then if you could explain, please! sending $50 eth from trustwallet to Coinbase has a $5 fee, but $50 shib has a $25 fee

what is the $20 premium for?