Get Your Hub Ready for Migration to AWS


We will soon be migrating the Uberflip platform to Amazon Web Services. Here's what you need to check on to make sure your account, Hubs, Flipbooks, etc. can be migrated seamlessly.

Archived Article

This article references a past event. The information it contains may no longer be accurate, and remains available for reference only.


Migration to AWS: What You Need To Know

Uberflip is growing, and that means we're rapidly approaching the capacity limits of our current server infrastructure. To future-proof our services and keep them running reliably, we are moving to Amazon Web Services (AWS). The migration will take place progressively over six to eight weeks between early May and late June 2019, and is expected to be finalized by July 1.

AWS is the world's largest provider of cloud computing services, and moving to AWS will allow us to scale at the pace we need, without sacrificing the performance of our platform. If you'd like to learn more about why we're making this change, please check out our blog post about the AWS migration.

For most of our customers, this migration will not require any action: all of your Uberflip assets, (including your account, Hubs, Flipbooks, content, etc.) will simply be moved over to AWS, and you shouldn't notice any change.

However, it's possible that your IT infrastructure is set up in such a way that the migration will not be seamless for you. If this is the case, you will need to take action to prepare for the migration and ensure your Uberflip assets remain accessible.

In this article, we'll explain what you need to check on to determine if any action is required on your part, and what exactly you'll have to do if there is.


What's Changing, And What That Means For You

Most of the changes that are happening as part of this migration are behind the scenes, and won't impact you directly. But there is one major aspect of the migration that may affect you: Uberflip's IP addresses are changing.

For the majority of our customers, this will not be an issue. Because we handle everything through domains (like and, you generally don't need to worry about the IP addresses that they are tied to: even if the underlying IP addresses change, the domains stay the same, so the change is effectively invisible.

However, if you reference specific Uberflip IP addresses anywhere within your IT infrastructure, then this change will have a significant impact on you. When Uberflip's IP addresses change, any system that relies on the old IP addresses will break, which can cause your Uberflip assets (including Hubs, the Uberflip application, Flipbooks, etc.) to become inaccessible.

As a result, you should check if you are referencing specific Uberflip IPs anywhere. There are three general areas in which you may have done so, and which would therefore be affected by the migration:

  • DNS records
  • Reverse proxy configuration
  • IP restriction rules (e.g. firewall)

To ensure a smooth, seamless migration, you should check each of these areas and take any necessary corrective action prior to July 1. To do so, simply follow the steps below.

Important Note

The following sections are intended for readers with an IT/networking background. They assume familiarity with basic networking terminology and concepts, and describe steps that would typically need to be completed by an IT or web administrator.


Step 1: Check DNS Records 

You very likely have set up DNS records relating to Uberflip, especially if you use a custom domain. If you have created any DNS records for domains that you own which reference Uberflip IPs, you will need to change them.

What You Should Look For

Check the DNS records for your custom domain(s). If your DNS records are:

  • CNAME records pointing to
    → No action needed
  • CNAME records pointing to a domain other than
    → Action recommended (but not required)
  • A records pointing to an Uberflip IP address

Tip: Checking DNS Records

Your DNS provider will typically provide tools for viewing the DNS records for your domain. Alternatively, you can also use the command line tool Dig, or a web-based version like Dig web interface or G Suite Toolbox Dig.

What You Need To Do

If any of the DNS records for your Uberflip-related domains are A records, this means that they point to a specific IP address. As a result, your service will be interrupted when the IP address changes.

To avoid this, change any A records to CNAME records that point to instead:


You don't need to wait until the migration date to do this — if you need to change your DNS records, we recommend doing so as soon as possible.

Note: Non-Custom Domains

If you do not use a custom domain, but instead use a default co-branded Uberflip domain, then you do not need to take any action. This includes any domains in this format:


Note that if you check the DNS records for this kind of domain, you will see an A record pointing to an Uberflip IP address. This is normal, and we will take care of updating this A record as part of the migration.

You may also have older CNAME records that point to a domain other than, specifically:


If this is the case, we strongly recommend changing these records to the domain, which is now our sole supported domain. However, if you do not do this, your service will not be interrupted as a result of this migration (though it may be affected in the future).


Step 2: Check Reverse Proxy Configuration

You may use a reverse proxy (via a web server, CDN, or load balancer) to serve your Uberflip Hubs or Flipbooks, most commonly if you use a subdirectory custom domain. If your reverse proxy configuration references Uberflip IPs anywhere, you will need to change it.

If you know that you do not use a reverse proxy in any capacity, you can skip this and proceed to the next step.

What You Should Look For

Review your reverse proxy's configuration. If it is set up to proxy traffic to:

  • The domain
    → No action needed
  • An IP address like

What You Need To Do

If you have configured your reverse proxy to send traffic to an Uberflip IP address, rather than the domain, your service will be interrupted when the IP address changes.

To avoid this, change your proxy configuration so that it connects to rather than the IP address.


Step 3: Check IP Restriction Rules

You may enforce IP restriction rules within your organization, for example via a network firewall, web proxy, or local firewall software. If any of these rules reference Uberflip IPs, you will need to update them.


In addition to firewalls, here are some examples of other services you might be using that may have IP restriction rules in place:

  • Private FTP/SFTP servers that Uberflip connects to in order to download PDFs to convert to Flipbooks
  • Private RSS feeds that are connected to Streams in your Uberflip Hub
  • Marketing Automation Platforms (e.g. Marketo, Eloqua, HubSpot, etc.) or Custom Form CTAs that Uberflip connects to for progressive profiling of visitors and for capturing Form CTA submissions and activity data

If you know that you do not use any mechanism that restricts connections based on IP address, you can skip this step.

What You Should Look For

Review your IP restriction rules. If these rules:

  • Only prevent connections to/from specific IP addresses (outbound/inbound connection exclusion)
    → No action needed
  • Only allow connections to specific external IP addresses (outbound connection inclusion)
  • Only allow connections from specific external IP addresses (i.e. inbound connection inclusion) AND you host or manage services that Uberflip must connect to

What You Need To Do

If you use an IP inclusion system, and it currently references Uberflip's IP addresses, your service will be interrupted when Uberflip's IP addresses change.

To avoid this, update any applicable rules with Uberflip's new IP addresses. The new IP addresses you must allow are:

Outbound Traffic from Your Systems

The following IPs are used to connect to Uberflip domains and services:

Inbound Traffic to Your Systems

Uberflip connects to customer systems using the following IPs:

Note: While these IP addresses are accurate and complete as of this writing, we may use additional IP addresses not listed here in the future. In such an event, we will separately communicate the change.


What's Next

If you have checked the three areas outlined in this article and have determined that you need to take no action, you're all set. If you do need to take some corrective action, you should do so prior to July 1 — ideally as soon as possible. Services will continue to work on the old IP addresses until at least July 1, but may be degraded as we get closer to that date.

Provided your Hub is ready by July 1, it will be automatically moved to AWS with no further action required on your part, and the change will be completely invisible to your visitors and users.

If you have any questions about the migration, please don't forget to check out our blog post, and of course you can also contact our Support Team for help.

0 out of 0 found this helpful



Please sign in to leave a comment.