Does the S3 bucket it is trying to make already exist? Remember that buckets need to be globally unique, in other words no other bucket with that name anywhere in the world must exist.
Thank you so much for your prompt response and greatly appreciated.
I do understand, but the problem over here, in personal AWS account works well and able to invoke lambda from from remotely after performing the command serverless deploy.
the same repository doesn’t work when I try to deploy in my work - organization aws account using serverless deploy -v.
Please see below and ITS REALLY URGENT AND YOUR HELP WILL BE GREATLY APPRECIATED,
If the S3 bucket name is the same when deploying to your account as when deploying to the work account, that is the problem. S3 bucket names need to be globally unique; i.e. across AWS accounts and across regions. For example, if you tried to create a bucket with the same name as a bucket I have created, you will get an error.
One way to get past this error when naming things that will be used local and in dev and in prod, etc is to add the stage (dev, prod, local) to the bucket name using ${opt:stage) and then passing the stage as an option with the deploy command: severless deploy --stage dev
If I understand correctly, serverless framework generating some unique bucket examples - my-test-project-prod-serverlessdeploymentbucket-ogmc9oi0007q (was generated when I deploy to my personal AWS account - assuming aws is generating random bucket to make it unique - COULD SOME ONE CORRECT ME IF MY UNDERSTANDING IS INCORRECT?) for each deploy.
When I deploy the same code to my official account, I’m getting the below error,
When I go and check CloudTrail and CloudWatch, I don’t find any logs. I really don’t understand, should give some logs about errors right? At least these logs may help to debug and analyze.
I really don’t understand what’s really causing in this scenario and did anyone come across this scenario and HELP ME IN UNDERSTANDING WHAT"S HAPPENING?