Amplify App - entire app - unwanted disappearance, and not deleting completely when actually deleting.

[TradeFuse]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [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

dyyvoq47s0kba

AWS Region

us-west-1

Amplify Hosting feature

Deployments, Not Applicable

Describe the bug

• About 10 days ago we had an entire Amplify app disappear from the "All Apps" Section in Amplify after leaving the Amplify console up for an extended period of time, then logging back in. We shrugged it off thinking it was our mistake. Linked to the "original" GitHub account. We then setup an Amplify App, which worked.
• A few days ago, we created a new Amplify app and deleted the old one and linked to a different temporary GitHub account. No issues at all.
• Earlier today, we decided get rid of that working Amplify App as we needed to connect back to the "original" GitHub account. After deleting the app, and some navigating around, the Amplify App from a few days ago reappeared in our Amplify Apps. Keep in mind we deleted this one already. We redeleted it, and created a new Amplify app connected to the "original" GitHub Account - the original intention of today. We received the error "CNAMEAlredyExistsException". Waited an hour, not working. It says in the supporting docs to then wait 6 hours. We did so; the issue still persisted.
• Just now, after 6 hours of waiting for any previous source to be unlinked and linking domains was still not working, we tried deleting the app that we created earlier today and create a new, fresh one. Did so, opened a new window and moved that window to my other monitor, and after refreshing the Amplify Apps, the App from a few days ago appeared again and the Amplify App I just created - it was in the process of running the build - disappeared. It seems like deleting an app does not work properly, and also leaving sessions open for too long or creating 2 windows for the Amplify App is prone to complete deletion of any previous progress which is very frustrating.

Expected behavior

Amplify Apps should be completely deleted when you delete. Previously deleted Amplify Apps should not reappear. Amplify Apps should not delete themselves after extended sessions in the console or after creating a new window and moving to another screen.

Reproduction steps

I'm not sure if this is a guarantee, but try

1. Create an amplify app like normal. Link to a github repo.
2. Wait until it auto logs you out due to timeout. See if the app is deleted.
3. If it's not, delete the app.
4. Create a new app linked to the same Gihub repo.
5. Duplicate the window and move to another screen.
6. On the duplicated screen, refresh the page and login out and back in. Do this a few times.
7. Go back to the original window and refresh. See if the app you just deleted reappears.

Build Settings

No response

Log output

# Put your logs below this line

Additional information

No response

[ghost]

Hi @Logiq-repos 👋🏽 we have a known bug where sometimes deleting applications directly from the console may be unsuccessful. In these cases, the workaround is to delete the backend environment via the AWS CLI and then delete the frontend application in the console. To delete the backend environment please run this command:

aws amplify delete-backend-environment --app-id <APP_ID> --environment-name <ENV_NAME>

Doc reference: https://docs.aws.amazon.com/cli/latest/reference/amplify/delete-backend-environment.html

To confirm that your app has been successfully deleted, please run the aws amplify list-apps command to make sure the app is no longer listed: https://docs.aws.amazon.com/cli/latest/reference/amplify/list-apps.html.

Please let us know if the above steps help you confirm deletion of the appropriate applications. The application periodically disappearing from the console needs to be further investigated so I will try to reproduce this behavior with the steps you provided.

[TradeFuse]

Hi hloriana, we do not have a backend environment setup; we are only using the hosting environment.

We ran into another bug today - in the last part of the original comment, we said that the Amplify App from a few days ago reappeared...it actually appeared to be working as we did a manual redeploy and the app properly updated. We also setup the access controls with no issues. Logging into AWS today, we discovered that Amplify deleted all those updates we did and is now giving us domain linking issues due to "CNAMEAlredyExistsException" again. Waiting will not work; the Amplify App that was supposed to be deleted from a few days ago still has some data residing somewhere in the AWS Amplify system that we cannot delete at the moment.

[TradeFuse]

Just to clarify, the CNAME error we are getting is

The following CloudFront distributions or Amplify Apps are already using one or more of your domains: [Distribution: *******YPBE0FU in AWS Account: ******359175]

We do not have an account with the last digits 359175, and there is no distribution in our account ending with YPBE0FU

[brunkb]

I am having a similar issue deleting apps--we did "amplify init" and got an error back stating that we had exceeded our 25 app limit, but we only have 3 apps right how. We have added/removed some recently, however. But right now I can't successfully get through the process of adding new ones.

[KaranKhirsariya]

Just to clarify, the CNAME error we are getting is

The following CloudFront distributions or Amplify Apps are already using one or more of your domains: [Distribution: *******YPBE0FU in AWS Account: ******359175]

We do not have an account with the last digits 359175, and there is no distribution in our account ending with YPBE0FU

I'm also facing similar issue where my website root domain was previously hosted on vercel.app and now after deleting the hosting from vercel, I changed my dns provider as route 53 and tried to add custom domain for my amplify app. I get One or more of the CNAMEs you provided are already associated with a different resource. (Service: AmazonCloudFront; Status Code: 409; Error Code: CNAMEAlreadyExists; Request ID: 0ac55b2f-4821-4ad6-830f-3f6f45840b74; Proxy: null) After checking the distribution id I found it's still with some other account as below. Although I'm not sure if vercel.app is using this account or not. "DistributionId": "*******CIDM0F2", "AccountId": "******164913"

[karthikeyansundaram2]

facing same issue amplify app not showing on the amplify console appId d1x20x5yrvmc5n

[henriacle]

Something similar is happening to me. I deleted the Amplify app. When I try to add a CNAME to CloudFront, I receive the following error: One or more of the CNAMEs you provided are already associated with a different resource. I ran the command aws cloudfront list-conflicting-aliases, and the CNAME is attached to an account that is not mine.

{
    "ConflictingAliasesList": {
        "MaxItems": 100,
        "Quantity": 1,
        "Items": [
            {
                "Alias": "www.****.com.br",
                "DistributionId": "*******WOOP2BA",
                "AccountId": "******171576"
            }
        ]
    }
}

Perhaps Amplify is using an internal account to create the resources and not properly deleting it, now the ID does not exist anymore. I can't do anything to fix it.

This is really concerning.