search

amplify-education / serverless-domain-manager

Serverless plugin for managing custom domains with API Gateways.
MIT License
936 stars 235 forks source link

No route53 entry / no hosted id / no cloudfront distribution #414

Closed Abhijith-Nagaraja closed 2 years ago

Abhijith-Nagaraja commented 3 years ago

Bug Report

Error Description Deployment is success without errors, but I don't see no route53 entry, hosted ID mentioned is not available in route53, no visible cloudfront distribution

From the console output I see domain and target domain, But when I try to hit domain and my api, it will go for timeout, I tried with https and http both. https will give me timeout and http will give 404 not found

I see Api Gateway, Lambda all deployed.

I went and checked route53 entry but I am not able to find one for this. I also searched for Hosted Zone Id: ABCDEFGHIJK, but that is also nowhere to be found. I check cloudfront distribution, but none were present.

Command Run e.g. sls deploy --verbose --env 'VPC Name'

Console Output

ServiceEndpoint: https://xxxxxxxxxxxxxx.execute-api.us-west-2.amazonaws.com/test
ServerlessDeploymentBucketName: xxxxxxxxxxxxxx-serverlessdeploymentbucket-8qq3f843bav

Serverless Domain Manager: Info: Found apiId: xxxxxxxxxxxxxx for subdomain.maindomain.com
Serverless Domain Manager: Info: Updated API mapping to 'api' subdomain.maindomain.com
Serverless Domain Manager: Summary: Distribution Domain Name
Serverless Domain Manager:    Domain Name: subdomain.maindomain.com
Serverless Domain Manager:    Target Domain: xxxxxxxxxxxxxx.execute-api.us-west-2.amazonaws.com
Serverless Domain Manager:    Hosted Zone Id: ABCDEFGHIJK

Domain Manager Configuration Replace this with your own serverless.yml file (anonymized, of course) to help us better resolve your issue.

plugins:
  - serverless-vpc-discovery
  - serverless-domain-manager
custom:
  stage: test
  region: us-west-2
  vpcDiscovery:
    vpcName: TEST-VPC
    subnets:
      - tagKey: Name
        tagValues:
          - TEST-Subnet-A
          - TEST-Subnet-B
          - TEST-Subnet-C
    securityGroups:
      - tagKey: Name
        tagValues:
          - test-sg
  customDomain:
    domainName: subdomain.maindomain.com
    certificateName: '*.maindomain.com'
    basePath: api
    stage: test
    endpointType: regional
    createRoute53Record: true
    apiType: rest
    autoDomain: true
    autoDomainWaitFor: 2400

Versions

nonbeing commented 3 years ago

Got the same issue.

No Route53 record is created, even when I specify the hostedZoneId. This happens regardless of whether I set createRoute53Record to true, or even if I omit this (and the default is true anyway so it should still create the record).

rddimon commented 2 years ago

Hi @Abhijith-Nagaraja It should be fixed in the version 5.3.1

Feel free to reopen it in case of any further issues related to it