AppSync GraphQL API with Custom Domain and CloudFormation

April 7th, 2019 272 Words

With AWS AppSync, it’s easy to run your own serverless GraphQL service API. Thanks to Velocity Mapping Templates, DynamoDB, and AWS Lambda your can aim for an architecture without any maintenance at all.

Getting started with AppSync is not that problem; there are tons of guides and frameworks. AWS has a nice guide to add a custom domain to your API using CloudFront as well. But how do you configure a custom domain using Route 53, AWS Certificate Manager, and AppSync in a CloudFormation Template? Here’s the answer:

AWSTemplateFormatVersion: "2010-09-09"
    Type: AWS::Route53::HostedZone

    Type: AWS::CertificateManager::Certificate
    DependsOn: HostedZone
      ValidationMethod: DNS

    Type: AWS::CloudFront::Distribution
        Enabled: true
        HttpVersion: http2
          - DomainName: !Ref AppSyncHostname
            Id: !Ref AppSyncHostname
              HTTPPort: 80
              HTTPSPort: 443
              OriginKeepaliveTimeout: 5
              OriginReadTimeout: 30
              OriginProtocolPolicy: https-only
              OriginSSLProtocols: [TLSv1, TLSv1.1, TLSv1.2]
        Aliases: []
          AllowedMethods: [HEAD, DELETE, POST, GET, OPTIONS, PUT, PATCH]
            QueryString: false
          SmoothStreaming: false
          Compress: true
          TargetOriginId: !Ref AppSyncHostname
          ViewerProtocolPolicy: redirect-to-https
        PriceClass: PriceClass_100
          SslSupportMethod: sni-only
          MinimumProtocolVersion: TLSv1.1_2016
          AcmCertificateArn: !Ref Certificate

    Type: AWS::Route53::RecordSetGroup
        - Name:
          Type: A
            HostedZoneId: Z2FDTNDATAQYW2
            DNSName: !GetAtt Distribution.DomainName

    Type: String

After creating your AppSync API, you will end up with a random subdomain for an AWS service. Of course, you want to configure a custom and branded domain for your AppSync GraphQL endpoint. Use the CloudFormation snippet above, provide the hostname of your GraphQL service and use your AppSync API with a custom hostname.

Important: You need to deploy this CloudFormation Stack to us-east-1 region! But you can deploy the AWS AppSync GraphQL API to any AWS region.

  • AWS re:Invent 2019 Recap & Videos

    December 15th, 2019 364 Words

    I was able to attend the AWS re:Invent 2019 conference. A week full of learning about current and new technologies, services, and general approaches is definitely overwhelming. There is no much content available, during the conference, and as videos and slide decks afterwards. I tried to list my favourite talks. There are way too much of them.

  • AWS Single Sign-On and Multi-Account Cloud Setup

    German August 16th, 2019
  • GraphQL with AWS AppSync and AWS Lambda

    German July 2nd, 2019
  • CloudFormation Best-Practices

    May 1st, 2019 573 Words

    You can find plenty of frameworks and tools to provision your AWS resources. Some of them do a great job for a specific purpose, others are more generic. Nevertheless, I do prefer to use native CloudFormation templates as much as possible.

  • Makefile Best-Practices

    April 30th, 2019 235 Words

    The more projects you work on, the more streamlined your tooling gets. Hopefully. Various services using different languages have different tooling requirements, of course. A sweet Makefile can be the entry to a unified tooling interface.