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

Cloud Formation EC2 not created AWS Cloud Personal #98

Open
keserwan opened this issue Dec 30, 2020 · 4 comments
Open

Cloud Formation EC2 not created AWS Cloud Personal #98

keserwan opened this issue Dec 30, 2020 · 4 comments

Comments

@keserwan
Copy link

Dears,

I created Hubs Cloud Personal from AWS Marketplace using Cloud Formation. It worked perfectly on my first AWS account, then I wanted to transfer the domain to another account, after that step I deleted the stack from the old AWS account and migrated the domain to the new hosted zones in the new AWS account.

Once all was ready, I re-did all the setup through Cloud Formation on the new AWS Account. After the setup had complete (successfully), I didn't see any EC2 instance(s) created.

Any suggestions?

Please advise if I am missing anything.

@keserwan
Copy link
Author

I am getting the following error when I visit the main URL:

<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>assets/pages/unavailable.html</Key>
<RequestId>9***************3D</RequestId>
<HostId>
7******2F**************
</HostId>
</Error>

@neonascent
Copy link

@keserwan I am having the same issue under the same circumstances (deploying, then deleting, then creating another stack pointing at old domain names) - where you able to resolve this?

@yondr-agency-15
Copy link

yondr-agency-15 commented Nov 2, 2022

I've noticed this issue after pushing a new client to AWS.
On AWS I checked my S3 services and noticed a different folder structure. Which cause the files to not be found.

My Fix:
https://s3.console.aws.amazon.com/s3/buckets/
In my cases I moved all assets from hubs/assets to hubs/src/assets

PS: (moving ALL assets did break my homepage styling. So I recommend to leave the stylesheets folder or just copy all files instead of moving)

@neonascent
Copy link

@yondr-luka

Thankyou for the fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants