nilesh asked
o1lab replied
as mentioned in pull request that button is misleading, seems like a growth hack for opta 
If button reads ‘deploying to x’ it should ‘deploy to x’. I guess here either one has to signup with opta or give opta the access of AWS account
The user doesn’t need to sign up to Opta, or require the access to account.
It’s all upto the user, all that Opta does make a configuration which can then be used to create infrastructure using the same binary.
And the button does as is written, Deploy to AWS. It’s just that a lot of complexities involved with creating the Infrastructure have been abstracted away.
Hey o1lab@discord we have made the required changes. Let me know if anything else needs to change with these.
Thank you for considering the changes, happy to merge PR
As also discussed over the call. Can you please provide a single machine setup in another PR ?
And info of Opta not storing any details from AWS is in 2nd step - first step is ideal (as discussed)
Hey o1lab@discord those changes were good and we were able to provide more clarity to the new users of Opta with your help.
Can you take a look at the PR: Adding deploy to AWS using Opta as a deployment option in readme by nsarupr · Pull Request #1128 · nocodb/nocodb · GitHub
Should we add the Deploy to AWS using Opta button some place else or is the readme just fine?