aws-amplify / aws-amplify/amplify-cli
Inconsistent naming of S3 buckets
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 825
- Avg merge
- 11d 23h
- Merged PRs (30d)
- 2
Description
**Describe the bug**
The way buckets are named is not consistent between `deployment` and `hostingBuckets`
**To Reproduce**
Create any environment via the Amplify CLI and publish it.
The deploy and hosting buckets will in inject the `environment name` at different positions in the bucket name making it harder than necessary to spot which buckets belong together. Example:
**Expected behavior**
Have a clear convention like:
* appName-env-deployment
* appName-env-hosting
;or
* appName-deployment-env
* appName-hosting-env
Contributor guide
Research direction
Start by reproducing the issue with the Amplify CLI and trace how names are generated for deployment and hostingBuckets. Compare the two naming paths against the proposed convention; done means newly created buckets place the environment name consistently and remain easy to associate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100