Add Storage => Domain already exists
See original GitHub issueSimilar to #1845
Describe the bug I have Auth, Function and Api services in place. I added Storage service and pushed. The error on Cloudwatch has this messages:
- message:
Domain already exists.
, code:AccessDeniedException
- message:
User XXXXX is not authorised to perform: cognito-idp:DeleteUserPoolDomain on resource: XXXXX
code:InvalidParameterException
- same as n.2
- same as n.2
But the bucket on S3 is created
Expected behavior successful s3 storage creation and use on the project
Additional context amplify version: 1.8.5
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
RHEV: Error while executing action: Cannot add Storage ...
Storage connection already exists. ... myself in a situation where I was trying to re-add an existing NFS share to use as a...
Read more >1951548 – Hosted-engine setup fails while upgrading from ...
Description of problem: This bug was hit while upgrading setup from 4.3.x to 4.4.x (last was to 4.4.5) in two different setups with...
Read more >8.7. Importing Existing Storage Domains
Click Storage → Domains. · Click Import Domain. · Select the Data Center you want to import the storage domain to. · Enter...
Read more >Import Storage Domain - oVirt
Press the “import Storage Domain” button. · Choose a file type domain (NFS, POSIX, etc.). · Provide the path where this Storage exists...
Read more >Why am I getting a “DNS zone already exists” error in Cloud ...
The “DNS zone already exists” error indicates that the domain you're trying to add already exists in our system on a different customer's ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@AlessandroVol23 I suspect what’s happening is that, when you’re modifying/adding a custom attribute (which are immutable and shouldn’t be updated after creation), Cloudformation is creating a new user-pool for you (with the new custom attributes), retaining the old one and trying to spin up a new hosted UI (with the same domain) as the previous user-pools hosted UI domain which still exists. To get around this, you might want to delete the old cognito user-pool and remove the hosted UI endpoint using the AWS console to make the push succeed.
This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server
*-help
channels for those types of questions.