serverless-domain-manager
serverless-domain-manager copied to clipboard
Docs unclear on setup. everything works, except it doesnt.
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Support Question
Taking it from the top.
-
Route53 I own the root domain:
-
Route53 Hosted Zone is set up:
-
Certificate Manager
-
sls.yml is setup for subdomain and function is defined.
$ cat serverless.yml
>>
[...]
custom:
customDomain:
domainName: sls.cofenster.ninja
# basePath: ${self:provider.stage}
stage: ${self:provider.stage}
endpointType: regional
certificateName: '*.cofenster.ninja'
createRoute53Record: true
securityPolicy: tls_1_2
apiType: rest
[...]
functions:
transcribeVideo:
handler: packages/transcription-pipeline/dist/transcribeVideo.handler
package:
exclude:
- ./**
include:
- packages/transcription-pipeline/dist/transcribeVideo.js
timeout: 30
events:
# - http: GET /transcribeVideo
- http:
path: /transcribeVideo
method: ANY
cors: true
- domain creation is confirmed
$ sls create_domain --stage finn --aws-profile cofenster
> Serverless: [AWS apigatewayv2 200 0.293s 0 retries] getDomainName({ DomainName: 'sls.cofenster.ninja' })
> Serverless: Custom domain sls.cofenster.ninja already exists.
- deploy works.
$ sls deploy --stage finn --aws-profile cofenster
>>
Serverless: Stack update finished...
Serverless: Invoke aws:info
Serverless: [AWS cloudformation 200 0.114s 0 retries] describeStacks({ StackName: 'com-cofenster-finn' })
Serverless: [AWS cloudformation 200 0.145s 0 retries] listStackResources({ StackName: 'com-cofenster-finn', NextToken: undefined })
Service Information
service: com-cofenster
stage: finn
region: eu-central-1
stack: com-cofenster-finn
resources: 28
api keys:
None
endpoints:
ANY - https://5qd6hixggk.execute-api.eu-central-1.amazonaws.com/finn/transcribeVideo
functions:
transcodingUploadReceived: com-cofenster-finn-transcodingUploadReceived
transcodingStatus: com-cofenster-finn-transcodingStatus
transcribeVideo: com-cofenster-finn-transcribeVideo
layers:
ffmpeg: arn:aws:lambda:eu-central-1:393241160538:layer:ffmpeg:14
Serverless: [AWS apigatewayv2 200 0.197s 0 retries] getApiMappings({ DomainName: 'sls.cofenster.ninja' })
Serverless: [AWS apigatewayv2 200 0.175s 0 retries] getDomainName({ DomainName: 'sls.cofenster.ninja' })
Serverless: [AWS apigatewayv2 200 0.229s 0 retries] updateApiMapping({
ApiId: '5qd6hixggk',
ApiMappingId: 'jrxm07',
ApiMappingKey: '(none)',
DomainName: 'sls.cofenster.ninja',
Stage: 'finn'
})
Serverless: Updated API mapping to '(none)' for sls.cofenster.ninja
Serverless Domain Manager Summary
Distribution Domain Name
Domain Name: sls.cofenster.ninja
Target Domain: d-oqa8jbks49.execute-api.eu-central-1.amazonaws.com
Hosted Zone Id: Z1U9ULNL0V5AJ3
Serverless: Invoke aws:deploy:finalize
Serverless: [AWS s3 200 0.123s 0 retries] listObjectsV2({
Bucket: 'com-cofenster-finn-serverlessdeploymentbucket-nknb6fjrumdb',
Prefix: 'serverless/com-cofenster/finn'
})
-
lambda is callable
https://5qd6hixggk.execute-api.eu-central-1.amazonaws.com/finn/transcribeVideo
-> works perfectly -
then why in foo's name is the route not available????
http://sls.cofenster.ninja/transcribeVideo
-> server not found
Did you ever resolve this issue? I'm having a similar issue now myself, and I am not clear on how to debug this issue.
no. no solution, help or docs found
Hi @FinnFrotscher @SethThomas
It's no activity for a long time and hope you have found a solution.
A question in another case, have you tried with https
protocol?
Our plugin has improved and I was wondering if you could try the latest version on the plugin and let us know And please provide packages versions which you are using next time it may help us to debug the issue
There is no activity for the last 6 months so clothing it.
Hope you have resolved your issue. Let's try our latest version and feel free to open a new issue in case of any problem.