Having issues with Clickdomain SSL Setup - Getting HTTP 400 from r.eu-central-1.awstrack.me

Question

Dear Braze-Community,

we re stuck right at the beginning :-)

After setting up our custom domains,  we cant make our clickdomains work.

our Amazon SES Cluster is: https://r.eu-central-1.awstrack.me/

it returns HTTP 400, which is suppose is expected because it needs a custom domain proxied against it to work.

We use a Google Cloud Platform Load Balancer. SSL works fine.

We point A/AAA records to the LB and have a backend configure to send traffic to r.eu-central-1.awstrack.me.

We setup in our request headers a "Host" which contains our custom clickdomain. i also added a x-forwarded-for with the client_ip just for good measure, still we get a http 400 error.

Is there any request header missing for it to work?

christoph_m · Answer

it seems to work adding the customer click domain name as Host and the client ip as x-forwarded-host to the request header

christoph_m · Answer

you can find it here: https://www.braze.com/docs/user_guide/channels/email/email_setup/ssl

its the SSL termination for the clickdomains. braze uses Amazon SES in our case and we use GCP.  a pure CNAME entry would be easy but its not creating or providing SSL :-)

Manoj__ · Answer

@christoph_m  You can find the documentation to add these DNS entries here: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#CNAMEFormat