|
9 | 9 |
|
10 | 10 | AWS SDK for JavaScript CodeDeploy Client for Node.js, Browser and React Native.
|
11 | 11 |
|
12 |
| -<fullname>AWS CodeDeploy</fullname> |
13 |
| - |
14 |
| -<p>AWS CodeDeploy is a deployment service that automates application deployments to |
15 |
| -Amazon EC2 instances, on-premises instances running in your own facility, serverless AWS |
16 |
| -Lambda functions, or applications in an Amazon ECS service.</p> |
| 12 | +<p>CodeDeploy is a deployment service that automates application deployments |
| 13 | +to Amazon EC2 instances, on-premises instances running in your own facility, |
| 14 | +serverless Lambda functions, or applications in an Amazon ECS |
| 15 | +service.</p> |
17 | 16 | <p>You can deploy a nearly unlimited variety of application content, such as an updated
|
18 |
| -Lambda function, updated applications in an Amazon ECS service, code, web and |
19 |
| -configuration files, executables, packages, scripts, multimedia files, and so on. AWS |
20 |
| -CodeDeploy can deploy application content stored in Amazon S3 buckets, GitHub |
21 |
| -repositories, or Bitbucket repositories. You do not need to make changes to your |
22 |
| -existing code before you can use AWS CodeDeploy.</p> |
23 |
| -<p>AWS CodeDeploy makes it easier for you to rapidly release new features, helps you |
24 |
| -avoid downtime during application deployment, and handles the complexity of updating |
| 17 | +Lambda function, updated applications in an Amazon ECS service, |
| 18 | +code, web and configuration files, executables, packages, scripts, multimedia files, and |
| 19 | +so on. CodeDeploy can deploy application content stored in Amazon S3 |
| 20 | +buckets, GitHub repositories, or Bitbucket repositories. You do not need to make changes |
| 21 | +to your existing code before you can use CodeDeploy.</p> |
| 22 | +<p>CodeDeploy makes it easier for you to rapidly release new features, helps |
| 23 | +you avoid downtime during application deployment, and handles the complexity of updating |
25 | 24 | your applications, without many of the risks associated with error-prone manual
|
26 | 25 | deployments.</p>
|
27 | 26 | <p>
|
28 |
| -<b>AWS CodeDeploy Components</b> |
| 27 | +<b>CodeDeploy Components</b> |
29 | 28 | </p>
|
30 |
| -<p>Use the information in this guide to help you work with the following AWS CodeDeploy |
31 |
| -components:</p> |
| 29 | +<p>Use the information in this guide to help you work with the following CodeDeploy components:</p> |
32 | 30 | <ul>
|
33 | 31 | <li>
|
34 | 32 | <p>
|
35 | 33 | <b>Application</b>: A name that uniquely identifies
|
36 |
| -the application you want to deploy. AWS CodeDeploy uses this name, which |
| 34 | +the application you want to deploy. CodeDeploy uses this name, which |
37 | 35 | functions as a container, to ensure the correct combination of revision,
|
38 | 36 | deployment configuration, and deployment group are referenced during a
|
39 | 37 | deployment.</p>
|
40 | 38 | </li>
|
41 | 39 | <li>
|
42 | 40 | <p>
|
43 | 41 | <b>Deployment group</b>: A set of individual
|
44 |
| -instances, CodeDeploy Lambda deployment configuration settings, or an Amazon ECS |
45 |
| -service and network details. A Lambda deployment group specifies how to route |
46 |
| -traffic to a new version of a Lambda function. An Amazon ECS deployment group |
47 |
| -specifies the service created in Amazon ECS to deploy, a load balancer, and a |
48 |
| -listener to reroute production traffic to an updated containerized application. |
49 |
| -An EC2/On-premises deployment group contains individually tagged instances, |
50 |
| -Amazon EC2 instances in Amazon EC2 Auto Scaling groups, or both. All deployment |
51 |
| -groups can specify optional trigger, alarm, and rollback settings.</p> |
| 42 | +instances, CodeDeploy |
| 43 | +Lambda deployment configuration settings, or an Amazon ECS |
| 44 | +service and network details. A Lambda deployment group specifies how |
| 45 | +to route traffic to a new version of a Lambda function. An Amazon ECS deployment group specifies the service created in Amazon ECS to deploy, a load balancer, and a listener to reroute production |
| 46 | +traffic to an updated containerized application. An Amazon EC2/On-premises deployment group contains individually tagged instances, Amazon EC2 instances in Amazon EC2 Auto Scaling groups, or both. All |
| 47 | +deployment groups can specify optional trigger, alarm, and rollback |
| 48 | +settings.</p> |
52 | 49 | </li>
|
53 | 50 | <li>
|
54 | 51 | <p>
|
55 | 52 | <b>Deployment configuration</b>: A set of deployment
|
56 |
| -rules and deployment success and failure conditions used by AWS CodeDeploy |
57 |
| -during a deployment.</p> |
| 53 | +rules and deployment success and failure conditions used by CodeDeploy during a deployment.</p> |
58 | 54 | </li>
|
59 | 55 | <li>
|
60 | 56 | <p>
|
61 | 57 | <b>Deployment</b>: The process and the components used
|
62 |
| -when updating a Lambda function, a containerized application in an Amazon ECS |
63 |
| -service, or of installing content on one or more instances. </p> |
| 58 | +when updating a Lambda function, a containerized application in an |
| 59 | +Amazon ECS service, or of installing content on one or more |
| 60 | +instances. </p> |
64 | 61 | </li>
|
65 | 62 | <li>
|
66 | 63 | <p>
|
67 |
| -<b>Application revisions</b>: For an AWS Lambda |
68 |
| -deployment, this is an AppSpec file that specifies the Lambda function to be |
69 |
| -updated and one or more functions to validate deployment lifecycle events. For |
70 |
| -an Amazon ECS deployment, this is an AppSpec file that specifies the Amazon ECS |
71 |
| -task definition, container, and port where production traffic is rerouted. For |
72 |
| -an EC2/On-premises deployment, this is an archive file that contains source |
73 |
| -content—source code, webpages, executable files, and deployment scripts—along |
74 |
| -with an AppSpec file. Revisions are stored in Amazon S3 buckets or GitHub |
75 |
| -repositories. For Amazon S3, a revision is uniquely identified by its Amazon S3 |
76 |
| -object key and its ETag, version, or both. For GitHub, a revision is uniquely |
| 64 | +<b>Application revisions</b>: For an Lambda deployment, this is an AppSpec file that specifies the |
| 65 | +Lambda function to be updated and one or more functions to |
| 66 | +validate deployment lifecycle events. For an Amazon ECS deployment, this |
| 67 | +is an AppSpec file that specifies the Amazon ECS task definition, |
| 68 | +container, and port where production traffic is rerouted. For an EC2/On-premises |
| 69 | +deployment, this is an archive file that contains source content—source code, |
| 70 | +webpages, executable files, and deployment scripts—along with an AppSpec file. |
| 71 | +Revisions are stored in Amazon S3 buckets or GitHub repositories. For |
| 72 | +Amazon S3, a revision is uniquely identified by its Amazon S3 object key and its ETag, version, or both. For GitHub, a revision is uniquely |
77 | 73 | identified by its commit ID.</p>
|
78 | 74 | </li>
|
79 | 75 | </ul>
|
80 | 76 | <p>This guide also contains information to help you get details about the instances in
|
81 |
| -your deployments, to make on-premises instances available for AWS CodeDeploy |
82 |
| -deployments, to get details about a Lambda function deployment, and to get details about |
83 |
| -Amazon ECS service deployments.</p> |
| 77 | +your deployments, to make on-premises instances available for CodeDeploy |
| 78 | +deployments, to get details about a Lambda function deployment, and to get |
| 79 | +details about Amazon ECS service deployments.</p> |
84 | 80 | <p>
|
85 |
| -<b>AWS CodeDeploy Information Resources</b> |
| 81 | +<b>CodeDeploy Information Resources</b> |
86 | 82 | </p>
|
87 | 83 | <ul>
|
88 | 84 | <li>
|
89 | 85 | <p>
|
90 |
| -<a href="https://docs.aws.amazon.com/codedeploy/latest/userguide">AWS CodeDeploy |
91 |
| -User Guide</a> |
| 86 | +<a href="https://docs.aws.amazon.com/codedeploy/latest/userguide">CodeDeploy User Guide</a> |
92 | 87 | </p>
|
93 | 88 | </li>
|
94 | 89 | <li>
|
95 | 90 | <p>
|
96 |
| -<a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/">AWS |
97 |
| -CodeDeploy API Reference Guide</a> |
| 91 | +<a href="https://docs.aws.amazon.com/codedeploy/latest/APIReference/">CodeDeploy API Reference Guide</a> |
98 | 92 | </p>
|
99 | 93 | </li>
|
100 | 94 | <li>
|
101 | 95 | <p>
|
102 |
| -<a href="https://docs.aws.amazon.com/cli/latest/reference/deploy/index.html">AWS |
103 |
| -CLI Reference for AWS CodeDeploy</a> |
| 96 | +<a href="https://docs.aws.amazon.com/cli/latest/reference/deploy/index.html">CLI Reference for CodeDeploy</a> |
104 | 97 | </p>
|
105 | 98 | </li>
|
106 | 99 | <li>
|
107 | 100 | <p>
|
108 |
| -<a href="https://forums.aws.amazon.com/forum.jspa?forumID=179">AWS CodeDeploy |
109 |
| -Developer Forum</a> |
| 101 | +<a href="https://forums.aws.amazon.com/forum.jspa?forumID=179">CodeDeploy Developer Forum</a> |
110 | 102 | </p>
|
111 | 103 | </li>
|
112 | 104 | </ul>
|
|
0 commit comments