Skip to main content

Show HN: I developed a native macOS client for EC2/S3 console https://ift.tt/3kyARfc

Show HN: I developed a native macOS client for EC2/S3 console Hello HN: Here is the link https://ift.tt/3kuuEAS After forgetting to turn off a p2.xlarge instance for a week, I got so mad at myself I learnt swiftUI to build a native macOS console for most of the actions I do on the web AWS console. I didnt want to use electron or other non native frameworks. Most importantly I just wanted it to know how much a certain instance costs right now, no matter its state, its type, its lifecycle(like ondemand or spot) and the costs associated with the EBS volumes attached including their IOPS/throughput and etc. It also has a S3 object browser, and a drag and drop UI to upload your files so that you can make S3 your own personal dropbox. I dont track or store anything, you just query the aws api. Sorry its a paid app, if anyone wants to try it and cant afford it let me know, I can send it to you. I think this can be useful and cost saving for individuals that spend more than 50usd per month on aws. August 29, 2021 at 11:23PM
Labels:

Comments

Post a Comment

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...
Post a Comment
Read more