Amazon Web Services (AWS) is launching a new collection of developer-focused resources for the AWS Command Line Interface (AWS CLI). These resources demonstrate working end-to-end shell scripts for working with AWS services and best practices that simplify the process of authoring shell scripts that handle errors, track created resources, and perform cleanup operations. The new AWS Developer Tutorials project on GitHub provides a library of tested, scenario-focused AWS CLI scripts covering over 60 AWS services. These tutorials provide quicker ways to get started using an AWS service API with the AWS CLI. Leveraging generative AI and existing documentation, developers can now more easily create working scripts for their own resources, saving time and reducing errors when managing AWS resources through the AWS CLI. Each script includes a tutorial that explains how the script works with the AWS service API to create, interact with, and clean up resources. The project also includes instructions that you can use to generate and contribute new scripts. You can use existing content and examples with generative AI tools such as the Amazon Q Developer CLI to generate a working script through an iterative test-and-improve process. Depending on how well-documented the use case is, this process can take as little as 15 minutes. For scenarios that don’t have existing examples of API calls with input and output, it can take more iterations to get a working script. Sometimes you need to provide additional information or examples from your own testing to fill in a gap. This process can actually be quite fun! To get started, see AWS Developer Tutorials. For more information on the project, see our post on Builder Center.

https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/using-sam-cli.html now supports https://runfinch.com/ as an alternative to Docker for local development and testing of serverless applications. This gives developers greater flexibility in choosing their preferred local development environment when working with SAM CLI to build and test their serverless applications. Developers building serverless applications spend significant time in their local development environments. SAM CLI is a command-line tool for local development and testing of serverless applications. It allows you to build, test, debug, and package your serverless applications locally before deploying to AWS Cloud. To provide the local development and testing environment for your applications, SAM CLI uses a tool that can run containers on your local device. Previously, SAM CLI only supported Docker as the tool for running containers locally. Starting today, SAM CLI also supports Finch as a container development tool. Finch is an open-source tool, developed and supported by AWS, for local container development. This means you can now choose between Docker and Finch as your preferred container tool for local development when working with SAM CLI. You can use SAM CLI to invoke Lambda functions locally, test API endpoints, and debug your serverless applications with the same experience you would have in the AWS Cloud. With Finch support, SAM CLI now automatically detects and uses Finch as the container development tool when Docker is not available. You can also set Finch as your preferred container tool for SAM CLI. This new feature supports all core SAM CLI commands including sam build, sam local invoke, sam local start-api, and sam local start-lambda. To learn more about using SAM CLI with Finch, visit the https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/install-finch.html. 

AWS Serverless Application Model Command Line Interface (SAM CLI) now supports Finch as an alternative to Docker for local development and testing of serverless applications. This gives developers greater flexibility in choosing their preferred local development environment when working with SAM CLI to build and test their serverless applications. Developers building serverless applications spend significant time in their local development environments. SAM CLI is a command-line tool for local development and testing of serverless applications. It allows you to build, test, debug, and package your serverless applications locally before deploying to AWS Cloud. To provide the local development and testing environment for your applications, SAM CLI uses a tool that can run containers on your local device. Previously, SAM CLI only supported Docker as the tool for running containers locally. Starting today, SAM CLI also supports Finch as a container development tool. Finch is an open-source tool, developed and supported by AWS, for local container development. This means you can now choose between Docker and Finch as your preferred container tool for local development when working with SAM CLI. You can use SAM CLI to invoke Lambda functions locally, test API endpoints, and debug your serverless applications with the same experience you would have in the AWS Cloud. With Finch support, SAM CLI now automatically detects and uses Finch as the container development tool when Docker is not available. You can also set Finch as your preferred container tool for SAM CLI. This new feature supports all core SAM CLI commands including sam build, sam local invoke, sam local start-api, and sam local start-lambda. To learn more about using SAM CLI with Finch, visit the SAM CLI developer guide.

Amazon Web Services (AWS) is launching a new collection of developer-focused resources for the AWS Command Line Interface (AWS CLI). These resources demonstrate working end-to-end shell scripts for working with AWS services and best practices that simplify the process of authoring shell scripts that handle errors, track created resources, and perform cleanup operations. The new AWS Developer Tutorials project on GitHub provides a library of tested, scenario-focused AWS CLI scripts covering over 60 AWS services. These tutorials provide quicker ways to get started using an AWS service API with the AWS CLI. Leveraging generative AI and existing documentation, developers can now more easily create working scripts for their own resources, saving time and reducing errors when managing AWS resources through the AWS CLI. Each script includes a tutorial that explains how the script works with the AWS service API to create, interact with, and clean up resources. The project also includes instructions that you can use to generate and contribute new scripts. You can use existing content and examples with generative AI tools such as the Amazon Q Developer CLI to generate a working script through an iterative test-and-improve process. Depending on how well-documented the use case is, this process can take as little as 15 minutes. For scenarios that don’t have existing examples of API calls with input and output, it can take more iterations to get a working script. Sometimes you need to provide additional information or examples from your own testing to fill in a gap. This process can actually be quite fun! To get started, see https://github.com/aws-samples/sample-developer-tutorials/tree/main. For more information on the project, see https://builder.aws.com/content/30w3vIpXgSNM1fxsDzjKKUCxwQg/aws-developer-tutorials-docs-as-test.

The AWS Command Line Interface (AWS CLI) v2 now supports OAuth 2.0 authorization code flows using the Proof Key for Code Exchange (PKCE) standard. This provides a simple and safe way to retrieve credentials for AWS CLI commands. The AWS CLI is a unified tool that enables you to control multiple AWS services from the command line and to automate them through scripts. AWS CLI v2 offers integration with AWS IAM Identity Center, the recommended service for managing workforce access to AWS applications and multiple AWS accounts. The authorization code flow with PKCE is the recommended best practice for access to AWS resources from desktops and mobile devices with web browsers. It is now the default behavior when running the aws sso login or aws configure sso commands. To learn more, see https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.html in the AWS CLI User Guide. Share your questions, comments, and issues with us on https://github.com/aws/aws-cli. AWS IAM Identity Center is available at no additional cost in https://docs.aws.amazon.com/general/latest/gr/sso.html.  

The AWS Command Line Interface (AWS CLI) v2 now supports OAuth 2.0 authorization code flows using the Proof Key for Code Exchange (PKCE) standard. This provides a simple and safe way to retrieve credentials for AWS CLI commands. The AWS CLI is a unified tool that enables you to control multiple AWS services from the command line and to automate them through scripts. AWS CLI v2 offers integration with AWS IAM Identity Center, the recommended service for managing workforce access to AWS applications and multiple AWS accounts. The authorization code flow with PKCE is the recommended best practice for access to AWS resources from desktops and mobile devices with web browsers. It is now the default behavior when running the aws sso login or aws configure sso commands. To learn more, see Configuring IAM Identity Center authentication with the AWS CLI in the AWS CLI User Guide. Share your questions, comments, and issues with us on GitHub. AWS IAM Identity Center is available at no additional cost in AWS Regions.