See dump files below, could you help, please? I've followed the README instructions and everything completed correctly until this last step.

Starting phase: preBuild

Executing command: cd client

2022-04-13T17:25:37.978Z [INFO]: # Executing command: npm ci
2022-04-13T17:25:39.183Z [WARNING]: npm
2022-04-13T17:25:39.184Z [WARNING]: ERR! cipm can only install packages with an existing package-lock.json or npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or later to generate it, then try again.

2022-04-13T17:25:39.215Z [WARNING]:
2022-04-13T17:25:39.215Z [WARNING]: npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-13T17_25_39_184Z-debug.log

2022-04-13T17:25:39.215Z [HELP]: Outputting the npm debug log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/root/.nvm/versions/node/v14.19.0/bin/node',
1 verbose cli '/root/.nvm/versions/node/v14.19.0/bin/npm',
1 verbose cli 'ci'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session [removed]
5 info prepare initializing installer
6 verbose prepare starting workers
7 verbose prepare installation prefix: /codebuild/output/[removed]/src/amazon-api-gateway-url-shortener/client
8 verbose checkLock verifying package-lock data
9 verbose teardown shutting down workers.
10 info teardown Done in 0s
11 verbose stack Error: cipm can only install packages with an existing package-lock.json or npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or later to generate it, then try again.
11 verbose stack at Installer.checkLock (/root/.nvm/versions/node/v14.19.0/lib/node_modules/npm/node_modules/libcipm/index.js:165:9)
11 verbose stack at /root/.nvm/versions/node/v14.19.0/lib/node_modules/npm/node_modules/libcipm/index.js:139:16
12 verbose cwd /codebuild/output/[removed]/src/amazon-api-gateway-url-shortener/client
13 verbose Linux 4.14.246-187.474.amzn2.x86_64
14 verbose argv "/root/.nvm/versions/node/v14.19.0/bin/node" "/root/.nvm/versions/node/v14.19.0/bin/npm" "ci"
15 verbose node v14.19.0
16 verbose npm v6.14.16
17 error cipm can only install packages with an existing package-lock.json or npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or later to generate it, then try again.
18 verbose exit [ 1, true ]

