aws-amplify / aws-amplify/amplify-hosting
Issues with Domain Association and Amplify App Deletion
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
### Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.
### App Id
d3gruxw5sqfod9
### AWS Region
us-east-1
### Amplify Hosting feature
One click deploy
### Frontend framework
Next.js
### Next.js version
12.2.6-canary.9
### Next.js router
App Router
### Describe the bug
I am encountering multiple issues with AWS Amplify and Route 53, including domain suspension due to unverified email, unexpected deletion of an Amplify app, and problems reassociating the domain with a new Amplify app.
### Expected behavior
My Amplify app shouldn't have been deleted by was automatically.
### Reproduction steps
1. Launched a web app with a custom domain using AWS Amplify and Route 53.
2. Received a domain suspension notice due to an unverified email from the domain issuer.
3. The original Amplify app appears to be deleted without notification.
4. Created a new Amplify app with the same source code.
5. Attempted to associate the previously used domain with the new Amplify app.
6. Encountered an SSL configuration error and a CNAMEAlreadyExistsException.
### Build Settings
_No response_
### Log output
```
# Put your logs below this line
```
### Additional information
Attention: I don't have the previous deployed web app since it's already been deleted by AWS for no reason so the app-id I provided is just the second app I created later on, and I just wanted my first app back on so that I can disconnect my domain from the first one and connect the domain to the second one :)
Contributor guide
Research direction
Start with the reproduction steps and the reported SSL configuration error and CNAMEAlreadyExistsException; the issue does not identify repository files, tests, or an entry point. Confirm whether the original Amplify app was deleted and why the domain remains associated, then document a verified way to detach and reassociate the domain without unexpected app deletion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, next.js
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100