Please enable JavaScript.
Coggle requires JavaScript to display documents.
M9 Automation (beanstalk (environment that will handle (capacity planing,…
M9 Automation
beanstalk
-
-
-
support app develop underJava, Node.js, PHP, Phyton, Ruby
-
-
Opswork
-
type
Opwork stack
feature
-
Also can use Opswork chef and puppet to launch your EC2, RDS and ELB
Can run in VPC & support auto scaling, cloudwatch
-
You can define the application’s architecture, including package and programming languages installation, software configuration and resources such as storage.
Software version control
1.Can retrieve the code you want to deploy from common version control systems like Git and Subversion as well as HTTP and private or public S3 bundles.
For example, you can deploy a specific version of your application by adding the version or branch from your Git repository into your OpsWorks Stacks app definition.
-
-
limitation
O/S supported
mazon Linux, Ubuntu 12.04 LTS, Ubuntu 14.04 LTS, and Windows Server 2012 R2.
-
-
-
-
stack
-
-
-
Instead manuall config this, configure chef or puppet to automate
demo
layers
-
can add receiipe to configure, deploy, shutdown the app
JSON template
AWS OpsWorks Stacks uses templates to create files such as configuration files, If you use custom JSON or custom cookbook attributes to override the AWS OpsWorks Stacks definitions, your preferred settings are incorporated into the configuration files in place of the AWS OpsWorks Stacks settings. However, AWS OpsWorks Stacks does not necessarily specify an attribute for every possible configuration setting; it accepts the defaults for some settings and hardcodes others directly in the template. You can't use custom JSON or custom cookbook attributes to specify preferred settings if there is no corresponding AWS OpsWorks Stacks attribute.
-
-
deletion policy
eleting a stack on CloudFormation also removes all the provisioned resources in it. In some cases, you want
some resources to be retained even after deleting its stack. The good thing is that you can do this by defining
-
This is pretty straightforward - you just need to define DeletionPolicy with Retain value and for the resources
that support snapshot, (like RDS databases) you can set Snapshot as its value. With DeletionPolicy: Snapshot, a
snapshot is created before a resource is deleted. This allows you to have a backup of the resource that's been
-
Let’s say for example that you want to delete a deployed application. This app uses S3 for storing its object
and RDS as its database, and you want to keep a copy of this resource as your reference. You may want to
update its stack and add DeletionPolicy: Retain for S3 and DeletionPolicy: Snapshot for RDS before deleting it.
By default, deleting a stack will also delete its provisioned resources like the AWS::S3::Bucket that was
-
-