AWS Serverless Application Repository provides a place to share serverless applications defined with AWS SAM templates.
Application sharing and deployment
AWS ServerlessServerless technologies let customers run code and integrate applications without managing servers. Application Repository helps teams find, publish and deploy serverless applications, which use services that run code without managing servers. A publisher provides an AWS Serverless Application Model (SAM) template, a file defining the application’s AWS resources, so others can reuse the application.
How it works
- Define the application in a SAM templateA template defines the AWS resources used by a serverless application. and publish it with the console, SAM CLI or an AWS SDK.
- Choose who can deploy it. New applications start private. A publisher can share with specific accounts, an AWS organization or everyone.
- Check Region availability. Private and privately shared applications are available in their creation Region; public applications are available in all AWS Regions.
| Sharing setting | Who can deploy | Region availability |
|---|---|---|
| Private | Publishing account | Creation Region |
| Privately shared | Specified accounts or organization | Creation Region |
| Public | Everyone | All AWS Regions |
When a public application is deployed in another Region, the repository copies its deployment artifacts, such as code, to an S3 bucket there and updates the template references.
Exam cues
- If the question says find and deploy a reusable serverless application, think AWS Serverless Application Repository, because it lets developers find, deploy and publish applications.
- If the question says reuse a serverless application across accounts in one organization, think private sharing, because the publisher can grant the organization access.
- If the question says deploy a privately shared application in another Region, think creation Region, because privately shared applications are only available there.
Remember
- Applications are private by default.
- Private application policiesAn application policy determines which actions a specified principal or organization can perform on a repository application. grant or deny access at the account level, not to individual users in an account.
Trap: Sharing an application privately does not make it available in another Region.
Review required capabilities and create the change set with those capabilities.
Execute the change set to deploy the application.
From the AWS docs (13)
- Serverless technologies let customers run code and integrate applications without managing servers.
- AWS Serverless Application Repository lets developers find, deploy and publish serverless applications.
- Publishers define applications with an AWS SAM template and can publish using the console, SAM CLI or an AWS SDK.
- Applications are private by default and can be shared with specific accounts, an AWS organization or everyone.
- Private and privately shared applications are available only in their creation Region; public applications are available in all AWS Regions.
- When a public application is deployed in another Region, the repository copies deployment artifacts to an S3 bucket in that Region and updates template references.
- A nested application is part of a larger serverless application.
- The repository checks templates for IAM roles, resource policies and nested applications and requires acknowledgment of applicable capabilities before deployment.
- Specified IAM resources require CAPABILITY_IAM or CAPABILITY_NAMED_IAM.
- Certain resource policies require CAPABILITY_RESOURCE_POLICY.
- A CloudFormation change set previews proposed stack changes before execution.
- A CloudFormation stack is a collection of AWS resources managed as one unit.
- For privately shared applications, repository application policies grant or deny access to AWS accounts, not individual users in an account.
Public sharing and deployment capabilities
AWS ServerlessServerless technologies let customers run code and integrate applications without managing servers. Application Repository public sharing and deployment involve requirements for application properties, permissions and capabilities. A consumer deploying a parent application must also have permission to deploy its nested applicationsA nested application is an application included inside another application..
How it works
- For public sharing, provide
SemanticVersionandLicenseUrl. - For a parent with nested applications, ensure the consumer has permission to deploy the nested applications.
- Review the required capabilities.
- For CLI deployment, review
requiredCapabilities, create a CloudFormation change setA change set describes proposed changes to a CloudFormation stack before execution. with the required capabilities, then execute the change set to deploy.
Exam cues
- If the question says a public parent contains a private nested application, think nested deployment permission, because the consumer needs permission to deploy the nested application too.
- If the question says an application contains nested applications, think
CAPABILITY_AUTO_EXPAND, because it must be acknowledged. - If the question says an application creates IAM resources with custom names, think
CAPABILITY_NAMED_IAM, because it is required for those resources. - If the question says a CLI change set has been created, think execute it, because execution deploys the application.
Remember
- Public sharing requires
SemanticVersionandLicenseUrl. - Review
requiredCapabilitiesbefore creating the change set with the required capabilities.
Trap: A public parent does not give a consumer permission to deploy a restricted nested application.
From the AWS docs (5)
- Public sharing requires SemanticVersion and LicenseUrl properties.
- A consumer must have permission to deploy nested applications to deploy their parent application.
- Applications with nested applications require CAPABILITY_AUTO_EXPAND.
- Applications containing IAM resources with custom names require CAPABILITY_NAMED_IAM.
- CLI deployment reviews requiredCapabilities, creates a CloudFormation change set with required capabilities and executes the change set.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 9 cards as a list
Where can a team find, publish and deploy reusable serverless applications?
AWS Serverless Application Repository. Publishers define applications using AWS SAM templates.
A team publishes an application to AWS Serverless Application Repository but has not configured sharing. Who can deploy it?
The publishing account. Applications are private by default.
A company wants to share an AWS Serverless Application Repository application only with its organization. What should the publisher configure?
Privately share the application with the AWS organization.
Can a privately shared AWS Serverless Application Repository application be deployed in a different Region from its creation Region?
No. Private and privately shared applications are available only in their creation Region.
What properties are required to share an AWS Serverless Application Repository application publicly?
SemanticVersion and LicenseUrl.
A public AWS Serverless Application Repository parent contains a private nested application. Why might another account be unable to deploy the parent?
The account also needs permission to deploy the nested application.
Which capability must be acknowledged when an AWS Serverless Application Repository application contains nested applications?
CAPABILITY_AUTO_EXPAND.
Which capability is required when an AWS Serverless Application Repository application creates IAM resources with custom names?
CAPABILITY_NAMED_IAM.
After creating an AWS Serverless Application Repository CloudFormation change set using the CLI, what deploys the application?
Execute the change set.