Application development processes and practices that enable effective design and deployment of applications into an AWS Managed Services (AMS) environment. AMS guides you through the following high level process:
Envision and architect an application to be developed or integrated to your AMS-managed environment. Some considerations:
How will you deploy your application? With automation using a deployment tool such Ansible, or manually by directly uploading needed files?
How will you update your application? With a mutable approach updating each instance separately, or with an immutable approach updating each instance with a single, updated, AMI in an Auto Scaling group?
Plan and architect the infrastructure that will be used to host the application using AWS architecture libraries, AWS "Well-Architected" guidance, and AMS and other cloud architecture subject matter experts. The following sections of this guide provide information that can help with this.
Select an infrastructure deployment approach:
Full Stack: All infrastructure components are deployed at once, together.
Tier and Tie: Infrastructure deployments are deployed separately and, after, tied together with security group modifications. This type of deployment is also achieved by a serial configuration of stack components that builds upon each other; for example, specifying the load balancer that you previously created when you create an Auto Scaling group.
What environments, such as Dev, Staging, and Prod, will you employ?
Choose AMS change types (CTs) that will provision the necessary stacks, or tiers, and prepare the necessary requests for change (RFCs).
Submit the RFCs to trigger the deployment of the infrastructure to the appropriate environment.
Deploy the application using the application deployment approach selected.
Re-work infrastructure and applications as needed.
Deploy infrastructure and applications to appropriate follow-on environments, assuming your first deployment is to a non-production environment.
Ongoing maintenance is handled by AMS operating the underlying infrastructure, and your operations teams operating the application(s) infrastructures.
To decommission an application, terminate the AMS infrastructure for it.
