✅ - Runtime version error and after I got S3 bucket name is already taken | AWS Amplify | Page 1

twilit quarry · 2022-11-16T15:12:29.314Z

1. So I use amplify version 4,24,3 because one of the tutorial I was following use that version 2. When I ran amplify push I got that runtime need to be node16x. and not node10. so I changed it to version 16. 3. I run amplify push again and what I got was that S3 bucket name is taken.

twilit quarry Nov 16, 2022, 3:12 PM

#

So I use amplify version 4,24,3 because one of the tutorial I was following use that version
When I ran amplify push I got that runtime need to be node16x. and not node10. so I changed it to version 16.
I run amplify push again and what I got was that S3 bucket name is taken.

#

I would appreciate help and advice

vocal roost Nov 16, 2022, 5:53 PM

#

Hey 👋 version 4 of the Amplify CLI is quite old at this point. I would suggest upgrading to latest. What's the tutorial you're following?

twilit quarry Nov 17, 2022, 9:54 AM

#

https://www.youtube.com/watch?v=JgwI22y_eFA&ab_channel=freeCodeCamp.org

#

This tutorial 🙂

#

So I upgraded it to the latest one and I did the GraphQL migration with the new rules. Thanks for you help

ocean dock Nov 17, 2022, 2:48 PM

#

Thanks @twilit quarry! Glad that your problem was resolved with the latest upgrade to CLI 🙂 Marking this thread solved.

sharp lavaBOT Nov 17, 2022, 2:49 PM

#

✅ - Runtime version error and after I got S3 bucket name is already taken

#✅ - Runtime version error and after I got S3 bucket name is already taken