Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform.
Trouble tickets are generally answered 9AM - 5PM EST, weekends and holidays excluded. Even though we try our best to assist you quickly, please allow 24-48 hours to hear back from us.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Standing up a Hub on AWS
Download: Download Instructions
In order to stand up a Hub on Amazon Web Services (AWS) you must have an AWS account that has been registered and confirmed.
Sign in to AWS
- Navigate to https://aws.amazon.com/marketplace/
- Sign in to your AWS account
- Click Amazon Web Services Home
- Click Sign In to the Console
- Under AWS Services, click EC2
Create Key Pair
- On the EC2 Dashboard under Network & Security, click Key Pairs
- If Key Pair hasn't been previously setup, you will need to set one up for Amazon
- Click on Create Key Pair
- In the Key pair name field, type XXXX(Name your Key) and click Create
- Save the file to your browser
- Verify that your Key Pair was created
Set-up Your Hubzero Instance
- Navigate back to https://aws.amazon.com/marketplace/
- Search for hubzero in the Shop All Categories
- Your search should return "Hubzero Platform for Scientific Collaboration"
- Click on the title of the Hubzero instance
- On the product description page, determine your region and then click Continue
- Click on 1-Click Launch and verify that your instance type is t2.micro
- Scroll to the bottom and verify that AWS key is present
- Verify that you are okay with the prices and click Launch with 1-click
- You will receive a confirmation page
- You will have to wait a couple of minutes as your instance is deployed on EC2. You should receive an email once your instance is ready.
- When your instance is ready, return to the Product Page
Check-out Your Hubzero Instance
- Sign in and navigate to EC2 and your EC2 Dashboard
- Under Resources select Running Instances
- Click on Public DNS and read the documentation grab
- Navigate back to EC2 and click on Actions then click Instance Settings
- Under Instance Settings click on Get System Log
- Grab your secure admin password by scrolling to the bottom
- Navigate back to your instance and click Jump to Your Hub
- Check-out your instance's interface and read the documentation
Login to Your Instance's /administrator interface
- When you're ready Jump to the /administrator interface
- Login with the username admin and your secure password
- Your browser might flag the site as a failed connection
- Remove the :80 from the URL and refresh the browser
- Then when you receive the "Your connection is not secure" click Advanced then Add Exception
- Confirm your location and either get a Certificate for your instance or click Confirm Security Exception
- Continue logging into the /administrator interface and start configuring your instance
- Your browser might flag the site as a failed connection
Congratulations on setting up a Hub!
- If you have any questions feel free to check out the rest of our documentation.
- If you can't find an article that answers your questions or you run into roadblocks, feel free to put in a support ticket.
- If you are interested in having the Hubzero Team train or help, you can join our Hubzero Foundation community.
- Keep in touch with Hubzero on Twitter @hubzeroplatform and subscribe to our monthly newsletter.
Third Party Email
Hubs are configured to send and receive email directly. However depending on server configuration, some mail servers on the internet may view an email message sent by your hub as SPAM. This can happen for a variety of reasons, ranging from partially setup machines used in development environments, servers that do not have DNS names properly established, MTAs that are not properly configured, etc.
Often you can find and fix specific issues it can help save your hub's email from your users' SPAM folders, but sometimes in cloud environments, your server is assigned an IP address from a pool of addresses where a previous user has used an IP addresses in that range to SPAM in the past, so your IP address itself of your server is blacklisted by various SPAM tracking software packages.
Often using a third party email provider such as Amazon SES or Mandrill can help rescue your outgoing email from your users' SPAM folders. This is an especially important issue for hubs that even occasionally send legitimate mass email to their users.
Steps for configuring EXIM with Mandrill
Setup an account with Mandrill. The free tier of service from Mandril will allow for up to 12000 email per month with no charges.
Login/sudo to your Debian machine as root.
% dpkg-reconfigure exim4-config
Mail Server configuration (page 1)
mail sent by smarthost; received via SMTP or fetchmail
Mail Server configuration (page 2)
enter the fully qualified domain name (FQDN) of the host (example.com)
IP-addresses to listen on for incoming SMTP connections
Other Destinations for which mail is accepted
Machines to relay mail for
IP address or host name of the outgoing smarthost
“Hide local mail name in outgoing mail?”
Keep number of DNS-queries minimal (Dial-on-Demand)
“Delivery method for local mail”
mbox format in /var/mail/
“Split configuration into small files"
root and postmaster mail recipient
- leave blank
Create a file /etc/exim4/passwd.client file as root
% nano /etc/exim4/passwd.client
Enter the following line at the end of the file:
*.mandrillapp.com:SMTP Username:API Key
Note: Go to your mandril app and select the ‘Settings” page from your dashboard to get your SMTP Username and API Key.
Make sure the group and permissions are properly set on the passwd.client file
% chgrp Debian-exim /etc/exim4/passwd.client % chmod 640 /etc/exim4/passwd.client
Suggestions on Expanding Volume
Not a procedure recommended for non-system administrators to try to preform. If you have further questions or need help, contact AWS for help.
- Shutdown the instance
- Snapshot the volume
- Create a new volume from the snapshot (and be sure to specify a large enough size here)
- Detach the old volume from the instance
- Attach the new volume to temporary instance
- In the temp instance, mount the new volume, and run resize2fs so it grows to take advantage of the entire partition space
- Shutdown temp instance
- Remount the new volume to the original instance
- Reboot original instance
Helpful AWS Documents:
You can also create a new volume, and then remount part of the root filesystem there. I usually move /home to the new partition. In this case, they'd probably want to move /var/ there, but it depends on what is taking up the most space on their system. This procedure is outlined here: