Title

AWS re:Invent 2022 - AWS infrastructure as code: A year in review (DOP201)

Summary

AWS Infrastructure as Code (IaC) portfolio includes more than CloudFormation, with services built on top of the CloudFormation engine.
AWS is working on the resource foundation layer, which is critical for future roadmap development.
Industry trends show enterprises using IaC at scale, evolving personas, and implementing best practice checks and policy as code.
AWS IaC tools manage both AWS and non-AWS services, with a focus on openness and flexibility.
CloudFormation Resource Registry is the foundation of AWS's IaC portfolio, ensuring service coverage and consistency.
Cloud Control API provides a standard API interface for all AWS services supported by the registry.
AWS organizations now have CloudFormation support for managing accounts, organizational units, and policies.
AWS has launched 50 new resource providers for third-party solutions like CloudFlare, GitLab, and PagerDuty.
The future focus includes improving resource coverage, performance, CDK enterprise adoption, and deployment visibility.
Control Tower has launched opinionated controls using CloudFormation Guard for proactive and detective controls.
AWS is committed to solving the resource model for the entire industry, aiming for day-one support for new services across various IaC tools.

AWS recognizes the importance of IaC for managing complex and scalable cloud environments and is investing in expanding its portfolio beyond CloudFormation.
The CloudFormation Resource Registry and Cloud Control API are strategic initiatives to ensure consistency and coverage across all AWS services, which is crucial for customer adoption and usage.
The integration of third-party resource providers into the CloudFormation registry indicates AWS's commitment to supporting multi-cloud and hybrid cloud environments.
The focus on industry trends such as platform engineering, GitOps, DevOps, and the influence of application developers on infrastructure design suggests AWS is aligning its services with modern software development practices.
AWS's emphasis on policy as code and the shift-left approach to governance indicates a strong focus on security and compliance within the IaC domain.
The mention of CDK and its adoption reflects the growing trend of developers preferring familiar programming languages and tools for defining infrastructure.
AWS's commitment to improving deployment visibility and performance indicates a response to customer feedback and a desire to enhance the user experience for cloud deployments.
The collaboration with partners like Terraform, Pulumi, and Ansible to support Cloud Control API demonstrates AWS's openness to community and industry collaboration, ensuring that customers have flexibility in their choice of IaC tools.