IMO we should exclude R53 rules from the CF template that we will share with partner organization. Or at least provide a template that can be used without the partner organization having to register a domain name. The best way to achieve this is probably to add R53 rules to the CF template but commenting them by default and adding a note that the partner organization should register their own domain name first and then update the template before using it. It's a probably a better solution than having two CF templates - with and w/o R53 rules - to avoid having to maintain duplicated content.
@thomasyu888 Xa and I are close to finalize the redirections. Currently we got https://www.nlpsandbox.io working but not https://nlpsandbox.io.
IMO we should exclude R53 rules from the CF template that we will share with partner organization. Or at least provide a template that can be used without the partner organization having to register a domain name. The best way to achieve this is probably to add R53 rules to the CF template but commenting them by default and adding a note that the partner organization should register their own domain name first and then update the template before using it. It's a probably a better solution than having two CF templates - with and w/o R53 rules - to avoid having to maintain duplicated content.