We're going to run through an example of deploying a serverless project to a pre-production environment, running some tests, and then deploying to production via an approval gate. We are using the "all at once" method of deployment and will be using the same account for all of our environments. The environments will be separated by using different CloudFormation stacks and different API Gateway stages and endpoints.
For a real production environment, you would want to have entirely separate AWS accounts for development, pre-production or staging, and production. This allows for a greater separation of IAM permissions and duties. It also means that if any account resource limits are reached because of a ...
