search

aws-samples / aws-saas-factory-ref-solution-serverless-saas

MIT No Attribution
459 stars 153 forks source link

Can't find anything on AWS Console after successful run of deployment.sh #33

Closed lwang168 closed 2 years ago

lwang168 commented 2 years ago

I was able to run deployment.sh successful, and can access Admin/Application/Landing URLs, but when I go to CodePipeline on AWS Console, I don't see any pipeline/build/deployment. What am I missing?

anubhavynr commented 2 years ago

Hi - What do you see on the Cloudformation console? Do you see any stack being created there?

lwang168 commented 2 years ago

Thanks for the response. I do see multiple stacks on the CloudFormation console.

ujwalbukka commented 2 years ago

@lwang168 - In the Cloudformation console, do you see a stack with name "serverless-saas-pipeline" successfully completed? This is the stack which takes care of creating codepipeline.

lwang168 commented 2 years ago

Yes, with the status "UPDATE_COMPLETE".

This is what happened. The first time I ran deployment.sh, it failed, but I remember I saw entries in CodePipeline build/deployment/pipeline. I deleted them.

Then I fixed issues from prior runs, and re-ran deployment.sh successfully, but no entries in CodePipeline. Is this expected behavior? How do I re-create entries in CodePipeline?

ujwalbukka commented 2 years ago

If "serverless-saas-pipeline" stack has completed successfully then the code pipeline might have created. Are you looking in the correct region? In the AWS console go the CodePipeline service in the same region where you have deployed the Serverless SaaS Reference solution then in the left menu under "Pipeline" click on "Pipelines" and you should see it.

You can redeploy code pipeline by just running the code in deployment.sh from L18 to L22

lwang168 commented 2 years ago

Thanks for your help. I believe I use the same region us-east-1. See attached screenshots of CloudFormation and CodePipeline.

CloudFormation CodePipeline

ujwalbukka commented 2 years ago

Did you tried redeploying the 'serverless-saas-pipeline' stack? If possible delete the 'serverless-saas-pipeline' stack first and then redeploy.

You can redeploy by just running the code in deployment.sh from L18 to L22 Or you can just rerun the whole deployment.sh script.

lwang168 commented 2 years ago

It works by deleting "serverless-saas-pipeline" stack and redeploying. Thanks for the help.

ujwalbukka commented 2 years ago

Closing this issue. Please reopen if you still have any issues/questions.