Skip to content

Latest commit

 

History

History

Example_5

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
src
src
 
 
README.md
README.md
 
 
generated-template.yaml
generated-template.yaml
 
 
template.yaml
template.yaml
 
 

README.md

Example 5 - Nested applications

This example will present Nested applications concept.

Nested applications build off a concept in AWS CloudFormation called nested stacks. With nested applications, serverless applications are deployed as stacks, or collections of resources, that contain one or more other serverless application stacks. You can reference resources created in these nested templates to either the parent stack or other nested stacks to manage these collections of resources more easily.

We will use a slightly modified version of Example 3 template. This time our stack will be enriched with a simple CRUD functionality for our file info database - all in a form of a serverless application taken from AWS Serverless Application Repository.

All commands should be invoked from Example_5 directory

Validate template:

sam validate

Deploy it to the Cloud!

Remember to use the correct bucket name (created in previous examples)

  • package project and generate processed template:
sam package \
   --template-file template.yaml \
   --output-template-file generated-template.yaml \
   --s3-bucket BUCKET_NAME
  • deploy stack
sam deploy \
   --template-file generated-template.yaml \
   --stack-name AWS-SAM-WORKSHOP-EXAMPLE-5 \
   --capabilities CAPABILITY_IAM

  • watch stack is being created in AWS Console here

  • at this point, we should have had a working stack - exactly like one in example 3. Test it by uploading some file to our input bucket.

Introduce nested application

  • Add new resource to the template
  microservicehttpendpoint:
    Type: AWS::Serverless::Application
    Properties:
      Location:
        ApplicationId: arn:aws:serverlessrepo:us-east-1:077246666028:applications/microservice-http-endpoint
        SemanticVersion: 1.0.3
      Parameters: 
        TableNameParameter: !Ref FileDb
  • package and deploy - remember to add new capability to the deploy command -> CAPABILITY_AUTO_EXPAND
sam deploy \
   --template-file generated-template.yaml \
   --stack-name AWS-SAM-WORKSHOP-EXAMPLE-5 \
   --capabilities CAPABILITY_IAM CAPABILITY_AUTO_EXPAND
  • Test new endpoint (find api gateway with resource name MyResource) and provide TableName parameter in query string