Standard Naming scheme for resources created as part of an Amplify App.

aws-amplify / amplify-backend

Home to all tools related to Amplify's code-first DX (Gen 2) for building fullstack apps on AWS

Apache License 2.0

185 stars 64 forks source link

Standard Naming scheme for resources created as part of an Amplify App. #925

Open vishal-dms opened 10 months ago

vishal-dms commented 10 months ago

Environment information

N/A

Description

As on today Amplify generated backend resources do not follow any standard naming convention to indicate important details like which amplify app and environment it belongs to. This creates a cumbersome user experience for someone looking at the resources and trying to search for app-related resources. Tagging resources can help to a certain extent but not all services (for e.g. Cognito) support searching/sorting/filtering based on tags.

Workaround

Customers need to manually override each resource name with a naming scheme that includes, Amplify app ID, name and environment along with resource name.

ykethan commented 10 months ago

Hey @vishal-dms, thank you for the feedback. Marking a feature-request.

edwardfoyle commented 10 months ago

Hi @vishal-dms you can navigate to the AWS CloudFormation stack created for your backend. Go to the AWS Console, then navigate to CloudFormation, then find your backend stack. It will be named amplify-<appId>-<branchName>-branch-<hash>. There will be a list of all resources associated with the backend there. Note that some resources are also in nested stacks under the root stack. Hopefully this can help you find all resources related to a single backend.

rupe120 commented 4 months ago

@edwardfoyle while your comment is true, it is very cumbersome to go through the CloudFormation stack to determine which DynamoDB tables are applicable to your environment. What is the NONE on the end of the name?