Template bundles - AWS Proton

Template bundles

Create AWS Proton infrastructure template bundles for automated serverless and containerized provisioning. Template bundles contain all of the information that AWS Proton requires to deploy and manage version controlled infrastructure-as-code resources in an automated, transparent, and repeatable manner. After a template bundle is created, it becomes part of your AWS Proton versioned template library.

As an administrator, you provide all of the information that AWS Proton needs in the following set of YAML-formatted files that make up a template bundle.

AWS Proton manages and deploys infrastructure resources through environments, services, service instances, and optional CICD service pipelines. Environments represent a set of shared resources that either you or developers deploy service instances to. Service instances run the developer's applications. When developers select a versioned service template bundle from the library, AWS Proton uses it to deploy and manage their applications.

The following diagram shows a process of how to create a template bundle that defines infrastructure resources for an environment or service. In this process, you identify the infrastructure resources, customization parameters, and resource-based parameters.

Customization parameters are parameters that require values that can only be provided when you deploy the service. One example of a customization parameter is a port number. A developer might need to provide the port number that a particular application requires access to. This number typically is different for different applications. By including the port number parameter, the template bundle can be re-used for applications that require access to different ports. By using parameters in this way, your template bundles can be used repeatably for different applications.

Resource-based parameters are associated with AWS Proton resources. For example, if you need to reference a resource defined in one template file, in another template file, you attach a name-space that associates it with an AWS Proton resource. For more information about these parameters, see Infrastructure template file parameters.

After you identify parameters, you then define a schema that serves as a customization parameter interface between AWS Proton and your infrastructure template files. Then, you use that schema when defining parameters as you build your infrastructure template files.

            A diagram that describes a process of how to create a template bundle for a set of AWS Proton infrastructure resources.