Amplify auto generated resources

2

Is there some way to tell which auto generated resources (cognito user pools, lambdas, etc) go with which amplify project? Some config file or console page or query I can issue that will show me the "inventory" of all the auto generated components that "go with" any specific amplify project?

Some details:

I have created a number of test amplify projects, and deleted some but not others. Of course there were occasional failures. I want to delete stuff that is left over from failed project deletes, but how do I tell which pieces go with which amplify project so I can determine if I still need the piece or not?

For instance, in addition to the cognito user pool associated with my auth (listed on the console page, and actually contains my users and groups so I know it's the right one), there are a number named "amplify_backend_manager_<<some-id>>". Not sure what they are for, or whether I still need any/all of them.

Also, in addition to the one lambda I explicitly created, there are a number named something indicating their purpose (such as "amplify-login-create-auth-challenge", "amplify-login-custom-message", "amplify-login-define-auth-challenge", "amplify-login-verify-auth-challenge") followed by some sort of id. Each id has all of the associated lambdas; there are at least 5 different sets... but I only have 1 amplify project at this point. Not sure which ones go with my project.

Can't seem to find an answer in the docs. Any help would be appreciated.

Thanks!

2 Risposte
0

I'm not sure about Cognito pools specifically, but Amplify resources are created using CloudFormation so many of them will automatically be tagged with the related CloudFormation information such as stack name and ID. You could use this to track which pool is related to which stack, and the associated Amplify application.

profile picture
rowanu
con risposta 2 anni fa
0

Resources created via amplify will have the name of the project included in the name of the resource that was created.

JeffM
con risposta un anno fa

Accesso non effettuato. Accedi per postare una risposta.

Una buona risposta soddisfa chiaramente la domanda, fornisce un feedback costruttivo e incoraggia la crescita professionale del richiedente.

Linee guida per rispondere alle domande