0x4447_product_s3_email
former2
0x4447_product_s3_email | former2 | |
---|---|---|
15 | 11 | |
3,010 | 2,140 | |
0.1% | - | |
2.6 | 7.6 | |
4 months ago | about 2 months ago | |
JavaScript | ||
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
0x4447_product_s3_email
-
Free VPS as SMTP Proxy
Here is something on GitHub that roughly follows this paradigm, and was made to use SES as the "email server".
-
Need any open-source alternatives?
- https://github.com/0x4447/0x4447_product_s3_email
-
Self-hosted email is the hardest it's ever been, but also the easiest
> Could there be a serverless alternative where the service wakes up only to receive emails and will be charged only when emails are processed, filtered and served & rest of the time no charge - avoiding $3 to $5 charged by behemoths per inbox?
I love ideas as much as the next guy and serverless email is kind of floating out there:
https://medium.com/schibsted-engineering/building-a-serverle...
https://github.com/arithmetric/aws-lambda-ses-forwarder
https://github.com/0x4447/0x4447_product_s3_email
It's possible to build it, but the problem is that you still have the same problem of deliverability. Obviously it works fine/great for receving emails though.
> Idea is how cheap can it go for personal inbox with all the features denied by the superlative pricing plans
It could get really cheap, but would people buy it? I always wonder if price is really the limiting factor for self hosted emails.
Zoho is already QUITE cheap: https://www.zoho.com/mail/zohomail-pricing.html
Maybe this would work as a business, but it's a bit questionable to me.
- Lambda email system
-
Get email attachments directly into S3 bucket?
Based on your description I think this project is for you: https://github.com/0x4447/0x4447_product_s3_email - it dose what you are looking for, I hope this helps.
-
Need Help | Create serverless 'Email Service'
Here is a complete solution that hopefully gives you some ideas for a more simplified approach based on your needs. https://github.com/0x4447/0x4447_product_s3_email
-
Please fix the AWS free tier before somebody gets hurt
> What do you think about this page: https://aws.amazon.com/getting-started/
It is very dangerous. If you select the full-stack tutorial you get: "Time to Complete 30 minutes". It should say: "30 min to ruin your life" ;)
If you want to really learn AWS, then this page should be used as a reference of how to design a stack. If I were you I would read the tutorials to see which services are needed for a solution, but before doing anything, I would read the docs for each of those services to really understand them, then I would go back to the tutorial and actually do it, and - MOST IMPORTANTLY - I would read the pricing page for each service that you are going to use.
> Do you think it's irresponsible for AWS to encourage beginners to try their service when they apparently only intend it to be used by those with a computer science degree and 5-year apprenticeship under an experienced sysadmin?
100% - when I started working with AWS in 2016 I had a very hard time figuring it out, because I was looking for the simplicity the the marketing team was writing about. I really don't like what the marketing team tries to tell you, because it dose not exist.
Regarding an approach to learn about AWS, I would start with all the serverless services that they have, since the pricing for most of them is ideal for beginners (WARNING - read the pricing page for each since not all have a free staring plane, like S3 and DynamoDB) and for simple weekend projects.
For example, I did build this project a while ago: https://github.com/0x4447/0x4447_product_s3_email, if you scroll down to the pricing section you will see this:
```
- A serverless email server on AWS using S3 and SES
former2
-
Top 10 terraform tools you should know about.
Former2 is a tool that automates the creation of Infrastructure-as-Code (IaC) scripts from existing AWS resources. It utilizes the AWS JavaScript SDK to scan the user’s AWS infrastructure, identifying all available resources. Users can then select from this list which resources they want to include in their IaC outputs. This process simplifies the task of writing IaC scripts, especially for complex environments, by directly converting current AWS configurations into ready-to-use code. Former2 is particularly useful for documenting existing infrastructure or for migrating manually created resources into an IaC framework.
-
[Question] Cloud formation Template Import Resources tools
More info: https://github.com/iann0036/former2
- former2
-
Importing multiple modules at once from AWS
You can use tools like https://github.com/cycloidio/terracognita or https://github.com/iann0036/former2 to generate the terraform code for you. Then you can consolidate them and if they are simply the same type of objects with different values then you can use terragrunt to pass values to your terraform module.
- Is there a way to turn a existing cloudformation template into a terraform file?
-
Overwhelmed by AWS
I have never tried out this tool, but maybe it's worth checking: you could create all the stuff via AWS Console in a sandbox environment and then try to use former2. Nothing autogenerated will ever be good enough compared to handcrafted, but it should give you a nice starting point without much effort.Such a tool can not be expected to work reliably. Thankfully, you need to cover only classic, foundational services like EC2, ELB, and IAM, so I would expect them to work properly for those use cases.
-
how reliable is it to generate a cloud formation automatically from an existing AWS environment?
Author of Former2 here.
-
Disaster Recovery with Former2?
I've heard of a few people setting up pipelines that use the CLI with the `ALL` services option to generate inventories of their systems, but the generated template would almost certainly not work out of the box due to:
- tool to log into AWS and generate Terraform code
-
Current infrastructure as code
Not quite: a command line tool is also available: https://github.com/iann0036/former2/blob/master/cli/README.md
What are some alternatives?
aws-nuke - Nuke a whole AWS account and delete all its resources.
terraformer - CLI tool to generate terraform files from existing infrastructure (reverse Terraform). Infrastructure to Code
mCaptcha - A no-nonsense CAPTCHA system with seamless UX | Backend component
terracognita - Reads from existing public and private cloud providers (reverse Terraform) and generates your infrastructure as code on Terraform configuration
amail - AWS-hosted personal email system: sending, receiving, storage, and forwarding (relaying). `notmuch` client. JMAP server WIP.
MoonMail - Email marketing platform for bulk emailing via Amazon SES (Google Cloud Platform and Azure coming soon)
terraforming - Export existing AWS resources to Terraform style (tf, tfstate) / No longer actively maintained
Apache - Mirror of Apache HTTP Server. Issues: http://issues.apache.org
aws-multi-account-viewer - Serverless app designed for any customer with two or more accounts to view resources across accounts/regions in simple single pane of glass website
Listmonk - High performance, self-hosted, newsletter and mailing list manager with a modern dashboard. Single binary app.
driftctl - Detect, track and alert on infrastructure drift