Live data from Hacker News

Show HN: Lemon – Alternative UI for AWS

uselemon.io

11–20 of 32 posts

Re: Show HN: Lemon – Alternative UI for AWS

#11
post #9
post #7

We are tackling this same issue, but in a different way. A unified UI for AWS and LocalStack. https://getcommandeer.com

Very cool! We're also considering building a mac app, that elegantly solves all the access control / compliance concerns The downside is that in client-only arrangement state is no longer centrally managed; I wonder how do you solve that? Or do you have a "hybrid" model with some parts on the client and others on the server?

So everything is done between the client app and AWS. Under the hood it is using the AWS SDK. We don't store any keys or any of your data on our servers. So, the user has to have access keys, and they can also have their session token. We also have it setup that it can read from your .aws/credentials file, so if you have a process that automatically updates that file, the session token is also automatically updated in the app.

Re: Show HN: Lemon – Alternative UI for AWS

#12
post #6

Great. More abstraction.

"Don't be snarky."

"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."

https://news.ycombinator.com/newsguidelines.html

"Be respectful. Anyone sharing work is making a contribution, however modest."

"When something isn't good, you needn't pretend that it is, but don't be gratuitously negative."

https://news.ycombinator.com/showhn.html

Re: Show HN: Lemon – Alternative UI for AWS

#13
post #8

Can this be launched internally, such that I am not leaking internal details out to a 3rd party? I can't imagine adopting this in the companies I've worked for, without that avenue.

+1

What'd you think of an "intermediate" solution like Mongo Atlas for example - hosted dedicated instance in your region, but managed by us?

Re: Show HN: Lemon – Alternative UI for AWS

#14
post #12
post #6

Great. More abstraction.

" Don't be snarky. " " Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something. " https://news.ycombinator.com/newsguidelines.html " Be respectful. Anyone sharing work is making a contribution, however modest. " " When something isn't good, you needn't pretend that it is, but don't be gratuitously negative. " https://news.ycombinator.com/showhn.html

Thanks!!

One of our fundamental challenges was and to some extent still is to strike the right balance. On the one hand, some high-level concepts are clearly needed because it's got so complex in the last decade. But on the other hand it can't be opague, low-level access and control are still needed because no stack is the same.

We believe we got this somewhat right by combining click-ops and Terraform into one seamless experience.

Re: Show HN: Lemon – Alternative UI for AWS

#17
I really don't know what must happen before I give AWS CRUD credentials to a third party.

However, that something didn't happen by reading this website and its value proposition.

I'm saying this as, hopefully, source for inspiration. The amount of trust a third party must inspire before anyone (like me at least?) dares to delegate operation must be overwhelming.

Re: Show HN: Lemon – Alternative UI for AWS

#18
post #17

I really don't know what must happen before I give AWS CRUD credentials to a third party. However, that something didn't happen by reading this website and its value proposition. I'm saying this as, hopefully, source for inspiration. The amount of trust a third party must inspire before anyone (like me at least?) dares to delegate operation must be overwhelming.

Thanks! This is super helpful

What'd be your thoughts on the following options:

- IAM role account-to-account (no credentials sharing)

- Self-hosted webapp that runs in your account

- Mac app so that creds never ever leave your laptop

Re: Show HN: Lemon – Alternative UI for AWS

#19
post #17

I really don't know what must happen before I give AWS CRUD credentials to a third party. However, that something didn't happen by reading this website and its value proposition. I'm saying this as, hopefully, source for inspiration. The amount of trust a third party must inspire before anyone (like me at least?) dares to delegate operation must be overwhelming.

Agreed, I'm not a fan of AWS's online console and its UI/UX, but my distaste isn't enough to login to AWS through another site. I'd rather navigate by CLI/API before I do that.

Furthermore, I'm not really a fan of these closed-source available-for-pricing, enhancement products. They last for a few months in pre-release form, gauge that they don't have the customer numbers to justify their revenue, and then cease development.

Post reply on HN