Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to Append Environment Name to All Resources Created by Amplify Backend #2451

Open
anishniroula1 opened this issue Jan 27, 2025 · 1 comment
Labels
feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed

Comments

@anishniroula1
Copy link

Environment information

Hi Amplify Team,

Is there a way to automatically/manually append the environment name (e.g., -dev, -prod) to all resources created by Amplify in the backend, such as DynamoDB tables, S3 buckets, etc.?

If this is possible, could you provide guidance or documentation on how to implement it globally for all resources?

Thanks!

Describe the feature

Feature Request: Append Environment Name to All Resources Created by Amplify Backend

Description:
Introduce a feature in Amplify to automatically append the current environment name (e.g., -dev, -prod, -test) to all resources created by the Amplify backend (e.g., DynamoDB tables, S3 buckets, Lambda functions). This would help in:

Resource Identification: Easily distinguish resources across different environments in the AWS Management Console.
Avoiding Conflicts: Prevent resource name conflicts when using multiple environments in the same AWS account.
Expected Behavior:
Amplify should either:

Automatically append the environment name to all resource names.
Allow a global configuration option to enable/disable this behavior.

Use case

In a multi-environment setup (e.g., dev, test, prod), managing backend resources across environments becomes challenging when resources don’t include environment-specific identifiers in their names.

For example:

Without the environment name, DynamoDB tables or S3 buckets might have generic names like TableName-NONE, making it difficult to distinguish which resource belongs to which environment.
This could lead to accidental resource usage or conflicts between environments when multiple environments share the same AWS account.
By appending the environment name (e.g., -dev, -prod) to all resources:

Developers can easily identify resources in the AWS Management Console or CLI.
It avoids naming conflicts, especially when managing multiple environments in the same AWS account.
It improves clarity and organization for resource tracking and debugging.
This feature would streamline multi-environment development and reduce errors in resource management.

@anishniroula1 anishniroula1 added the pending-triage Incoming issues that need categorization label Jan 27, 2025
@ykethan
Copy link
Member

ykethan commented Jan 27, 2025

Hey, thank you for reaching out. Marking this as feature request.

@ykethan ykethan added feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed and removed pending-triage Incoming issues that need categorization labels Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request needs-product-input Needs non-technical requirements or direction to proceed
Projects
None yet
Development

No branches or pull requests

2 participants