https://serverless-stack.com/ logo
Join Slack
Powered by
Hello, I am trying to add `aws lambda power tuning...
# help
b
Hello, I am trying to add 
aws lambda power tuning
 using cdk like here: https://github.com/alexcasalboni/aws-lambda-power-tuning/blob/master/README-DEPLOY.md#option-3-deploy-the-aws-sar-app-with-aws-cdk after adding it, the sst console is keeping stuck on 
Waiting for invocations
do you have any idea about this?
t
Hey I haven't tried this but it wouldn't make sense to use it with sst start right?
b
Yes right, but I wanted to report this issue, to see if there is any conflicts with cdk sam
t
I'm not sure - I don't think there should be any issue but I'm not fully familiar with what it's doing
b
I see, thank you
f
If you start up 
sst console
in another terminal while 
sst start
is running, u can look at the CloudWatch for the functions and see if there are any errors
b
Wow, I will try
I've just tried to run 
sst console
with a deployed stage having this cdk sam construct, I got same issue
j
@Bshr Ramadan any luck with this issue?
f
@Bshr Ramadan sorry about the delayed follow up. Just to clarify, after you run 
sst console
to start up the console, the console should look like this
Note that you shouldn’t see a Local tab on the left, and you should see 
Polling for logs
on the right. This indicates we are not in the 
sst start
mode, instead we are looking at CloudWatch logs.
Now, if you run the power tuner, wait for about a minute, you should see logs coming in.
b
@Jay sorry I didn't notice your message @Frank after running 
sst console
it keeps on this, and if I removed the sam application it would work
Actually it's not a necessary for me now to run power tuning, but I wanted to report this issue.
f
I see… if you open up developer tools, do u see any errors in the console?
b
@Frank
f
Ah.. @thdxr i think what’s going on here is that the Lambda Power Tuning tool is adding a new stack automatically. And that stack is also tagged with 
sst:app
and 
sst.stage
, but it doesn’t have the metadata. Could that be why the request if failing?
@Bshr Ramadan could you also share what you in the request? ie. request body, header
b
Copy code
Request URL: <http://localhost:12557/proxy/https://cloudformation.us-east-1.amazonaws.com/>
Request Method: POST
Status Code: 400 Bad Request
Remote Address: [::1]:12557
Referrer Policy: strict-origin-when-cross-origin

Response headers:
Access-Control-Allow-Headers: undefined
Access-Control-Allow-Methods: GET, PUT, PATCH, POST, DELETE
access-control-allow-origin: *
access-control-expose-headers: x-amzn-RequestId,x-amzn-ErrorType,x-amzn-ErrorMessage,Date
connection: close
content-length: 351
content-type: text/xml; charset=utf-8
date: Fri, 18 Feb 2022 18:22:38 GMT
x-amzn-requestid: 624927fa-fa50-42bd-8aea-c67572a805cd
X-Powered-By: Express

Request headers:
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
amz-sdk-invocation-id: dd05cbc8-c8cb-4558-aebc-5c66d45b8f80
amz-sdk-request: attempt=1; max=3
authorization: AWS4-HMAC-SHA256 Credential=AKIA2HHJMBBBYE7AWP22/20220448/us-east-1/cloudformation/aws4_request, SignedHeaders=amz-sdk-invocation-id;amz-sdk-request;content-length;content-type;host;x-amz-content-sha256;x-amz-date;x-amz-user-agent, Signature=c8c1ab1eaea08d99f065b218fd5a435cd9ed2ff1a976ec69da90f647c945f36c
Connection: keep-alive
Content-Length: 136
content-type: application/x-www-form-urlencoded
DNT: 1
Host: localhost:12557
Origin: <https://console.serverless-stack.com>
sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="98", "Microsoft Edge";v="98"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.102 Safari/537.36 Edg/98.0.1108.55
x-amz-content-sha256: 5c41eba4754fcdb704fef987e2ca590cbc1df615f807b95663c9663aad01d0a2
x-amz-date: 20220218T182240Z
x-amz-user-agent: aws-sdk-js/3.43.0 os/Windows/NT_10.0 lang/js md/browser/Microsoft_Edge_98.0.1108.55 api/cloudformation/3.43.0
Hello @Frank I wanted to ask if you could find solution for this issue I created a new stack with cdk ElasticBeanstalk construct and it caused same problem.
f
Hey @Bshr Ramadan sorry about the delay. Let me see if @thdxr can put in a quick fix.
Dax, my guess for the issue is that the Lambda Power Tuning tool is adding a new stack automatically. And that stack is also tagged with 
sst:app
and 
sst.stage
, but it doesn’t have the metadata. Could that be why the request if failing?
b
No worries, thank you @Frank
2 Views
Open in Slack
PreviousNext
Powered by