Menu
AWS CodeDeploy
User Guide (API Version 2014-10-06)

Create a Deployment Group (CLI)

To use the AWS CLI to create a deployment group, call the create-deployment-group command, specifying:

  • The application name. To view a list of application names, call the list-applications command.

  • A name for the deployment group. This name must be unique for each application associated with the deployment group.

  • Information about the tags or Auto Scaling group names that identify the instances to be included in the deployment group.

  • The Amazon Resource Name (ARN) identifier of the service role that allows AWS CodeDeploy to act on behalf of your AWS account when interacting with other AWS services. To get the service role ARN, see Get the Service Role ARN (CLI) . For more information about service roles, see Roles Terms and Concepts in IAM User Guide.

  • Information about the type of deployment, either an in-place deploment or blue/green deployment, to associate with the deployment group.

  • (Optional) The name of an existing deployment configuration. To view a list of deployment configurations, see View Deployment Configuration Details. If not specified, AWS CodeDeploy uses a default deployment configuration.

  • (Optional) Commands to create a trigger that pushes notifications about deployment and instance events to those who are subscribed to an Amazon Simple Notification Service topic. For more information, see Monitoring Deployments with Amazon SNS Event Notifications.

  • (Optional) Commands to add existing CloudWatch alarms to the deployment group that will be activated if a metric specified in an alarm falls below or exceeds a defined threshold.

  • (Optional) Commands for a deployment to roll back to the last known good revision when a deployment fails or a CloudWatch alarm is activated.

  • For in-place deployments:

    • (Optional) The name of the Classic load balancer in Elastic Load Balancing that will manage traffic to the instances during the deployment processes.

  • For blue/green deployments:

    • Configuration of the blue/green deployment process:

      • How new instances in the replacement environment are provisioned.

      • Whether to reroute traffic to the replacement environment immediately or wait a specified period for traffic to be rerouted manually.

      • Whether instances in the original environment should be terminated.

    • The name of the Classic load balancer in Elastic Load Balancing to be used for instances registered in the replacement environment.