You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*`AWS_CODE_DEPLOY_DEPLOYMENT_CONFIG_NAME` (optional): Deployment config name. By default: _CodeDeployDefault.OneAtATime_. Built-in options:
103
218
* CodeDeployDefault.OneAtATime
104
219
* CodeDeployDefault.AllAtOnce
220
+
* CodeDeployDefault.HalfAtATime
105
221
*`AWS_CODE_DEPLOY_MINIMUM_HEALTHY_HOSTS` (optional): The minimum number of healthy instances during deployment. By default: _type=FLEET_PERCENT,value=75_
@@ -137,14 +253,17 @@ This step consists to push the application to S3.
137
253
Environment Variables:
138
254
139
255
*`AWS_CODE_DEPLOY_S3_BUCKET` (required): The name of the S3 bucket to deploy the revision
140
-
*`AWS_CODE_DEPLOY_S3_KEY_PREFIX` (optional): A prefix to use for the file key. It's highly recommended to structure a bucket with a prefix per deployment group. This allows to limit stored revisions per deployment group. Note: A leading or trailing slash is not required. For example:
141
-
```
142
-
AWS_CODE_DEPLOY_S3_BUCKET="my-bucket-test"
143
-
AWS_CODE_DEPLOY_S3_KEY_PREFIX="production-www"
144
-
AWS_CODE_DEPLOY_S3_FILENAME="100#c3a5fea.zip"
256
+
*`AWS_CODE_DEPLOY_S3_KEY_PREFIX` (optional): A prefix to use for the file key. It's highly recommended to structure a bucket with a prefix per deployment group. This allows to limit stored revisions per deployment group. Note: A leading or trailing slash is not required.
145
257
146
-
# The resulting stored file would exist at s3://my-bucket-test/production-www/100#c3a5fea.zip
147
-
```
258
+
For example:
259
+
260
+
```
261
+
AWS_CODE_DEPLOY_S3_BUCKET="my-bucket-test"
262
+
AWS_CODE_DEPLOY_S3_KEY_PREFIX="production-www"
263
+
AWS_CODE_DEPLOY_S3_FILENAME="100#c3a5fea.zip"
264
+
265
+
# The resulting stored file would exist at s3://my-bucket-test/production-www/100#c3a5fea.zip
266
+
```
148
267
149
268
#### Step 8: Limiting Deploy Revisions per Bucket/Key
150
269
@@ -153,13 +272,17 @@ old revisions to help limit the size of the container. Large teams can quickly f
153
272
TBs/day depending on the projects. Since deployments typically don't need to store that many versions
154
273
backwards, this step will ensure that only N revisions exist, removing oldest revisions upon deploy.
155
274
156
-
> Note: If a limit is specified, the `ListObjects`IAM permission will need to be granted for the
275
+
> Note: If a limit is specified, the IAM permissions described below will need to be granted for the
157
276
specific s3://bucket/(key).
158
277
159
278
Environment Variables:
160
-
161
279
*`AWS_CODE_DEPLOY_S3_LIMIT_BUCKET_FILES` (optional): Number of revisions to limit. If 0, unlimited. By default: 0
0 commit comments