Cloud-Architects / Cloud-Architects/open-console
MVP
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Hello friends, I am very interested in this project and I think we can start making an MVP version to validate the idea and the architecture.
I know that neither @meshuga nor I are specialists in front-end technologies like VueJS/React/Angular/ NuxtJs and others, but we can think of doing this in a simple way and who knows how to get some contributor with experience.
For this initial version I think we must have the following things:
1. Domain. We choose the name and I can register the domain.
2. The website with following features:
2.1 - Login using keys/region
2.2 - Screen showing which permissions are allowed
2.3 - VPC functionalities [1]
2.4 - Audit logs
3. We must decide the software architecture. I like the idea about a middleware to manage the calls from Website to AWS endpoints because we can control cache, permissions and others. The idea is not storage the user keys, but store a temporary token to control and resume the session. As the software is opensource and anyone can audit it, users can feel secure.
4. Ideas :D
[1]

Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by turning the proposed domain, website, key-based login, permissions screen, VPC functionality, audit logs, and AWS middleware into a decided scope and architecture; done means those decisions and an implementation plan are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- authentication, authorization, cloud, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100