In today’s cloud-first environment, Infrastructure as Code (IaC) has become crucial for managing cloud resources effectively. However, organizations often face significant challenges in adopting IaC practices, including steep learning curves, complex syntax requirements, and difficulty translating manual operations into code. Amazon Q Developer‘s Console-to-Code feature addresses these challenges by providing an intuitive bridge between manual AWS Console operations and infrastructure as code. This innovative solution helps organizations accelerate their automation journey while maintaining consistency and reliability in AWS deployments. Understanding Amazon Q Developer and Console-to-Code Console-to-Code is a feature of Amazon Q Developer that helps automate AWS infrastructure by recording manual actions performed in the AWS Management Console and converting them into infrastructure-as-code (IaC). It leverages generative AI to generate automation-ready code, allowing users to transition from manual operations to repeatable deployments effortlessly. Console-to-Code provides multi-language support, offering code generation in AWS Cloud Development Kit (CDK) formats such as Java, Python, and TypeScript, as well as AWS CloudFormation in JSON and YAML formats. Console-to-Code records your console actions, then uses generative AI to suggest code in your preferred language and format. In this blog post, we’ll explore how Console-to-Code can help you: Transform manual console actions into reusable infrastructure code Improve operational efficiency and reduce human error Accelerate the transition from manual to automated deployments Supported AWS Services Console-to-Code currently supports automation for several essential AWS services. These include Amazon EC2, which allows for the provisioning and management of virtual machines; Amazon VPC, which enables configuration of networking components such as subnets, route tables, and gateways; and Amazon RDS, which facilitates the management of database instances, configurations, and scaling options Potential Use Cases: Now that we’ve covered the basics of Console-to-Code and its supported services, let’s explore some potential use cases for this feature. DevOps and Agile Development In the fast-paced world of DevOps and agile development, Console-to-Code enables teams to rapidly prototype and iterate on infrastructure configurations. The ability to quickly create and replicate consistent environments across development, staging, and production stages ensures infrastructure reliability while maintaining agile velocity. Compliance-Focused Industries Organizations in regulated industries benefit from Console-to-Code’s systematic approach to implementing and maintaining compliant infrastructure. By recording proven, compliant configurations, organizations ensure that all subsequent deployments maintain the same level of security and compliance, creating an automatic audit trail for regulatory requirements. Step-by-Step Guide to Using Console-to-Code Follow these steps to automate AWS services using Amazon Q Developer’s Console-to-Code feature: Prerequisites Before getting started with Amazon Q Developer’s Console-to-Code feature, ensure you have the following: Service Access: AWS Management Console access Access and permissions to supported AWS services such as: Amazon EC2, Amazon VPC, and Amazon RDS Required Permissions: The q:GenerateCodeFromCommands permission for Amazon Q Developer to use Console-to-Code (added by default, no additional requirement from the user) Subscription Tiers: Free Tier: No fixed monthly limit for recording console actions No fixed monthly limit for generating CLI commands Monthly limit applies to AWS CDK and CloudFormation code generation Pro Tier: Requires IAM Identity Center authentication IAM Identity Center identity must be subscribed to Amazon Q Developer Pro No fixed monthly limit for AWS CDK or CloudFormation code generation For this demonstration the Free Tier would suffice. Supported Code Formats: Console-to-Code can generate infrastructure-as-code in the following formats: AWS CDK: Java, Python, and TypeScript AWS CloudFormation: JSON and YAML Getting Started Step 1: Start Recording To start recording with Console-to-Code, follow these steps: Sign in to the AWS Management Console. Navigate to the console of one of the supported services (Amazon VPC, Amazon RDS, or Amazon EC2) On the right edge of the browser window, choose the Console-to-Code icon. Click Start recording. Note: While recording actions is free, you will still be charged for any AWS resources created during the recording process. Figure 1: Opening the Console-to-Code panel and starting a recording session in the VPC console. Step 2: Perform Actions in AWS Console Go to the AWS service (e.g., EC2, S3) you want to automate. Perform desired actions such as launching an EC2 instance or creating an S3 bucket. Figure 2: Demonstration of creating and configuring resources while Console-to-Code records all actions in real-time. The Console-to-Code panel will record all of these actions as you perform them. You can move between different service consoles (such as VPC and EC2) during a single recording session, allowing you to create a comprehensive recording that involves actions across multiple supported services Step 3: Generate Code & Stop Recording In the Console-to-Code panel, review your recorded actions. You can filter the recorded actions using the dropdown, search box, or filter widget at the top of the Console-to-Code panel. Select the actions that you want to convert into code. Only the actions with checked boxes will be used in the following steps. Indicate the type of code that you want to generate. From the reverse dropdown menu at the lower right of the Console-to-Code panel, select the language and (if applicable) format of the code to be generated. Choose Generate chosen language. The generated code will appear, along with the equivalent CLI commands. Figure 3: Stopping the recording, selecting desired actions, and generating infrastructure code in your preferred language through the Console-to-Code panel. Benefits of Using Console-to-Code The implementation of Console-to-Code offers numerous advantages to AWS users. It increases time efficiency by reducing manual effort on repetitive console tasks and ensures consistency and compliance with organizational security and governance policies. The tool minimizes human errors through the generation of syntactically accurate infrastructure code, enables rapid prototyping for quick transitions from experimentation to production, and serves as a valuable learning resource for new AWS users to understand infrastructure-as-code best practices Best Practices Planning and Organization Success with Console-to-Code requires thorough planning and organization. Document your infrastructure requirements comprehensively, establish clear naming conventions and tagging strategies, and maintain a systematic approach to version control for generated code. Maintenance and Updates Regular review and testing of generated code ensure continued reliability and efficiency. Implement a code review process for infrastructure changes and maintain comprehensive documentation of your deployment patterns and configurations. Troubleshooting Guidelines Common issues during recording sessions can often be resolved by using a single browser tab and ensuring proper permissions are in place. For code generation issues, validate service compatibility and review action sequences carefully. Clear browser cache and verify IAM permissions when encountering persistent issues. Conclusion Amazon Q Developer’s Console-to-Code represents a significant advancement in infrastructure automation, making IaC accessible to teams of all skill levels. By following the strategies and best practices outlined in this guide, organizations can effectively leverage this tool to accelerate their cloud journey while maintaining security, compliance, and operational excellence. The future of infrastructure automation looks promising with tools like Console-to-Code, enabling organizations to focus more on innovation and less on manual operations. As AWS continues to enhance this feature, users can expect even more capabilities and integrations to support their infrastructure automation needs. Ready to accelerate your infrastructure automation journey? Start exploring Console-to-Code today by signing into your AWS Management Console and recording your first infrastructure deployment. For additional resources and documentation, visit the AWS Console-to-Code documentation page. About the Authors: Adeogo Olajide Adeogo is a Solutions Architect at AWS, where he supports GovTech customers and other public sector customers in their cloud transformation journey. He specializes in designing secure, scalable, and compliant architectures that help public sector organizations modernize their digital services. Outside of work, he enjoys playing and watching soccer. Jehu Gray Jehu Gray is a Prototyping Architect at Amazon Web Services where he helps customers design solutions that fits their needs. He enjoys exploring what’s possible with IaC. Damola Oluyemo Damola Oluyemo is a Solutions Architect at Amazon Web Services focused on Enterprise customers. He helps customers design cloud solutions while exploring the potential of Infrastructure as Code and generative AI in software development. Abiola Olanrewaju Abiola Olanrewaju is a Solutions Architect at AWS, specializing in helping Financial services customers implement scalable solutions that drive business outcomes. He has a keen interest in Data Analytics, Security and Generative AI. Ibraheem Ojelade Ibraheem Ojelade is a Solutions Architect at Amazon Web Services, focused on supporting Independent Software Vendors (ISVs). He partners with customers to accelerate their cloud adoption, optimize performance, and strengthen security. With a strong background in cybersecurity and cloud solutions, he helps ISVs design scalable architectures while exploring emerging technologies to drive innovation and growth.