AWS Proton makes new fields available for Jinja parametrization
AWS Proton has made two new fields_, service_instance_ and service_instance_name, available as inputs for the Jinja parametrization of templates. Template writers can use these fields to name individual resources in the template without requiring additional inputs from developers.
AWS Proton has made two new fields_, service_instance_ and service_instance_name, available as inputs for the Jinja parametrization of templates. Template writers can use these fields to name individual resources in the template without requiring additional inputs from developers.
Previously, template writers and developers faced the challenge of creating multiple unique identifiers when naming resources. With today’s feature release, you can refer to service_name and service_instance_name in your templates, and AWS Proton will automatically inject the corresponding value. For example, you can uniquely name resources, such as Log Groups, using the provided service instance name. This will facilitate consistent naming standards and further reduce the number of required parameters.
You can read more about creating AWS Proton templates in our documentation. To get started with AWS Proton, visit our product page.