> ## Documentation Index > Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Serverless Application Repository > Overview of AWS Serverless Application Repository for packaging, publishing, sharing, and deploying SAM-based serverless applications and components across AWS accounts. In this lesson we explore the AWS Serverless Application Repository — a managed catalog for sharing, discovering, and deploying serverless applications and components. The repository is tightly integrated with the AWS Serverless Application Model (SAM) so developers can package SAM templates plus application artifacts, publish them, and let others deploy those serverless applications quickly. For full reference, see the official Serverless Application Repository docs: [https://docs.aws.amazon.com/serverlessrepo/latest/devguide/](https://docs.aws.amazon.com/serverlessrepo/latest/devguide/) A flow diagram titled "Serverless Application Repository" showing a developer packaging a SAM template and application, publishing them to the AWS Serverless Application Repository, and then sharing them with users. Icons depict a single user on the left, the repository in the center, and a group of users on the right. ## How it works — packaging, publishing, and deploying Typical workflow: * Define your application with an AWS SAM template that references your Lambda code, API definitions, and other resources. * Package application artifacts (upload code and assets to an S3 bucket) and produce a packaged SAM template that refers to those uploaded artifacts. * Publish the packaged template and metadata to the Serverless Application Repository. * Consumers discover the application, provide parameter values and settings, and deploy it into their own AWS accounts. Commands using the AWS SAM CLI: ```bash theme={null} # Package the application artifacts and produce packaged.yaml sam package --template-file template.yaml --s3-bucket my-bucket --output-template-file packaged.yaml # Publish the packaged application to the Serverless Application Repository sam publish --template packaged.yaml --region us-east-1 ``` Consumers who deploy a repository application receive a CloudFormation template derived from the SAM template. CloudFormation provisions the resources declared in the template so the application runs in the consumer's account. Key resources typically provisioned: * Lambda functions * Amazon API Gateway endpoints * IAM roles and policies * Supporting resources such as DynamoDB tables, S3 buckets, EventBridge rules, etc. ## Benefits and features The Serverless Application Repository helps teams accelerate development by offering reusable, vetted serverless components, and simplifying deployment via SAM + CloudFormation. | Feature | Benefit | Example / Use case | | - | - | - | | Centralized repository | Discover and share serverless solutions across teams | Search for common patterns like "user-auth" or "image-processor" | | Integrated with AWS SAM | Define serverless resources with familiar SAM constructs | Use SAM templates to define `AWS::Serverless::Function` and `AWS::Serverless::Api` | | Rapid deployment | Consumers can configure parameters and deploy quickly | One-click deploy of an application into a target account | | Reusable components | Reduce duplicated effort by publishing common building blocks | Shared Lambda layers, authorization logic, or monitoring stacks | | Public, private, or account-restricted sharing | Control who can find or deploy your applications | Publish publicly or restrict to specific AWS accounts | A "Features" slide with five numbered panels, each showing a colorful icon. The panels list: Centralized Repository; Integrated with AWS SAM; Rapid Deployment; Reusable Applications; and Public and Private Sharing. Applications published to the repository can be shared publicly, privately, or with specific AWS accounts. Use IAM and resource-based policies to control publishing and deployment permissions. ## Best practices * Use versioning when publishing so consumers can pick specific stable releases. * Limit deployment permissions with IAM and resource-based policies so only authorized accounts can publish or deploy. * Publish clear metadata, parameter descriptions, and examples to make adoption easier. * Reuse Lambda layers and other shared resources where possible to minimize package size and duplication. ## Links and references * Serverless Application Repository — [https://docs.aws.amazon.com/serverlessrepo/latest/devguide/](https://docs.aws.amazon.com/serverlessrepo/latest/devguide/) * AWS SAM (Serverless Application Model) — [https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/) * AWS SAM CLI — [https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli.html](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli.html) * AWS CloudFormation — [https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html) * AWS Lambda — [https://docs.aws.amazon.com/lambda/latest/dg/welcome.html](https://docs.aws.amazon.com/lambda/latest/dg/welcome.html) * Amazon API Gateway — [https://docs.aws.amazon.com/apigateway/latest/developerguide/welcome.html](https://docs.aws.amazon.com/apigateway/latest/developerguide/welcome.html) * AWS IAM — [https://docs.aws.amazon.com/IAM/latest/UserGuide/](https://docs.aws.amazon.com/IAM/latest/UserGuide/) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.