This application deployment strategy is a simple and manual update of application instances. These are the basic steps.
IDs for all CT options can be found in the Change Type Reference.
Note
Currently, you must use Amazon S3 storage with this solution.
The basic steps are outlined here; the various procedures are detailed in the AMS User Guide.
Create an Amazon S3 storage bucket. CT: ct-1a68ck03fn98r. The S3 bucket must have versioning enabled (for information on doing this, see Enabling Bucket Versioning).
Put your bundled application artifacts on it (everything your application needs to start on boot and work). You can do this with the Amazon S3 console without requesting access through AMS. Or using a variation of this command:
aws s3 cpZIP_FILEPATH_AND_NAMEs3://S3BUCKET_NAME/Find an AMS AMI, all will have CodeDeploy on them. To find a "customer-" AMI use either:
AMS Console: The VPC details page for the relevant VPC
AMS API For the AMS SKMS API reference, see the Reports tab in the AWS Artifact Console. or CLI:
aws amsskms list-amis
Create an EC2 instance with that AMI. CT: ct-14027q0sjyt1h. Specify the AMS AMI, set a tag
Key=backup, Value=trueand specify thecustomer-mc-ec2-instance-profilefor theInstanceProfileparameter. Note the instance ID that is returned.Request admin access to the instance. CT: ct-1dmlg9g1l91h6. You'll need the FQDN for your account. If you’re unsure what your FQDN is, you can find it by:
Using the AWS Management Console for Directory Services (under Security and Identity) Directory Name tab.
Running one of these commands (return directory classes; DC+DC+DC=FQDN): Windows:
whoami /fqdnor Linux:hostname --fqdn.
Log into the instance, see Accessing Instances via Bastions in the AMS User Guide.
Download your bundled application files from your S3 bucket to the instance.
Request an immediate backup with a service request to AMS, you will need to know the instance ID.
When you need to update your application, load new files to your S3 bucket and then follow steps 3 through 8.
