Live data from Hacker News

Show HN: Vantage – An alternative AWS console focused on developer experience

vantage.sh

61–70 of 88 posts

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#61

Earlier quoted context omitted.

The provided CloudFormation stack creates a Cross Account IAM Role with a list of read only permissions. We don't accept access keys or secrets. - A permissions overview is here (most aren't used for now). This list was made from the AWS-managed IAM policy of "ReadOnlyAccess" but whittled down to remove things like our ability to read from S3 Buckets or Databases: https://docs.vantage.sh/permissions/ - The latest Clo…

I'm so refreshed to see this designed this way. I assumed that they would be asking for an API key or equivalent, because I don't know anything about the product team or the company and this bad behavior is so bog-standard. I beg you to blog heavily about this approach, especially if you find success with it / it doesn't provide a very negative user experience. See if you can get featured on enterpriseready.io or som…

I am confused by your comment. How do they access the role they create if not through keys?

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#63

Earlier quoted context omitted.

I'm so refreshed to see this designed this way. I assumed that they would be asking for an API key or equivalent, because I don't know anything about the product team or the company and this bad behavior is so bog-standard. I beg you to blog heavily about this approach, especially if you find success with it / it doesn't provide a very negative user experience. See if you can get featured on enterpriseready.io or som…

I am confused by your comment. How do they access the role they create if not through keys?

You can allow IAM roles in your account (which simply just has the permissions defined, with no keys or other credentials associated) to be assumed by identities in another account. Vantage would then be responsible for securing credentials for the target identity in their account, but there would be no transfer of keys involved whatsoever from one party to another.

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#64
very cool view on my checkered history of failed and abandoned personal projects lol. nice to have it confirmed they're not still costing me money though!

one question. I have a couple projects on Amplify that don't pop up on my Vantage dashboard. Is it just a subset of AWS services that are included?

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#66

Earlier quoted context omitted.

I'm so refreshed to see this designed this way. I assumed that they would be asking for an API key or equivalent, because I don't know anything about the product team or the company and this bad behavior is so bog-standard. I beg you to blog heavily about this approach, especially if you find success with it / it doesn't provide a very negative user experience. See if you can get featured on enterpriseready.io or som…

I am confused by your comment. How do they access the role they create if not through keys?

You can create a role with certain permissions in your account. You can then configure this role to only be assumed by another user in another specific AWS account.

This is how you can share resources between different AWS accounts.

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#67
Congrats on launching a product. I think it’s a great idea for small - medium sized shops to use this.

I used to be an SRE at a large company with a gigantic AWS account. While the console can be a mess, it’s really information dense and once you are familiar with it, you can find a lot of stuff. It also meant that it was easier to use awscli because you knew what was available without reading the docs.

I honestly don’t need things to look well designed with lots of white space at the expense of lowering the information density.

Cost saving views displayed in plaintext above resources are cool, but not better than the billing console which can be fairly powerful.

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#68
post #14

Earlier quoted context omitted.

Congrats on the product launch, looks a neat UI. AWS easily has the worst UX of the three major clouds I've used. From that perspective my favourite by far is GCP. Do you forsee supporting other cloud vendors? I guess there is a lot less demand for others, in terms both of number of users, and also Google and Microsoft UIs are a bit less awful to start with...

Thank you! Great question. We are planning on supporting GCP, Azure, DigitalOcean and Heroku in the future and have users who have actively been requesting support for all of them. Additionally - I think we can build a truly objective cloud console that shouldn't be relegated to just public cloud provider services. For example: Why can't scale.ai sit alongside ML offerings from AWS and GCP? Why can't Cloudflare see S…

Great product - sorely needed for AWS - that said Heroku is an interesting choice... I’ve been using it for almost 10 years now and I’m not sure how much more room for improvement there is - maybe I’ve got blinkers on - what are the Heroku UI/UX pain points you’re seeking to solve?

Re: Show HN: Vantage – An alternative AWS console focused on developer experience

#70
post #68

Earlier quoted context omitted.

Thank you! Great question. We are planning on supporting GCP, Azure, DigitalOcean and Heroku in the future and have users who have actively been requesting support for all of them. Additionally - I think we can build a truly objective cloud console that shouldn't be relegated to just public cloud provider services. For example: Why can't scale.ai sit alongside ML offerings from AWS and GCP? Why can't Cloudflare see S…

Great product - sorely needed for AWS - that said Heroku is an interesting choice... I’ve been using it for almost 10 years now and I’m not sure how much more room for improvement there is - maybe I’ve got blinkers on - what are the Heroku UI/UX pain points you’re seeking to solve?

Thank you! We aren't looking to add any UI/UX improvements to Heroku but are looking at facilitation of migrating (or replicating) Heroku accounts to one of the larger players like GCP/Azure/AWS.

So essentially we'd look at your current Heroku setup and look to replicate it on a public cloud provider of your choice.

Post reply on HN