Last updated January 22, 2020
Welcome! This guide helps new users like you get started with Fastly as quickly as possible.
We want to help you get the most out of Fastly's edge cloud platform. Whether you run a WordPress site that gets a couple thousand impressions per month or an enterprise web application that receives millions of page views per day, we want to help your websites and apps perform faster, safer, and at global scale.
We've created this page to help you get started and then explore our other products and services.
1. Get to know Fastly
New to the world of content delivery networks (CDNs) and edge computing? Learn how Fastly can speed up your website or app by reading through our guides on getting started, how Fastly's CDN service works, and how caching and CDNs work.
2. Create an account
3. Create your first service
Once you've created an account and you're logged in, familiarize yourself with our web interface so you can get more comfortable playing with configuration settings. See our guide on web interface controls for more information.
You'll be working with a service: a set of caching rules and settings for your website or application. Services are version controlled so you can always roll back to a previous version of a service. See our guide on working with services for more information.
4. Connect an origin server
To take advantage of your configurations, you need to connect your Fastly service to an origin server so we can cache your content. You'll sometimes see the origin referred to as a "host" or "backend" server. Your origin server is whatever cloud service or web server that contains the content of your website or application. Fastly caches the content stored on your origin server at points of presence (POPs) around the world.
You can add the hostname of your origin server on the Origins page, as shown below. See our instructions on connecting to origins for more information.
5. Add a domain name
Once you've connected your Fastly service to an origin server, you can add your domain name to your service. Your domain name is what people type in a web browser to locate you (such as
www.example.com). Don't worry — adding a domain name won't have any impact on your production traffic until you change your DNS records. More on that in a bit.
You can add your domain name on the Domains page, as shown below. See our instructions on working with domains for more information.
We recommend that you don't use apex or second-level domains with Fastly. For example, you should use
www.example.com and not
6. Activate and test
Now for the fun part: activating your service and testing it. Activation might sound scary, but you're just saving the origin server and domain name settings in your service (you do it when you click the green Activate button as shown below). Activation won't have any impact on your production traffic. See our instructions on activating versions of services for more information.
After your service is activated, you can start testing. Click the Test domain link on the Domains page to check how your website or application loads with Fastly. See our testing setup guide for more information.
When you're ready to make more changes to your service, click Clone to create a new version of the service. You can edit this version and then activate it when you're ready to save the changes.
7. Go beyond the basics
Congratulations! You've successfully configured Fastly to cache your content. But before you go live, take a look at some other features you can enable. After all, you've only just started discovering what Fastly is capable of doing. This section provides an overview of some of our most popular features. Of course, it's up to you to pick and choose which of these to enable, if any.
When you make a change to your site, you have to purge the cached content so Fastly fetch the new content from your origin server. You can do this manually or programmatically. See our guide on single purges for more information.
By designating a Fastly POP to serve as a shield for your origin server, you can increase the cache hit rates for your Fastly service and potentially protect your origin server from unexpected spikes in requests for content. See our guide on shielding to learn how to enable origin shielding.
Set up streaming logs
To help you tune the performance of your Fastly service, we support real-time log streaming of data that passes through Fastly. We support a number of protocols that allow you to stream logs to a variety of locations, including third-party services, for storage and analysis. See our guide on setting up remote log streaming to learn how to set up streaming logs.
Serve stale content
Fastly can optionally serve stale content when there is a problem with your origin server or if it's taking a long time to fetch new content from your origin server. For example, if Fastly can't reach your origin server, our POPs will continue to serve cached content when users request it. See our guide on serving stale content to learn how to enable this feature.
Configure custom responses
Fastly can send custom responses for certain requests that you don't want to reach your origin server. For example, you can configure responses for a robots.txt file and 404 and 503 error pages. See our guide on custom responses that don't hit origin servers for more information.
Set up health checks
Health checks monitor the status of your hosts. Fastly performs health checks on your origin server based on a check frequency setting. This feature is typically used conjunction with the serving stale content feature and failover. See our guide on working with health checks to learn how to enable this feature.
Enable automatic gzipping
Fastly's gzip feature dynamically fetches content from origin, compresses it, and then caches it. Compression is a simple, effective way to save bandwidth and speed up your site. See our guide on enabling automatic gzipping for more information.
You can use conditions to control how requests are processed. Conditions add logic to any basic configuration object in a service and control if and when that object is applied. See our about conditions guide for more information.
Embed Fastly in your application
Start using VCL
Explore other products and services
8. Go live
You've connected an origin server, added a domain name, tested your service, and added extras. Now it's time to go live. To move production traffic to Fastly, you need to modify your DNS records to point to Fastly. See our adding CNAME records guide for more information.
9. Set up TLS
We strongly recommend securing traffic between Fastly and your customers using Transport Layer Security (TLS) as soon as possible. Once you're a paid customer, Fastly TLS allows you to add five free domains to your account. See our instructions on serving HTTPS traffic using Fastly-managed certificates for more information. You can also enable HSTS.Back to Top