We have several developers working on our project. Would they also be required to have a serverless account and log in?
Yes. Every where you run āsls ā¦ā has to have āsls loginā done or an environment set. You can have unlimited users, even in the free tier as I understand it.
Our problem is you canāt migrate a single project/client from v3 to v4, itās all or nothing : Serverless 3 & 4 together
At some point Serverless are going to update their Chocolatey package from v3 to v4 and break everything.
What if I write this in terminal is it can deploy in v4 ?
export SERVERLESS_ACCESS_KEY="my_acess_key
Yes, that should work 
Every where you run āsls ā¦ā has to have āsls loginā done or an environment set.
Iām trying this framework for about 2 weeks. We had tried AWS SAM but this is a much simplier tool. Anyways, when I first read the pricing from the official webpage I felt like I had to pay to use it. Donāt ask me why, I believe the way youāre communicating it is confuse for some people. Aside for that, do I have to pay to use the CI/CD coming from serverless?
The features of Serverless Dashbaord such as CI/CD are paid for tools and you would need to purchase additional credits beyond the 2 free credits provided.
However, if all you want to do is use Serverless Framework CLI and are under the $2 million annual revenue threshold, there is no requirement to pay for your use of Serverless Framework and can use it as mucha s you need to
What should I do if I want to keep using serverless v3? Now it seems we are blocked by deploying our apps because even we are using v3 it is asking us to update to v4 and such. This is extremly annoying. If I have to migrate our process, why not migrate to SAM or CDK?
The process to switch to v4 is similar to what you would have had to do to switch to v3 from v2. Switching to SAM or CDK is far harder. You donāt need to āmigrate your processā. And V3 still works, nothing is blocking you from using it.
Besides that we donāt intend to depend on people purchasing licenses just because its hard to switch, but also because Serverless Framework is the best way to develop serverless applications. Its why we have no spent a huge amount of time and effort adding a ton of new features since v4 was launched, optmizing to improve the framework. Serverless Framework has not seen the kind of improvement to it that we are currently doing because now we are able to do so.
I had good experience using serverless before. Canāt understand why is so hard to separate login/dashboard/monitoring things from the framework. I donāt know a good example of paid framework that prospered after some time, especially if this changed over time.
The monitoring capabilities of Serverless Dashboard are entirely optional and require a significant process to onboard to.
Hi Suddenly I cannot deploy either and we needed to do a clean wipe on all our laptops to clear out a overly complicated authentication process. I do not want logging, AWS has ample dashboards on tracking. I want a simple way to ship microservices, and suddenly deploying an update has taken 3 days. But even worse it made my blood boil, why do you need to put your self in between me and AWS, it is meant a support package not a gatekeeper.
My main problem seems to be that your provider/ login key / license key was all tripping over each other and being written left and right, while storing old AWS credentials.
I need a help with serverless CLI, so running simple commands such as serverless or serverless print leads me to this error everytime.
my sls version is >V4
If you run āserverlessā on its own it will walk you through creating an account and logging in so that the message no longer occurs. You can have a free account and continue as normal.
hey @garethmcc, thank you for your response. Actually at that time even after running the serverless command same error was thrown by the framework. What I found was at that time I was using multiple sls accounts, one from organization, second from my other account and third this one, I was suppose to use the right keys to run this command.
Also, there is .serverlesssrc file which I deleted and after re-running the same command (sls), it created automatically and I was able to use the framework.
Having said that I donāt use the dashboard provided for sls-framework butā¦ I have seen I am currently been using 4 instances which is not true. And I tried to run sls reconcile over the command line, it was still showing the same list. I donāt want to get charged because I am trying some personal projects only. Any help or guidance can be provided?
You do not need to subscribe in order to use Serverless Framework V4 for free. You can just use V4 without adding payment details or subscribing. If you have not subscribed then Serverless cannot bill you for anything and there is no way for Serverless to know they should not be billing you if you have subscribed.
Ohh okay, thank you so much 
The recent changes to Serverless Framework v4ās authentication requirements present significant challenges for enterprise deployments.
Operational Challenge: CI/CD Pipeline Updates The primary operational issue organizations like ours will face is the need to modify our CI/CD pipelines to incorporate the new authentication step. With numerous Lambda functions deployed across AWS, weāll need to systematically update and test each deployment to ensure compatibility with Serverless v4.
Security and Compliance Concerns The more significant challenge involves customer communication and trust. Weāll need to explain to our customers that the new authentication process involves transmitting data about their AWS accounts to a third-party service. This disclosure will likely raise substantial security concerns and may require additional compliance reviews, potentially impacting our deployment timelines and customer relationships.
Strategic Considerations These operational complexities and security concerns would easily justify moving away from the Serverless Framework entirely, especially when alternative solutions like AWS CDK, Terraform, or AWS SAM can provide similar functionality without the third-party authentication requirements.