Amplify configured for next.js is not removing all resources

0

Hi we have issues using Amplify configured as Next.js. We had an app with d28nwgksusfkk0 than now is deleted. I noticed that some PRs and branches after being closed still had cloudfront, s3 buckets, Lambda functions and cloudwatch log groups. This is a big problem because at some point the buckets are more than 100 and we are over quota. Also I'm not sure if we are paying more for things that we are not using. We have other apps using Amplify and we don't even see all their infrastructure(cloudfront, S3...). I think there's a bug somewhere in Amplify for Next.js and Bitbucket. Now they are 3 cloudfronts and buckets even after deleting the app. Cloudfront IDS: E3CDR1ZN4TVPC, E3VT9FDUFW0OQN, EEYQSHDEE3LX5. Let me know if you need more information.

  • What's the status of this issue? I still have some AWS resources not deleted from Amplify

  • Hello rePost-User-8960215, Seems like there might be something with the way you've configured Amplify. We suggest to get support team involved to look into your configuration. The best route at this point would be to open a support ticket.

1 Answer
1

Hello,

Sorry to hear this is happening. If you'd like to contact our Amplify team directly for assistance, you can reach out via email: aws-amplify-customer@amazon.com. Alternatively, you can contact our Amplify team via chat on their Discord community page: https://discord.com/invite/amplify.

Kind regards,

-Marc O.

AWS
EXPERT
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions