429 - Too many requests

In aws.InstalledService Following has to be converted to OnetoOneField since sice a InstalledService is tied with single InstallableService as non identifying relation

installable_service = models.ForeignKey('InstallableService', related_name='installed_service',
on_delete=models.CASCADE)

Models can have their PK in format <MODEL_NAME>_id , which eases querying DB

When 2 tabs open the same plan and different changes are made in both tabs and saved, the final plan is not consistent.
Expected result: the tab in which the final save happens should be the final version.

• Hackernews
• Individual companies
• Social media accounts
  • twitter , linkedin , discord, instagram

Can an user get following perspectives on EC2 ,

• Monitoring
• Security
• Utilization
• Billing

When a user deletes the last component, It causes the page to blank

We should have auto functionality implemented in all places like PlanSave, Component properties screen

authAxios.interceptors.response

1. Control endless loop

(TODO : Following interceptor may fall in endless loop when refresh token not set in httpOnly cookie
Backend has throttle control, which won't entertain more than 60 requests/sec)

2. When second attempt fails, redirect to Login page

noImplicitAny - is set to false. This needs to be reverted back to true and any related issues has to be fixed.

Right now this is lifecycle of a UI aws component (eg: EC2)

• created in Canvas ( while drag& drop) + Its backend object created
• Edited in canvas + Backend updated
• Deleted in canvas + Backend delete

Required enhancement : Front end object should compose required logic to for backend operations

Mock customer (AWS):

• Registration
• IAM User Creation
• IAM User Stored in Database in Encrypted Fashion
• Spin a EC2 instance
• Monitor it
• Terminate it

1. Use store instead of context for login and user
2. Fix the refresh bug by using the store

1. https://99designs.com/how-it-works
2. https://www.fiverr.com/?source=top_nav

EC2 instance_type has to be populated from a database, which is periodically updated from aws updates .

instance_type = models.TextField(default='t2.micro')

• start with empty square , after Instance started become green solid,
• Once terminated becomes empty square
• no auto refresh

After successful login accessToken can be stored in React Context

If user doesn't wish to save his AWS key & Secret key, then we should have option to provide them each & every time when he wants to deploy.