Deploy Your Serverless Infrastructure

Chapter Comments
1

Link to chapter - https://serverless-stack.com/chapters/deploy-your-serverless-infrastructure.html

1 Like
2

After this has been deployed to AWS, is it OK to delete the resources we created manually?

What is the list of services that can be deleted once this step is finished?

3

Do you mean the services from the first part of the tutorial?

The two parts of the tutorial create complete separate resources. So removing one wonā€™t affect the other.

4

Ya Jay I mean the services we created manually at the beginning (without CloudFormation). It would just be nice if there was a section that went a bit like this:

Now that we have deployed our resources using CloudFormation, we can go in an delete the ones we created manually: API Gateway, Lambda, Cognito, etcā€¦

5

Related question ā€“ this part of the tutorial create a user pool named generically ā€˜stageā€™-user-pool rather than ā€˜stageā€™-notes-user-pool. Any reason for this? If we start developing multiple apps we would want these to be more easily recognizable no? And what happens if we forgot about this and made another app with the same user pool naming conventionā€¦ when we tried serverless deploy would it just fail because thereā€™s already a user pool with that name?

6

@mperone Yeah thatā€™s a good point. It should be $stage-notes-user-pool or something of the like.

@peetss Yeah we could add a note. But itā€™s really up to you if you want to keep those around. I know people donā€™t necessarily go through the advanced part of the tutorial.

7

Idiot question(s)!

So then, Iā€™ve ran sudo serverless deploy -v. Now my aws site is updated! Huzzah!

But. I donā€™t THINK my client-side stuff (app-client) is pointing at all that.

Will that be covered in further chapters? (I will be looking into this later, and if I answer my own questions Iā€™ll leave up the answer in an edit)

8

Yup. In the next few chapters youā€™ll be asked to update it.

1 Like
9

When deploying the new CloudFormation template(s), I get the following error:

  Error --------------------------------------------------
 
  The CloudFormation template is invalid: Template error: instance of Fn::GetAtt references undefined resource NotesTable

For debugging logs, run again after setting the ā€œSLS_DEBUG=*ā€ environment variable.

In my serverless.yml I have the following:

  iamRoleStatements:
    - Effect: Allow
      Action:
        - dynamodb:DescribeTable
        - dynamodb:Query
        - dynamodb:Scan
        - dynamodb:GetItem
        - dynamodb:PutItem
        - dynamodb:UpdateItem
        - dynamodb:DeleteItem
      # Restrict our IAM role permissions to
      # the specific table for the stage
      Resource:
        - "Fn::GetAtt": [ NotesTable, Arn ]
1 Like
10

So I just cloned the backend api from github, and now I gets another error:

  An error occurred while provisioning your stack: ListLambdaFunction - Value of property Variables must be an object with String (or simple type) properties.
11

I was missing the env.yml file. Apparently its not part of the official github repo?

12

Yeah that file isnā€™t meant to be checked in since it contains sensitive information. Iā€™ll add a note to the repo so itā€™s not confusing.

13

Or maybe just include the file in the repo, but give the strings a value like ā€œREPLACE THIS WITH YOUR STRIPE KEYā€?

14

Sorta, we just donā€™t want to give the impression that the file should be in your Git repo.

15

I totally understand that.

1 Like
16

Hi @jayair - When I tried to deploy, I get the following cloud formation error:

    Error --------------------------------------------------
    The CloudFormation template is invalid: Template format error: Unrecognized resource types [AWS::Cognito::UserPool, AWS::Cognito::IdentityPoolRoleAttachment, AWS::Cognito::UserPoolClient, AWS::Cognito::IdentityPool]

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Any tips on what I can try next? I validated that those are indeed CloudFormation resource types: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cognito-userpoolclient.html

1 Like
17

@kpathakota I am having the same problem. In my case is because my default region does not support Cognito. You can fix that by running sls deploy -v --region us-east-1

What I am really trying to figure out is how to leave my whole stack as sa-east-1 (does not support cognito) and have cognito on the us-east-1 region. @jayair or anyone else - could you help me? Thanks in advance

18

I havenā€™t tried it but conceptually it should be possible?

Whatā€™s the issue you are running into?

Btw, @kpathakota did @leogonzalezā€™s tip work for you?

1 Like
19

@jayair - yes, worked! @leogonzalez - thanks! That was exactly it. Makes sense that the region did not understand that particular CloudFormation template if itā€™s not available.

2 Likes
20

Thanks @jayair - I want to run my entire stack in Sao Paulo (sa-east-1) since response times are better (90% better than us-east-1 for me) except cognito (us-east-1) since the service is not available here.

running sls deploy -v --region sa-east-1 throws the error since cognito is not available, so I was wondering how can I override the region for a specific service (Cognito) within my YML file.