View/modify amplify CLI published apps in the AWS console?

Hi,

Sorry for the confusion.
Init a project with amplify CLI will not create a AWS Amplify Console. What I would recommend is that push your project to GitHub and Connect your project to AWS Amplify Console. You will be able to set custom domain in AWS Amplify console.

Thanks,
Gary

Hi Gary,

Thanks for the quick reply.

I'm gonna add some more info here, in case anyone come across the same issue and could use the help.

In short, I backed out of the cli hosting by using "amplify remove hosting". I then followed that up with a amplify push, which (I hope) removed all of the cloud elements. In fact, it did not remove the s3 hosing bucket, so I removed that manually.

That done, I used the AWS Amplify Console to connect a Bit Bucket repo with my app code.

On the first build attempt, it failed, as it could not find the src/aws-exports.js file, which was added to the .gitignore file automatically at some point during the setup of the site.

That particular file has what seems to be a lot of sensitive information, so I was hesitant to exclude it from .gitignore.

Tired and bored, and knowing that my bb-repo was private, I added and committed the file and waited.... and viola!

Publishing this way allowed me to add a custom domain.

If anyone has a better way, le me no....

@kimford. You do not need to commit the exports file. This tutorial shows you how to deploy a fullstack Amplify app: https://docs.aws.amazon.com/amplify/latest/userguide/deploy-backend.html

I have the same problem right now.
I build an Angular (Ionic) app with amplify.
When i first deployed the app with the amplify console everything worked fine.
Then my API-Key expired after 7 days. Now, after creating a new API-Key and setting the "APIKeyExpirationEpoch" = "-1" in parameters.json my app throws an error that the API-Key could not be found.

I already deleted my app from the amplify console and creating a new one like in the the link @nikhil1986 posted but still the same problem.
Removing the aws-exports.js from my gitignore solves the problem. But that can't be the long term solution right?

Maybe someone else already solved the problem and can help me?

Thanks so much
Jan