S3 resource fails in amplify push for too-long bucket name #13364
Labels
bug
Something isn't working
good first issue
Good for newcomers
p3
platform-push
Issues related to `amplify push`
storage
Issues tied to the storage category
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v18.17.1
Amplify CLI Version
10.7.3
What operating system are you using?
Ubuntu
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
I have created a new environment (with
amplify env add
) namedstuartprod
, and am now trying toamplify push
to deploy the environment. I get the following error:I don't know what the bucket name that it's trying to create actually is, and I don't know how to find out. The name of the whole project is
projnewcomponents
. I note that in the existing environment (calledstaging
), the name of the bucket isprojnewcomponents5ddb(28 hex chars)3503-staging
, which is 61 characters long. So perhaps it's trying to createprojnewcomponents5ddb(28 hex chars)3503-stuartprod
which would be 64 characters long and therefore too long? This is OK if so, but there really ought to be a warning about this somewhere!Expected behavior
Either this shouldn't fail, or, if the constructed bucket name is too long, it should tell me what the failing bucket name is so I can try to resolve it.
Reproduction steps
I don't know what's causing this (although see speculation above) so it's hard to know how to reproduce it.
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: