Production environment

The production environment supports the released product, handling real data by real clients. This is a protected environment that is assigned access by least privilege and elevated access should only be allowed through an audited exception process for a limited period of time.

Access

In the production environment, developers should have limited, read-only access in the AWS Management Console. For example, developers should be able to access log data for day-to-day operations. All releases to production should be gated by an approval step prior to deployment.

Build steps

None. The same artifacts that were used in the testing and staging environments are reused in the production environment.

Deployment steps

Automatically initiate deployment of the release branch (Gitflow) or the main branch (Trunk or GitHub Flow) in the production environment after approval and deployment in the staging environment. The following are the deployment steps in the production environment: