DNS PROVISIONING: Provision Route 53, ACM, Amplify, and CloudFront DNS for a customer.
The last two steps — the API certificate and the API domains — need the core and product stacks to already exist, so run those after the first core and product deploy. Everything they create then survives a rebuild: only the /v1 mapping is repointed, which the 'Get API ID' steps do by themselves on every deploy.
Tab: DNS Provisioning.
This page was generated from the description shown inside VibeStudio. Expand it with the detail an adopter needs — what to do, what good looks like, and what to check when it goes wrong.