Deployment artifact

Q: How deeply does Amazon Web Services in Action, Third Edition: An in-depth guide to AWS cover deployment artifact?

Explains archive contents, S3 storage, deployment commands, lifecycle hooks, and package-size effects on Lambda cold starts.

As explained in Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

A deployment artifact is a packaged archive containing the code, scripts, configuration, and instructions required to release software.

A deployment artifact is a packaged archive containing the code, scripts, configuration, and instructions required to release software. In AWS workflows, it is commonly a ZIP file stored in Amazon S3 and consumed by services such as Lambda or CodeDeploy. section 6.3.5 section 15.1

A typical deployment-artifact workflow has these steps:

Assemble application code, dependencies, scripts, configuration, and deployment instructions into an archive. section 15.1
Upload the archive to an S3 bucket and reference it from the deployment configuration. section 6.3.5 section 15.1
Use SAM, CloudFormation, or CodeDeploy to distribute the archive and configure its target resources. section 6.3.5 section 15.1
Let the target agent or service execute included instructions, copy application files, and report deployment status. section 15.1

Lambda package with SAM

Create an S3 bucket, package the Lambda template and deployment archive, then deploy the generated CloudFormation template. The resulting stack configures the function and its dependencies, including IAM and event resources. section 6.3.5

$ aws cloudformation package --template-file template.yaml \
  --s3-bucket ec2-owner-tag-$yourname --output-template-file output.yaml

Package a SAM template and upload its deployment package to S3, producing an output template that references the uploaded artifact. section 6.3.5

aws deploy create-deployment --application-name etherpad-codedeploy \
 --deployment-group-name etherpad-codedeploy \
 --revision "revisionType=S3,
 s3Location={bucket=$BucketName,
 key=etherpad-lite-1.8.17.zip,bundleType=zip}"

Create a CodeDeploy deployment from a ZIP revision stored in S3, selecting the application and deployment group. section 15.1

Artifact size affects Lambda cold-start time because AWS must download and initialize the package. Keeping the archive small can reduce latency, while CodeDeploy artifacts can carry lifecycle hooks such as installation, startup, and validation scripts. section 6.4.1 section 15.1

How Amazon Web Services in Action, Third Edition: An in-depth guide to AWS covers it

Cover of Amazon Web Services in Action, Third Edition: An in-depth guide to AWS

liveBook manning.com

Read Amazon Web Services in Action, Third Edition: An in-depth guide to AWS on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Learn Docker in a Month of Lunches, Second EditionA deployable artifact is a tested software package or image that is ready to be deployed.

Compare how 2 books explain deployment artifact →

Related concepts

deployment pipelineproduced by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
container imageincludes · A container image is a packaged filesystem and configuration artifact from which a container can be created and run.
object storeuses · An object store is a storage system that stores and retrieves data as independently addressable objects containing content and associated metadata.
dacpacincludes · A DACPAC is a SQL Server data-tier application package containing definitions of database objects for schema deployment.
continuous integrationproduced by · Continuous integration is a software development practice in which code changes are integrated frequently into a shared codebase and automatically validated.

This explainer was generated by Manning's knowledge graph from the text of Amazon Web Services in Action, Third Edition: An in-depth guide to AWS. The section links point to the parts of the book it draws on.