AWS Proton introduces service components
[AWS Proton](/proton/) introduces service components, a new feature that allows developers complement the standard infrastructure of Proton templates with additional resources for their services. Platform engineers use Proton to define the core infrastructure of their services and keep it consistent and updated across services, and now with components developers can complement that core infrastructure with the additional resources they need to meet the needs of their particular application. Proton components enable platform engineers to expand the use cases they support without having to drastically increase the number of templates that they manage. AWS Proton is a managed service for platform engineers to increase the pace of innovation by defining, vending, and maintaining infrastructure templates for self-service deployments. With Proton, customers can standardize centralized templates to meet security, cost, and compliance goals. Proton helps platform engineers scale up their impact with a self-service model, resulting in higher velocity for the development and deployment process throughout an application lifecycle. Developers can create a component by providing their infrastructure-as-code template, and then associating the component with their service. Platform engineers can configure a specific IAM role to provision components, ensuring that they control what types of resources are available as part of components. Developers can define outputs as part of their components definition and Proton makes them available to be use in the service template, so that the infrastructure defined in the components can be integrated into the service - for example, a developer can create an S3 bucket and a policy to grant access to it, and then pass the name and policy to a Fargate-based service instance, enabling access to the bucket. To learn more about how to use Proton components, read [here](https://docs.aws.amazon.com/proton/latest/adminguide/ag-components.html).