During onboarding, AWS Managed Services (AMS) works with you to determine the infrastructure that you need.
The basic infrastructure includes an AWS virtual private cloud (VPC), communication security via an ADFS forest trust, the basic subnets (DMZ, Shared Services, and Private) mirrored across two availability zones and configured with a managed NAT, bastions, public load balancers, AWS Direct Connect (DX), and required security. Your application resources will be deployed in your private, or customer-applications, subnet. You can learn more about a typical AMS architecture in the AWS Managed Services User Guide.
The infrastructure you deploy once the basics are done, should include all components for your applications and application development.
Application deployment capabilities in AMS
Some of the ways you can deploy applications in AMS. Details on each method follow.
Method Name | Infrastructure Deployment | AMI or Key Element(s) | Application Install |
---|---|---|---|
Mutable Applications, AMS AMI |
|||
Manual application deployment |
Full stack CT or Tier and Tie CTs |
AMS-provided AMI |
Submit Access management CT, install application manually. |
UserData application deployment with application agent (i.e. Chef, Puppet, etc.) |
Use provisioning CT with UserData scripting that installs an application agent, and that script/agent installs the application. |
||
UserData agentless application deployment (i.e. Ansible, Salt SSH, etc.) |
Submit Access management CT, install application agent. Deploy application with application deploy tooling. |
||
Mutable Applications, Custom AMI | |||
Custom AMI application deployment (non-ASG) |
Full stack CT or Tier and Tie CTs |
Custom AMI. AMS AMI -> customize with application deploy tooling agent -> create EC2 instance (CT) -> create AMI (CT). |
Application deploy tooling (i.e. Chef), leveraging agents, deploys application. |
AWS Database Migration Service (DMS) application deployment |
AWS DMS sync to existing AMS Relational Database stack. |
Custom AMI |
Customer or partner employs AWS Database Migration Service; AMS verifies AMS components on launch |
Workload Ingest application deployment |
Partner-migrated instance/AMI and customer-initiated Workload Ingest CT. |
Partner migrates instance, creates AMI in customer AMS-managed VPC; customer uses Workload Ingest CT to launch stack in AMS. For details, see AMS Workload Ingest (WIGS). |
|
Immutable Applications | |||
Custom AMI application deployment (ASG) |
Full stack CT or Tier and Tie CTs |
AMS AMI -> customize -> create EC2 instance (CT) -> create AMI (CT) -> create Auto Scaling group. |
Auto Scaling deploys application with the custom AMI For details, see Tier and Tie App Deployments in AMS. |
Mutable or Immutable Applications | |||
Custom CloudFormation Template application deployment |
CloudFormation template |
AWS CloudFormation template -> customize/prepare for AMS -> Deployment | Ingestion | Stack from CloudFormation Template | Create (ct-36cn2avfrrj9v). |
AMS deploys your application to your account using your custom CloudFormation template, and validates the application deployment. For details, see AMS CloudFormation ingest. |
SQL Database Import |
AMS operations (Other | Other CT) |
On premise SQL database -> .bak file -> AMS RDS SQL database -> Management | Other | Other | Create (ct-1e1xtak34nx76) for the import. |
AMS imports your on-premises database to your AMS-managed RDS database. For details, see Database (DB) import to AMS RDS for Microsoft SQL Server. |
Database Migration Service (DMS) |
AMS operations (Multiple CTs) |
On premise database -> DMS replication instance -> DMS replication subnet group -> DMS target endpoint -> DMS source endpoint -> DMS replication task. |
AMS imports your on-premises database to your AMS-managed S3 or target RDS database. For details, see AWS Database Migration Service (AWS DMS). |
CodeDeploy application deployment |
CodeDeploy |
Application -> CodeDeploy application -> CodeDeploy deployment group -> CodeDeploy deployment. | Depending on usage, In-place or Blue/Green application deployment. For details, see CodeDeploy requests. |