2022-04-13T17:25:39.218Z [ERROR]: !!! Build failed
2022-04-13T17:25:39.218Z [ERROR]: !!! Non-Zero Exit Code detected
2022-04-13T17:25:39.218Z [INFO]: # Starting environment caching...
2022-04-13T17:25:39.219Z [INFO]: # Environment caching completed
Terminating logging...`

Thanks for this great example. I only wonder about the monthly costs for a given usage. Similar is done in this example https://aws.amazon.com/blogs/compute/build-a-serverless-private-url-shortener/

‚You create 1000 short URLs per month and each is viewed by 1000 users – i.e., 1 million requests per month‘

what would be the costs with this architecture?

Please add a screenshot of the UI. It is not present in the blog series https://aws.amazon.com/it/blogs/compute/building-a-serverless-url-shortener-app-without-lambda-part-1/ nor in this repo.

The only frontend available appears to be here https://github.com/aws-samples/amazon-api-gateway-url-shortener/blob/master/client/src/views/Dashboard.vue but I am not sure people will setup everything if they cannot see the UI before setting up the whole environment. I propose to add at least 1 screenshot of the frontend in the docs.

I'm struggling to figure out the right syntax to use in CloudFormation templates.

Is there a particular reason why the mapping templates were written with double quoted strings, as opposed to block strings?

responseTemplates:
  application/json: "#set($inputRoot = $input.path('$'))[ \
    #foreach($elem in $inputRoot.Items) { \
      \"id\":\"$elem.id.S\", \
      \"url\": \"$elem.url.S\", \
      \"timestamp\": \"$elem.timestamp.S\", \
      \"owner\": \"$elem.owner.S\"} \
    #if($foreach.hasNext),#end \
    #end]"

Using a multiline/block string seems so much more writable and readable:

responseTemplates:
  application/json: |-
    #set($inputRoot = $input.path('$'))[
      #foreach($elem in $inputRoot.Items) {
        "id": "$elem.id.S",
        "url": "$elem.url.S",
        "timestamp": "$elem.timestamp.S",
        "owner": "$elem.owner.S"}
      #if($foreach.hasNext),#end
    #end]

(this example is from api.yaml line 171)

Deploy runs perfectly, and so does Amplify build. Visiting website, both "signup" and "login" give Access denied error. Grubbing around Cognito doesn't surface any settings I can change, registered a user manually but stuck. Welcome any tips, tricks.

Hey -- getting a bogus URL generated in the output. In my case, it generated:

VUE_APP_API_ROOT=https://:d2xx9t23blargh.cloudfront.net

Note the colon before the "d2xx9...". Unsurprisingly, this failed when I put it in the .env file for the Vue app, but when I removed the rogue colon and restarted the app, it worked fine.

I don't think I changed anything, other than giving my credentials, etc.

Thanks!

where do i add 400 template

Looks like a PR put in a hard-coded email address opposed to $context.authorizer.claims.email

Thanks for the great introduction. I just tried it. But I get an error when I want to shorten URLs "SlipLink cannot be created. Bad format.". Any advice for me?

Regards,
Ramón

Thanks for doing this, it's fantastic!

From working on another project, I learned that you can do:

aws cloudformation delete-stack --stack-name yourstacknamehere

This starts a stack deletion, and returns nearly instantly. I don't know how to tell if it's done or not, other than trying to get information about the stack, which will eventually fail. I'll dig around and see if I can find out.

Dev Environment

SAM CLI, version 1.0.0
aws-cli/2.0.33 Python/3.7.4 Darwin/19.6.0 botocore/2.0.0dev37

When I start the deployment using command sam deploy -g, It is getting failed in between with the following message of failure.

CloudWatch Logs role ARN must be set in account settings to enable logging (Service: AmazonApiGateway; Status Code:400; Error Code: BadRequestException; Request ID: 58541396-e90b-418c-a8c5-8ae495604e75)

I am able to figure out this problem by adding following policy in the template.yml

  CloudWatchRole:
    Type: 'AWS::IAM::Role'
    Properties:
      AssumeRolePolicyDocument:
        Version: 2012-10-17
        Statement:
          - Effect: Allow
            Principal:
              Service:
                - apigateway.amazonaws.com
            Action: 'sts:AssumeRole'
      Path: /
      ManagedPolicyArns:
        - >-
          arn:aws:iam::aws:policy/service-role/AmazonAPIGatewayPushToCloudWatchLogs
  Account:
    Type: 'AWS::ApiGateway::Account'
    Properties:
      CloudWatchRoleArn: !GetAtt 
        - CloudWatchRole
        - Arn

Now it is getting deployed as expected.

After successful deployment I can see the landing Magic home page but when i click on Signup/Login I am getting following error.

<Error> <Code>AccessDenied</Code> <Message>Access Denied</Message> <RequestId>BFD2F9DAC0C76C7E</RequestId> <HostId>u1cmt0WOo96vP9naC7HW5aRd7N7aBzSQse9e0llXByYRQX8B5OIOxtR/JmEjZmw2iQJhvjf33NU=</HostId> </Error>
I am not sure what am I missing here.

While building code using Amplify getting following error.

17 error cipm can only install packages with an existing package-lock.json or npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or later to generate it, then try again.
18 verbose exit [ 1, true ]
2021-05-19T12:16:42.475Z [ERROR]: !!! Build failed
2021-05-19T12:16:42.475Z [ERROR]: !!! Non-Zero Exit Code detected
2021-05-19T12:16:42.475Z [INFO]: # Starting environment caching...
2021-05-19T12:16:42.475Z [INFO]: # Environment caching completed

Thanks!

So on the proper https://slip.link/, the client and "API" are on the same domain and work side by side. I cannot for the life of me figure out how to do this in practice and the docs don't seem to cover it.

If I add both origins to cloudfront and set up the behaviors, I can't get amplify to work because it goes to https://mydoma.in/pkojhuytfyfguhijokpl;njbhgvyt78y92304rr/ where there is a random string after the domain and this breaks cloudfront. No matter what I do with the behaviors, I can't find a way to get it to work.

I also tried to do the static files in S3, but for the life of me I can't get all of the behaviors set up in a way that works with that either.

I'd think that maybe the amplify site would pull the redirects from dynamo, but it doesn't seem to do that. The cloudformation seems to set up the api gateway and only link cloudfront to that api. The API doesn't include amplify though either.

Am I missing something or do the docs just not cover it?