# Welcome! ## Introduction to FlashEdge FlashEdge is a versatile platform designed to enhance content delivery performance and security. It offers a range of features and functions tailored to optimize content delivery, improve website speed, and protect against online threats. With a user-friendly setup and competitive pricing, **FlashEdge provides enterprise-grade solutions that are accessible to businesses of all sizes.** {% content-ref url="/pages/4tF3HHd54QAJYj1VtslF" %} [Introduction to FlashEdge CDN](/welcome/introduction-to-flashedge-cdn) {% endcontent-ref %} ## # Introduction to FlashEdge CDN FlashEdge CDN (Content Delivery Network) is a web service that speeds up the delivery of your static and dynamic web content, such as .html, .css, .js, and image files, to your users. FlashEdge delivers your content through a worldwide network of data centers called edge locations. When a user requests content that you're serving with FlashEdge, the request is routed to the edge location that provides the lowest latency (time delay), so that content (typically images or other static files) is delivered with the best possible performance. ### How does FlashEdge CDN work? * If the content is already in the edge location with the lowest latency, FlashEdge delivers it immediately. * If the content is not in that edge location, FlashEdge retrieves it from an origin that you've defined, such as an HTTP server (for example, a web server), an Amazon S3 bucket, or any other publicly *accessible* origin that you have defined as the source of your content. ![](https://2573132646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGEg7GGm9CN7xkty0CC7a%2Fuploads%2FmVu0VObHMbUfKIwmDUSi%2Fflashedge3.png?alt=media\&token=5322d4d3-335c-4693-b3a4-6fd1d6cc1bd3) As an example, suppose that you're serving an image from a traditional web server, not from FlashEdge. You might serve an image, sunrisephoto.png, using the URL . Your users can easily navigate to this URL and see the image. But they probably don't know that their request is routed from one network to another, through the complex collection of interconnected networks until the image is found. FlashEdge speeds up the distribution of your content by **routing each user request through the worldwide optimized network to the edge location that can best serve your content**. Usually, this is a FlashEdge server that provides the fastest delivery to the viewer. Using the optimized route significantly reduces the number of networks that your users' requests must pass through, which improves performance. **Users get lower latency (the time it takes to load the first byte of the file) and higher data transfer rates.** ![](https://2573132646-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGEg7GGm9CN7xkty0CC7a%2Fuploads%2F3qVw7RjM8eizjtsp7d6f%2Fflashedge1.png?alt=media\&token=60e9f6f1-ff70-44ac-b59e-1d9813f36ed7) You also **get increased reliability and availability** because copies of your files are now cached in multiple edge locations around the world. ### FlashEdge distribution To start using FlashEdge, you will first need to create an account and a distribution. After creating a new distribution, FlashEdge will create a new domain address such as xxxxxxx*.flashedgecdn.net*. You will then be able to use this address in your DNS or application. FlashEdge will automatically fetch and cache files from your origin server. For example, if your file is located at:\ *** The same file will now be available at\ \_**\*\** # Introduction to FlashEdge Storage {% hint style="info" %} **FlashEdge Storage is currently available only to paying customers.** {% endhint %} Welcome to FlashEdge Storage, a scalable and high-performance storage service that seamlessly integrates with FlashEdge CDN. Whether you need to store static assets, application data, or large media files, FlashEdge Storage offers a reliable solution with robust security and ease of use. Every FlashEdge Storage needs the FlashEdge CDN for public access. So, the final infrastructure and how it works are shown in the diagram below.
Private access to browse, upload, and download files is done by file explorers that have to support access to Amazon S3 and specific S3 buckets. We have selected some of the best options and described them in our documentation. # Getting started with FlashEdge Click the “Get Started for Free” button on the FlashEdge web page and finish the simple registration process. Alternatively, you can contact FlashEdge’s sales team to assist you with the deployment and configuration of the CDN solution. If you have a volume greater than 100TB and would like to get customer support and custom pricing, please reach out to the sales team. # Creating a FlashEdge account Experience the efficiency of FlashEdge – your solution for faster digital content delivery! To begin, visit our [account creation page](https://www.flashedgecdn.com/free-trial), where you'll encounter two user-friendly options: ### Option 1: Try a Free Trial Start your journey with a 14-day free trial by choosing the "[Try Free Trial](https://www.flashedgecdn.com/try-free-trial)" offering. Designed for those seeking a firsthand experience of FlashEdge CDN's capabilities, within moments, you'll gain access to the tools you need. This option comes packed with benefits that include: * Access to FlashEdge CDN Features: Immerse yourself in the spectrum of FlashEdge CDN's features, designed to elevate your content delivery, and boost performance. * 200+ PoPs (Points of Presence) in Europe and the US: Benefit from a robust network infrastructure with over 200 PoPs strategically positioned across Europe and the US, ensuring optimal content delivery to your global audience. This can be enhanced after your free trial ends to 450+ PoPs around the globe. * Generous free Data Transfer and Requests: Enjoy a substantial allocation of 100GB data transfer out from FlashEdge to the internet (upgradeable to 500 GB by contacting support) and 20,000,000 HTTP or HTTPS requests, providing room to experiment and fine-tune your content delivery strategies. * No Commitment, No Credit Card Required: Experience the freedom to explore without any commitments or credit card obligations. Dive into the trial with peace of mind. * Seamless AWS Integration: Seamlessly integrate your FlashEdge CDN experience with Amazon Web Services (AWS), enhancing your content delivery through a synergistic cloud-powered solution and benefit from free data transfer between AWS services and FlashEdge locations. ### Option 2: Individual Trial & Assistance For those seeking a more personalized journey, our "[Individual Trial & Assistance](https://www.flashedgecdn.com/individual-trial/)" pathway is your gateway to a tailored approach. The FlashEdge CDN team stands ready to provide: A Personalized Approach and Tailored Offer: * Collaborate closely with us to create a CDN solution that aligns precisely with your unique requirements and aspirations. * Expanded Access to PoPs: Benefit from an expanded network of PoPs (500+), strategically positioned to ensure swift and reliable content delivery to your audience. * Consulting and Implementation Services: Navigate the implementation process with expert guidance, ensuring seamless integration of FlashEdge CDN into your current digital ecosystem. * Custom PoC (Proof of Concept) for Your Project: Test the solution with a custom Proof of Concept designed specifically for your project's needs. * Comprehensive CDN Insights: Get answers to any CDN-related questions you have, empowering you to make informed decisions. * AWS Cloud Expertise: Leverage our expertise in AWS Cloud services to optimize your CDN setup or any infrastructure-related decisions and amplify the benefits of AWS Cloud. # Flashedge CDN distribution tutorials # How to create your first FlashEdge CDN distribution ### Create a first FlashEdge distribution for external origins After you complete the creation of your account you can create your first distribution. {% hint style="info" %} We have simplified a distribution creation and many advanced settings are in the console after the distribution creation. {% endhint %} Complete the following procedure to create a distribution. 1. Sign in to the [FlashEdge](https://www.flashedgecdn.com/login). 2. Click on **“Deploy Resources”** on the FlashEdge Console home page. 3. Choose your Origin source - **"External Site"** * Fill in the domain of your origin. An origin can be any service that has a publicly accessible domain name. For example (yourservice.com, app.yourservice.com, long.domain.name.com) * Fill in the name of the Zone 4. Select a Caching strategy * You can select from many options, but a lot of additional advanced settings can be then set in the FlashEdge console after you create the zone. 5. Select **"Coverage"** 6. Select the **"Firewall"** options. 7. Add your custom domain. This helps you create HTTPS. 8. Review the setup and click on **“Deploy”** ### What can you do next? You can follow the next manuals after your distribution is prepared. 1. Add a CNAME record to your DNS (Domain Name System) to begin routing traffic to your distribution. After you add the alias record, users who visit your domain are routed through your distribution. For more information, see: [Configuring DNS to point to a FlashEdge distribution](/flashedge-cdn-distribution-tutorials/configuring-dns-to-point-to-a-flashedge-cdn-zone). 2. Create an SSL/TLS certificate for your domain to use HTTPS with your distribution. For more information, see [Setting up HTTPS with a Custom Domain](/flashedge-cdn-distribution-tutorials/setting-up-https-with-a-custom-domain). # Configuring DNS to point to a FlashEdge CDN zone One of the first things that you would usually need to do is to point yourdomain.com to your newly created FlashEdge distribution. In this manual, you'll find step-by-step instructions to help you create the first CNAME record in DNS. Whether you're entirely new to the concept or seeking a little bit of help, this guide is your resource. ### General steps A CNAME (Canonical Name) record is used to point one domain to another domain's hostname. This is helpful when you want to associate a FlashEdge CDN domain with a different server or service. For the purpose of this tutorial, let's say you want to set up a CNAME record to point "[www.yourdomain.com](http://www.yourdomain.com)" to "xxxxxxx.flashedgecdn.net". This provided manual is very general and your DNS will probably use other names for some of the things. 1. **Log into your DNS:** Access the account provided by your DNS hosting provider for yourdomain.com, where you manage your domain's DNS settings. 2. **Go to DNS Management:** Navigate to the section related to DNS records. It's often labeled as "DNS Management", "DNS Settings", or something similar. 3. **Add a CNAME Record:** Find the option to add a new DNS record. Choose the record type "CNAME". 4. **Configure the CNAME Record:** Fill in these details: * Name or Host: Enter the subdomain you're creating the alias for. In this case, it's [www.](http://www.) or "www" * Alias, CNAME, or Points to: Input the target domain's hostname, like "xxxxxxx.flashedgecdn.net". 5. **Save the Changes:** After entering the necessary information, save your changes. This action might involve selecting "Save", "Add Record”, or a similar command, depending on your DNS provider's interface. 6. **Wait for DNS Propagation:** Keep in mind that DNS changes may take some time to propagate globally. This process can take anywhere from a few minutes to several hours. During this propagation period, the CNAME record will gradually begin directing traffic to the target domain. It usually helps to test it in an Incognito window of your browser. 7. If you need to direct traffic from more than one domain, please go through the steps from point 3 of this manual again. If you're unsure about any step or encounter difficulties, we recommend reaching out to your DNS provider's support or consulting their documentation for specific instructions tailored to their platform. **You've now successfully established a CNAME record/s in your DNS settings!** ### Creating CNAME records in the most know DNS We are not able to provide exact steps for every provider here are at least links for the most used DNS and how to create CNAME records in them. If you have a problem adding these records, contact your IT administrator or IT support. * [GoDaddy](https://au.godaddy.com/help/add-a-cname-record-19236) * [CloudFlare](https://community.cloudflare.com/t/adding-dns-records/52718) * [Amazon Route 53](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html) * [Google DNS](https://support.google.com/a/answer/47283?hl=en) # Setting up HTTPS with a Custom Domain Using HTTPs with your FlashEdge distribution is easy and free, you just need to create and validate a TLS/SSL certificate for your FlashEdge CDN zone. For this, you need to have access to your custom domain DNS records (example.com). Every certificate automatically validates and adds any subdomain, like [www.example.com](http://www.example.com), api.example.com, or to be precise, \*.example.com, but it also works for lower-level subdomains. {% hint style="info" %} Certificates are provided by Amazon and are issued by the certificate authority recognized by Internet browsers. You can use them securely for any type of website/application that is also accessible via the public Internet. {% endhint %} # Creating an SSL/TLS certificate for FlashEdge distribution When you create a certificate, you **specify the primary (apex) domain name or subdomain** for the certificate, such as example.com or app.example.com. When you create a certificate for domain example.com, you'll **automatically receive a certificate with a wildcard for subdomains (\*.example.com), allowing you to use your FlashEdge CDN zone with any subdomain**. This is also applicable to lower-level domains, so if you create a certificate for app.example.com, you’ll automatically get the certificate for \*.app.example.com. After you update the DNS record of your domain to point to your distribution, your distribution accepts the traffic and serves your content using HTTPS. Complete the following procedure to create an SSL/TLS certificate for your distribution. 1. Sign in to the FlashEdge. 2. Choose the CDN zone for which you want to create a certificate. 3. Choose the Domain tab. 4. Fill in your Custom domain (example.com, or any subdomain) 5. Click on “Add Domain”. Your certificate request is submitted, and the status of your new certificate is changed to PENDING\_VALIDATION. During this time, FlashEdge waits for you to add a validation CNAME record to the DNS of the primary domain. For more information, see Validating FlashEdge domain. # Validating an SSL/TLS certificate for FlashEdge distribution Validation of the SSL/TLS FlashEdge certificate is partly manual and you have 72 hours until it gets to a failed status and you have to create a new certificate. For validation, you have to have administrator access to your DNS (e.g. GoDaddy, Amazon Route 53, etc.) You will first need to [create a FlashEdge certificate](https://docs.flashedgecdn.com/flashedge-tutorials/https-setup-with-custom-domain/creating-tls-ssl-certificate-for-distribution) to be able to validate it and as a result, you should have a certificate that is pending validation. ### CNAME record values for certificate validation After you’ve created a certificate in FlashEdge CDN Zone, you should be able to see the CNAME values that you’ll need for the validation. 1. Sign in to the FlashEdge. 2. Choose the CDN zone for which you want to validate a certificate. 3. Choose the Domain tab. 4. You should see the values that you’ll need for the validation (e.g. \_xxxxxxxxxxxxxxxxxxxxxxxxxxx.example.com. for CNAME and \_xxxxxxxxxxxxxxxxxxxxxxxxxxx.acm-validations.aws. as a value of the CNAME record). 5. Use these values in the next steps in your DNS. ### Creating a CNAME record in your DNS To validate a FlashEdge certificate, you'll need to create a CNAME record in your DNS (Domain Name System). A CNAME (Canonical Name) record is used to alias a domain to another domain. While specific steps may vary depending on your DNS provider, we've prepared a general guide to help you through the process. Alternatively, you can use the links that describe this for the best known DNS services. Here's a step-by-step overview of what you need to do: 1. Log into your DNS: Access your DNS provider's dashboard using your credentials. This is usually where you manage your domain's settings. 2. Locate DNS Management: Look for an option related to "DNS Management", "DNS Settings", or "Domain Configuration". The exact wording might differ, but you're essentially searching for the area where you can edit DNS records. 3. Identify the domain: Choose the domain or subdomain that you want to set up with SSL/TLS and a CNAME record. This is typically done by selecting from a list of domains you own. 4. Add a CNAME record: There should be an option to add a new DNS record. Select "CNAME" as the type of record you want to create. 5. Complete the CNAME record fields: 6. * Name/Alias: Enter the subdomain you want to link:\_xxxxxxxxxxxxxxxxxxxxxxxxxxx.example.com. This will usually only be the specific code before the .example.com. * Value/Points to: Provide the target domain. This will usually be the whole text :\_xxxxxxxxxxxxxxxxxxxxxxxxxxx.acm-validations.aws 7. Save Changes: Once you've filled in the required fields, save the changes. This might involve clicking a "Save" or "Update" button. 8. Propagation Time: Keep in mind that DNS changes might take some time to propagate across the Internet. Changes could be live within minutes or may take up to 48 hours, depending on various factors. Please note that the instructions provided here are general guidelines. Your DNS provider's interface and terminologies might differ. If you're unsure about any step or encounter difficulties, we recommend reaching out to your DNS provider's support or consulting their documentation for specific instructions tailored to their platform. {% hint style="info" %} Links for documentation of most used DNS providers: [GoDaddy](https://au.godaddy.com/help/add-a-cname-record-19236) [Cloudflare](https://community.cloudflare.com/t/adding-dns-records/52718) [Amazon Route 53 (AWS) ](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html) [Google DNS](https://support.google.com/a/answer/47283?hl=en) {% endhint %} ### Check validation status A “SUCCESS” status confirms that you have validated your certificate with the CNAME records that you added to your domains. Your certificate is valid for 12 months from the date on which you validated them, after which time the FlashEdge certificate manager attempts to automatically re-validate them. We recommend that you don't delete the CNAME record because they are required when your certificate is re-validated. {% hint style="info" %} A “FAILED” status can appear after 72 hours. If this happens, try to delete the certificate and start again. If you use the same domain name, the values of the validation CNAME will probably not change. {% endhint %} # Deleting an SSL/TLS certificate for your FlashEdge distribution You can delete the FlashEdge certificate that you're no longer using or if you need to change a domain for your certificate. {% hint style="info" %} Deleting an SSL/TLS certificate is final and can't be undone, but you can create a new certificate with the same domain if needed. {% endhint %} 1. Sign in to the FlashEdge. 2. Choose the CDN Zone for which you want to remove a certificate. 3. Choose the Domain tab. 4. Click on Remove to delete the certificate and wait for a couple of seconds. # Creating a new FlashEdge source server A FlashEdge source server (origin) is a crucial component that your CDN Zone pulls and caches content from, serving as the source for delivering that content to end-users efficiently. The reason why you have the option to add multiple origins to one distribution is that you can, for instance, serve static content (pictures, videos, etc.) from one origin and serve your dynamic content from a different origin behind only one FlashEdge distribution. Follow the steps below to set up your new origin: ### Accessing the origin creation page 1. Log in to your FlashEdge account. 2. Navigate to the FlashEdge CDN Zone for which you want to create a new source server. 3. Click on the “Source Server” tab in the console. ### Initiating the origin creation 1. Look for the option to "Add Source Server" and click on it. 2. You'll be presented with the following fields to fill in or select: ### Origin details 1. **Origin Name (origin-1):** This is a name you'll assign to your origin for easy identification. 2. **Fill Your Domain Name:** Enter the public domain name of your server or service. For example, if you're using a virtual machine in an environment like vm.yourorigin.com or if you are using an AWS S3 bucket or an elastic load balancer, enter the corresponding domain name. 3. **Protocol Policy:** Choose the protocol that FlashEdge should use to connect to your origin. You have three options: * **HTTP Only**: FlashEdge will connect to the origin using HTTP. * **HTTPS Only:** FlashEdge will connect to the origin using HTTPS. * **Match Viewer:** FlashEdge will use the same protocol as the viewer used to access your content (HTTP or HTTPS). 4. In Advanced settings, you can set: 1. **Origin Path (optional):** If your content is stored within a specific path on your origin (e.g., vm.yourorigin.com/assets), you can specify it here. 2. Ports to use for HTTP and HTTPS ### Review and Confirmation 1. Double-check all the information you've entered. 2. Once you're satisfied, click on the "Create New Origin" button. You've successfully set up a new origin for your FlashEdge distribution. Your distribution will now pull and cache content from the specified origin, making your content delivery faster and more efficient. If you are creating more than one origin, make sure that you’ll create a correct FlashEdge cache behavior, so you can forward requests to multiple origins. {% hint style="info" %} ***Feel free to repeat these steps to add more origins or modify existing ones as needed.*** {% endhint %} # Creating a Cache rule Cache rules help you define how FlashEdge handles caching, compression, and caching policies for specific paths or file types. ### Access FlashEdge Cache rules configuration Follow these steps to create or edit cache rules: #### Accessing Cache Behavior Configuration 1. Sign in to the FlashEdge. 2. Choose the CDN Zone for which you want to create a cache rule. 3. Choose the Cache Rules tab. 4. Click on the “Create Rule” or “Edit” button next to the behavior that you want to configure. ### Configure FlashEdge Cache behavior You'll find the following options to configure: 1. **Cache Behavior Details** * Select Origin: Choose the origin (e.g., origin1) to which this cache behavior will apply. * Path or File Type Selection: Specify the path or file types you want to customize caching for. You can use asterisks as wildcards to match directories or file types. For instance: * /path/to/assets/\* for a specific directory. * /\*.html, /\*.jpg, /\*.js for specific file types. Remember, path and file type entries are case-sensitive. 2. **Object Compression:** Choose to enable or disable object compression. Enabling this feature allows your distribution to serve compressed objects to viewers who support them, improving performance. * **Compression enabled:** This function aims to improve the delivery of web content by reducing the amount of data transferred between the origin server and the end user's device. FlashEdge can compress objects using Gzip and Brotli. * **Compression disabled:** This means that the compression is disabled for the selected cache behavior. 3. **Redirect HTTP/HTTPS:** Choose a redirection option to ensure secure connections between viewers and your origin: * **HTTP and HTTPS:** No specific redirection, both protocols are allowed. * **Redirect HTTP to HTTPS:** Redirects all HTTP requests to HTTPS for encryption. * **HTTPS only:** Enforces HTTPS connections only. 4. **Cache Policy:** Select a pre-configured cache behavior that fits your content: * **Cache everything (Best for static content):** Caches and serves your entire website as static content. Ideal for content that remains constant across users or relies less on cookies and headers. * **Cache nothing (Best for dynamic content):** Disables caching entirely; suitable for personalized content using cookies, headers, and query strings. * **\*Custom cache (Advanced cache settings):** Allows tailored cache settings, suitable for advanced users requiring specific caching configurations. 5. Custom Review and Confirmation **Continue below this paragraph if you selected “Custom cache (Advanced cache settings)“.** * Double-check your cache behavior settings. * Once satisfied, click on the "Create/Edit Cache Behavior" button. ### \* Advanced Cache Settings (For "Custom cache" Option) After selecting the "Custom cache (Advanced cache settings)" option, access the advanced cache configuration settings. 1. **Time-to-Live (TTL) Cache Policy:** Specify that the maximum time objects stay in the cache before expiring. Choose TTL duration in days, hours, minutes, or seconds. 2. **Allowed HTTP Methods:** Define which HTTP methods your distribution will process and forward to your origin. * **GET, HEAD:** Only GET and HEAD methods are forwarded. * **GET, HEAD, OPTIONS:** Additionally, the OPTIONS method is forwarded. * **GET, HEAD, OPTIONS, PUT, POST, PATCH, DELETE:** All listed methods are forwarded. 3. **Header Forwarding:** Choose how headers are handled when communicating with your origin: * **Forward Default Headers:** This option is suitable for most cases. It forwards essential headers like "User-Agent" and "Accept-Encoding" that help your origin provide accurate responses based on viewer capabilities. * **Forward All Headers:** You might choose this option to ensure that all headers are forwarded to your origin server. * **Forward Headers I Specify:** For your API, you might select this option and specify headers like "Accept-Language" and "X-Custom-Header". Only these specified headers will be sent to your origin. 4. **Cookie Forwarding:** Choose how cookies are managed when forwarding requests to your origin: * **Don't Forward Cookies:** For example, this might be suitable for static product pages. Such pages don't rely on user-specific cookies for content differentiation. * **Forward All Cookies:** For user personalization and tracking, you would choose this option. It ensures that cookies containing user session details, preferences, or any other content are forwarded to your origin, leading to a seamless shopping experience. * **Forward Cookies I Specify:** Suppose that your application uses cookies named "UserSession" and "CartItems". You'd select this option and specify these cookies. This way, only those specific cookies, critical for your app functionality, are sent to your origin. 5. **Query String Forwarding:** Decide how query strings (?your=query-strings) are managed when interacting with your origin: * **Don't Forward Query Strings:** If your app doesn't rely on query string parameters to function correctly, you can choose this option. * **Forward All Query Strings:** In situations where query strings play a significant role in tailoring content delivery, selecting this option ensures that all query string parameters are forwarded to your origin. * **Forward Query Strings I Specify:** If you want precise control over which query string parameters affect the content delivered from your origin, choose this option. You've successfully configured a cache behavior for your FlashEdge distribution. Repeat these steps to add more cache behaviors or modify existing ones as needed. # Selecting the Coverage (Pricing Regions) for FlashEdge Pricing regions in FlashEdge provide you with the flexibility to choose where your data is served, ensuring optimal performance and cost efficiency for your content delivery needs. By selecting the most suitable pricing region, you can align your content delivery strategy with your target audience's geographic locations. This guide offers a straightforward overview and step-by-step instructions on setting up coverage within the FlashEdge console. {% hint style="info" %} In Free-Trial you are only able to use North America and Europe regions {% endhint %} 1. Sign in to FlashEdge. 2. Choose the CDN Zone for which you want to change the coverage. 3. Choose the Coverage tab. 4. Select your Coverage: * **Europe & North America:** If you want to achieve the best performance and global coverage. This might come with a specific cost per gigabyte, but we still count the costs based on the region of the users. * **Global Expansion:** If your audience is primarily based in North America and Europe, select the "Use only North America and Europe" option. This option has the lowest cost per gigabyte, but users from different regions can get a bigger latency. # Monitoring CDN zone metrics in FlashEdge After you create a distribution in FlashEdge, you can monitor its usage via metrics in the console. ### Distribution monitoring metrics in FlashEdge The following distribution metrics are available: #### Requests This metric quantifies the total number of viewer requests received by your distribution. It includes all HTTP methods and both HTTP and HTTPS requests. #### Bytes uploaded and downloaded * **Bytes uploaded:** This metric measures the quantity of bytes uploaded to your origin by your distribution through POST and PUT requests. * **Bytes downloaded:** This metric indicates the volume of bytes downloaded by viewers in response to GET, HEAD, and OPTIONS requests. #### Error rate * **Total error rate:** This metric denotes the percentage of all viewer requests for which the response's HTTP status code was 4xx or 5xx. * **HTTP 4xx error rate:** This metric represents the percentage of all viewer requests for which the response's HTTP status code was 4xx. In these scenarios, errors might have occurred due to client or viewer mistakes. For instance, a status code of 404 (Not Found) signifies that the client requested an object that could not be found. * **HTTP 5xx error rate:** This metric signifies the percentage of all viewer requests for which the response's HTTP status code was 5xx. These instances indicate that the origin server failed to fulfill the request. For example, a status code of 503 (Service Unavailable) implies that the origin server is currently inaccessible. ### Viewing FlashEdge distribution metrics Complete the following procedure to view distribution metrics in the Lightsail console. 1. Sign in to the FlashEdge. 2. Choose the distribution for which you want to find metrics. 3. Choose the Monitoring tab. 4. Examine the included graphs and utilize the metrics graph to execute these actions: * Adjust the graph's display to reveal information for 1 hour, 6 hours, 1 day, 1 week, and 2 weeks. * Hover your cursor over a data point to access in-depth details about that specific data point. # Suspending a FlashEdge CDN zone {% hint style="warning" %} Disabling/Enabling a distribution in FlashEdge is a fundamental step that allows you to temporarily deactivate a distribution configuration without permanently deleting it. {% endhint %} This action is especially useful when you need to suspend the zone's functionality, whether it's due to maintenance, updates, or other reasons. By disabling a CDN zone, you prevent it from actively delivering content, ensuring that users don't receive content from that particular zone during the disabled period. After disabling, you should not incur any costs for this zone. ### Disabling The following guide outlines the straightforward process of disabling a FlashEdge distribution: 1. Sign in to FlashEdge. 2. Choose the zone that you want to delete. 3. Choose the Settings tab. 4. Click on the “Suspend” button. 5. Wait until the zone is disabled. ### Resuming The following guide outlines the straightforward process of enabling a FlashEdge zone: 1. Sign in to FlashEdge. 2. Choose the distribution that you want to resume the functionality of the FlashEdge CDN zone. 3. Choose the Settings tab. 4. Click on the “Resume” button. 5. Wait until the zone is resumed. # Deleting a FlashEdge CDN zone {% hint style="danger" %} Warning: Deleting a distribution is an irreversible process! {% endhint %} Deleting a zone in FlashEdge is a significant action that allows you to permanently remove a zone setup. This process removes all associated configurations and settings. Whether you're restructuring your content delivery strategy or no longer require a specific CDN zone, by following these steps, you can efficiently manage your content delivery network and ensure that your resources are allocated optimally. {% hint style="warning" %} Update your DNS records or application before deleting your distribution to avoid traffic interruption to your origin. {% endhint %} 1. Sign in to the FlashEdge. 2. Choose the distribution that you want to delete. 3. Choose the Settings tab. 4. Click on the “Delete Permanently” button. If the button is greyed out, you will first need to disable the distribution. 5. Confirm the deletion. 6. Wait until the zone disappears from the zone list and home. # FlashEdge Storage tutorials # Getting started with FlashEdge Storage After creating a FlashEdge account, you can simply start the process of creating FlashEdge Storage. ## Creating the first FlashEdge Storage Complete the following steps to create FlashEdge Storage: 1. Sign in to the FlashEdge Console. 2. Click on an arrow before “Deploy Resources” on the home page, or click “Add FlashEdge Storage”. 3. Fill in the Bucket Name. 4. Specify the desired region for optimal latency and availability. 5. Click on "Continue". 6. Either select "Manual connection later" or, if you already have a CDN zone where you want to connect. 7. Review and click on “Create Storage”. When you select "Manual connection later" FlashEdge Storage isn't automatically connected to a FlashEdge CDN zone. You have to create FlashEdge CDN distribution. {% content-ref url="/pages/1eBJV81uHLy41nei6BHl" %} [Creating FlashEdge CDN zones for FlashEdge Storage](/flashedge-storage-tutorials/creating-flashedge-cdn-zones-for-flashedge-storage) {% endcontent-ref %} # Creating FlashEdge CDN zones for FlashEdge Storage Every FlashEdge Storage needs to have a FlashEdge CDN to publicly access the files, applications, website, or anything else you store in the Storage. Complete the following procedure to create a distribution. 1. Sign in to the [FlashEdge](https://www.flashedgecdn.com/login). 2. Click on “Deploy resource” on the home page. 3. Choose your source server. 1. Fill in the name of your source server. 2. Select the FlashEdge Storage as the source server. 4. Select a caching behavior. 1. For FlashEdge Storage, we recommend using the possibility to Cache Everything. 5. Click on “Create a Distribution”. 6. After creation, it may take some time (usually up to 15 minutes) for the distribution to deploy globally. 7. After the FlashEdge distribution is created for your FlashEdge Storage, you should be able to access files that are stored there by simply checking the corresponding path through the FlashEdge CDN distribution URL, for example, xxxxxxx.flashedge.net/images/pic1.png. # Securing FlashEdge Storage access through FlashEdge CDN with HTTPS It’s possible to serve content from FlashEdge Storage securely through HTTPS with your custom domain. If you want to connect your own domain to FlashEdge CDN and FlashEdge Storage and secure it with HTTPS, follow [these instructions](/flashedge-cdn-distribution-tutorials/setting-up-https-with-a-custom-domain/creating-an-ssl-tls-certificate-for-flashedge-distribution), which describe the whole process. # FlashEdge Storage access ### Creating an access key This guide provides step-by-step instructions for creating remote access keys for FlashEdge Storage. All of your FlashEdge Storages share this access key.\ \ Access keys are essential for securely managing and accessing your stored data. Follow the steps below to quickly generate a new access key through the FlashEdge Console. 1. Sign in to the FlashEdge Console. 2. Click on “Account” in the upper menu. 3. Select “API Keys” from the upper menu. 4. Click on “Generate key”. 5. The access key should be created after a couple of seconds. ### Granting access to FlashEdge Storage to the access key After you create an access key in the settings, you can use it for the FlashEdge Storage that you have created. 1. Sign in to the FlashEdge Console. 2. Select the FlashEdge Storage that you want to grant access key to. 3. Select the tab “Remote access”. 4. Click on “Grant access.” 5. After a couple of seconds, you should see the resulting connection settings. ### Using FlashEdge Storage access key This guide provides step-by-step instructions for uploading and browsing files in FlashEdge Storage using the AWS Command Line Interface (CLI) and other options. It is designed for users on Windows, macOS, and Linux. Follow these instructions to easily manage your content and take full advantage of FlashEdge Storage capabilities. #### **Using AWS (Amazon Web Services) CLI** You can use AWS CLI to connect to FlashEdge Storage. You can also use all its functions. This manual describes only a couple of major functions that you can use. **Step 1: Install the AWS CLI** You can find the latest manuals in the official AWS documentation. 1. Windows:\ Download and run the installer from [AWS CLI for Windows](https://aws.amazon.com/cli/).\ After installation, restart your terminal or command prompt. 2. macOS: `“brew install awscli”` 3. Linux: `“sudo apt update”` `“sudo apt install awscli”` **Step 2: Configure AWS CLI with Access Keys** Run the following command to configure AWS CLI with your access key and secret key: `“aws configure”` Now you will need the information from the FlashEdge Console. You will be prompted to enter: `AWS Access Key ID: Enter your FlashEdge Storage access key.` `AWS Secret Access Key: Enter your FlashEdge Storage secret key.` `Default region name: (e.g., us-east-1).` `Default output format: Leave it on default.` **Step 3: Upload Files to FlashEdge Storage** Use the following command to upload a file: `“aws s3 cp /path/to/your/file.txt s3://your-bucket-name/”` Replace: `/path/to/your/file.txt with the actual path to your file.` `your-bucket-name with the name of your S3 bucket.` **Step 4: Upload a Directory to FlashEdge Storage** To upload all files from a directory, use: `“aws s3 cp /path/to/your/folder s3://your-bucket-name/ --recursive”` **Step 5: Listing files in FlashEdge Storage** Use the following command to list all objects in a specific bucket: `“aws s3 ls s3://your-bucket-name”` To include subfolders and detailed information, add the --recursive and --human-readable flags: `“aws s3 ls s3://your-bucket-name --recursive --human-readable”` To list files with a specific prefix (e.g., all files in a folder or with a particular file name pattern), replace folder-name with the path to the folder or prefix.: `“aws s3 ls s3://your-bucket-name/folder-name/"` *** #### Using Cyberduck to connect to the FlashEdge Storage Cyberduck is a popular open-source client that connects to various cloud storage services. Follow the steps below to configure Cyberduck on macOS or Windows to connect to your FlashEdge Storage. **Prerequisites** ● Cyberduck is installed on your machine.\ Download the latest version from the official website: ● FlashEdge Storage access key and secret key, and the bucket name of your FlashEdge Storage. **Steps for macOS and Windows** 1. Open Cyberduck\ Launch Cyberduck on your macOS or Windows machine. 2. Add a New Connection 3. Click on the “Open Connection” button in the toolbar. 4. Select Amazon S3 as the Connection Type 5. From the drop-down menu at the top, choose “Amazon S3”. 6. Enter Connection Details 7. Server: Enter s3.amazonaws.com. 8. Access Key ID: Enter your FlashEdge Storage Access Key ID. 9. Secret Access Key: Enter your FlashEdge Storage Secret Access Key. 10. Click the “More Options” or “Advanced options” and specify a path (bucket name from the FlashEdge Storage Console). 11. Save and Connect 12. Click “Connect” to access your FlashEdge Storage. 13. To save the connection for future use, click the “Bookmark” button before connecting. # Deleting FlashEdge Storage If you decide that you don’t need any of your FlashEdge Storage, you can delete it from your account. If you have created FlashEdge CDN distribution for this Storage, don’t forget to delete it as well or change the origin. {% hint style="warning" %} Deleting the FlashEdge Storage is final and can't be undone. It will also delete all stored files without the possibility of restoring them. {% endhint %} Follow the next instructions: 1. You need to first delete all files from your storage. 2. Sign in to FlashEdge. 3. Choose the Storage that you want to delete. 4. Choose the Advanced tab. 5. Click on “Delete” to remove. 6. Type the name of the Storage and click on “Delete.” # FlashEdge WAF (Web Application Firewall) tutorials The FlashEdge Web Application Firewall is built into the FlashEdge CDN and helps protect your content and applications against common web threats, including Layer 7 (application layer) DDoS attacks, unwanted IP access, and traffic from undesired countries. This feature is available under the **Firewall** tab for each distribution separately within the FlashEdge CDN console. *** ### Enabling Recommended Protection Enable a curated set of Layer 7 protection rules designed to block the most common threats to web applications. This includes: · Mitigate common web application vulnerabilities · Prevent malicious actors from probing for weaknesses · Block IP addresses associated with suspicious or harmful activity Use this option to quickly apply a set of curated rules designed to block common web threats. **How to enable:** 1\. Go to your **distribution** in the FlashEdge CDN console. 2\. Open the **Firewall** tab. 3\. Check the **Enable Recommended Protection** option. *** ### Configuring Country Protection Restrict or allow access to your distribution based on the origin country of incoming requests. * Allow mode: Only selected countries will be allowed; all others will be blocked * Block mode: Selected countries will be blocked; all others will be allowed To configure, check Enable country protection and define the country list and mode. **How to configure:** 1\. Go to your **distribution** in the FlashEdge CDN console. 2\. Open the **Firewall** tab. 3\. Check the **Enable Country Protection** option. 4\. Select your **mode** (Allow or Block). 5\. Add the countries you want to allow or block. *** ### Configuring IP Address Protection Manage access based on IP addresses. You can explicitly allow or block specific IPs or ranges. * Allow mode: Only listed IP addresses are permitted * Block mode: Listed IP addresses are denied access To configure, check Enable IP address protection and add your rules accordingly. **How to configure:** 1\. Go to your **distribution** in the FlashEdge CDN console. 2\. Open the **Firewall** tab. 3\. Check the **Enable IP Address Protection** option. 4\. Select your **mode** (Allow or Block). 5\. Add the individual IPs or ranges as needed. *** ### Advanced description of the FlashEdge WAF recommended protection #### Mitigate common web application vulnerabilities This part of our FlashEdge recommended protection includes general-purpose protection for web applications from a wide range of common vulnerabilities, including many listed in the [OWASP Top 10](https://owasp.org/www-project-top-ten/). It's a good starting point for most use cases. | Name | Description | | ------------------------------------ | ------------------------------------------------------------------------------------------------ | | No User Agent HEADER | Checks for requests missing the User-Agent HTTP header. | | User Agent Bad Bots HEADER | Detects bad bots using known User-Agent patterns like nessus or nmap. | | Size Restrictions QUERYSTRING | Flags query strings longer than 2,048 bytes. | | Size Restrictions Cookie HEADER | Flags cookie headers exceeding 10,240 bytes. | | Size Restrictions BODY | Flags request bodies over 8 KB (8,192 bytes). | | Size Restrictions URIPATH | Flags URI paths longer than 1,024 bytes. | | EC2 MetaData SSRF BODY | Detects EC2 metadata access attempts in the request body. | | EC2 MetaData SSRF COOKIE | Detects EC2 metadata access attempts in cookies. | | EC2 MetaData SSRF URIPATH | Detects EC2 metadata access attempts in the URI path. | | EC2 MetaData SSRF QUERYARGUMENTS | Detects EC2 metadata access attempts in query parameters. | | GenericLFI QUERYARGUMENTS | Detects Local File Inclusion (LFI) patterns in query parameters, such as ../../. | | GenericLFI URIPATH | Detects LFI attempts in the URI path. | | GenericLFI BODY | Detects LFI patterns in the request body. | | Restricted Extensions URIPATH | Flags URI paths with unsafe file extensions like .log or .ini. | | Restricted Extensions QUERYARGUMENTS | Flags query arguments with risky file extensions. | | Generic RFI QUERYARGUMENTS | Detects Remote File Inclusion (RFI) attempts using URLs with IPv4 addresses in query parameters. | | Generic RFI BODY | Detects RFI patterns in the request body using embedded URLs with IPv4 hosts. | | Generic RFI URIPATH | Detects RFI attempts in the URI path using URL-based payloads. | | CrossSiteScripting COOKIE | Detects cross-site scripting (XSS) patterns in cookie values. | | CrossSiteScripting QUERYARGUMENTS | Detects common XSS patterns in query arguments. | | CrossSiteScripting BODY | Detects XSS patterns in the request body, such as \. | | CrossSiteScripting URIPATH | Detects XSS patterns in the URI path. | #### Prevent malicious actors from probing for weaknesses This includes blocking of suspicious request patterns often used to find or exploit vulnerabilities. This helps reduce the risk of attacks on your application. | Name | Description and Label | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Java Deserialization RCE | Checks request headers for patterns related to Java deserialization RCE attempts, such as known Spring vulnerabilities. Example: (java.lang.Runtime).getRuntime().exec("whoami"). Inspects up to 8 KB or 200 headers. | | Java Deserialization RCE BODY | Checks the request body for Java deserialization RCE attempts, including Spring Core and Cloud Function vulnerabilities. Inspects up to the configured body size limit. | | Java Deserialization RCE URIPATH | Scans the URI path for signs of Java deserialization RCE attempts. | | Java Deserialization RCE QUERYSTRING | Scans the query string for Java deserialization RCE exploit patterns. | | Host localhost HEADER | Detects use of localhost in the request host header. | | PROPFIND METHOD | Flags requests using the PROPFIND HTTP method, often used to probe or exfiltrate XML data. | | Exploitable Paths URIPATH | Detects access attempts to risky application paths like web-inf. | | Log4J RCE HEADER | Inspects headers for Log4j RCE attempts (${jndi:ldap\://...}) linked to known CVEs. | | Log4J RCE QUERYSTRING | Scans the query string for Log4j RCE exploit patterns. | | Log4J RCE BODY | Scans the request body for Log4j vulnerability attempts. | | Log4J RCE URIPATH | Scans the URI path for Log4j RCE patterns like ${jndi:...}. | #### Block IP addresses associated with suspicious or harmful activity Checks for IP addresses known to be involved in malicious activity. The list is built using multiple threat intelligence sources, including Amazon’s MadPot system. [Learn more about MadPot](https://www.aboutamazon.com/news/aws/amazon-madpot-stops-cybersecurity-crime). # FlashEdge Pricing ## FlashEdge pricing overview FlashEdge charges are based on actual usage of the service in four areas: Data Transfer Out to the Internet from FlashEdge, HTTP/HTTPS Requests, Invalidation Requests, and Data Transfer Out to Origin associated with a FlashEdge distribution. For every new account, we offer a 14-day trial which is described below. {% content-ref url="/pages/WmcepyYC1JSijJlQGhcr" %} [FlashEdge CDN pricing](/flashedge-pricing/flashedge-cdn-pricing) {% endcontent-ref %} ## FlashEdge billing ### Billing information Your FlashEdge billing information can be found and changed in the FlashEdge billing console. ### Analytics of current spending FlashEdge offers a couple of places in the console where you can check your current spending on every distribution separately or for the sum of the distribution. This information is updated once a day. ### Billing period Shortly after each week, an invoice is generated automatically by Stripe. We will automatically send you an email containing the invoice. You can also download your invoices at any time in the account billing. *** ## FAQ ### Does FlashEdge price include taxes? Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. ### Which payment methods do you support? We use Stripe as our payment method. This means you can conveniently make payments using a variety of options through Stripe, including credit and debit cards. With Stripe, your payment experience is secure, seamless, and tailored to your needs. ***
# FlashEdge CDN pricing ### FlashEdge CDN free-trial With the FlashEdge free trial, you can get started for free. Per account, all FlashEdge users receive: * 14-day trial * 100 GB data transfer out from FlashEdge to the Internet, upgradeable up to 500 GB by contacting support. * 20,000,000 HTTP and HTTPS Requests free of charge. * 1,000 invalidation requests (FlashEdge cache reset/cleaning). * 1 GB inbound data transfer (inbound from FlashEdge to your origin). * Ability to create three FlashEdge distributions. We automatically check for your current usage of the FlashEdge free trial and you’ll get notified when you are close to reaching the limits. ### FlashEdge CDN list pricing * $0.03 per GB for North America/Europe and $0.06 for the rest of the regions (Data Transfer Out from FlashEdge to the internet). Usually provided by the GET, HEAD, and OPTIONS HTTP methods. * $0.0065 per 10.000 requests (HTTP and HTTPS). * $0.02 per GB for FlashEdge to your origin server (Data Transfer Out to Origin or Inbound Data Transfer). Provided usually by the POST HTTP method. * $0.005 per invalidation (cache invalidation request). ***We provide special pricing and a free trial to those who utilize more than 100 TB of data transfer from FlashEdge to the Internet. Contact us for an*** [***individual free trial***](https://www.flashedgecdn.com/individual-trial)***.*** ### Detailed description of FlashEdge CDN pricing * **Data Transfer Out to the Internet:** you are charged for the volume of data transferred out from FlashEdge locations, measured in GB. Note that your data transfer usage is totaled separately for specific geographic regions. * **Data Transfer Out to Origin (inbound data transfer):** you will be charged for the volume of data transferred out, measured in GB, from the FlashEdge locations to your origin (both AWS origins and other origin servers). * **HTTP/HTTPS Requests:** you will be charged for the number of HTTP/HTTPS requests made to FlashEdge for your content. For each 60 KB of FlashEdge Data Transfer Out, you will receive one free HTTP or HTTPS GET Request. For additional HTTP or HTTPS GET Requests, the rate is $0.0065 per 10,000 of such requests. * **Invalidation Requests:** you are charged per your invalidation request in the console. You can request up to 1,000 invalidations each month from FlashEdge at no additional charge. Beyond the first 1,000 paths, you will be charged. ### Costs connected to FlashEdge CDN usage When you start using FlashEdge CDN you can get one benefit that many other CDN services can’t bring you. If you use AWS (Amazon Web Services) origins (such as Amazon S3, Amazon EC2, AWS Elastic Load Balancer, and so on), you will not be charged for AWS data transfer out from AWS to FlashEdge. This applies to data transfer from all AWS Regions to all FlashEdge locations. This would normally appear on your AWS for around $0.09 per GB, but with FlashEdge this will be free of charge because FlashEdge is directly connected to AWS regions. If you are using your on-premises servers or service from a provider other than AWS, you will be charged separately based on the pricing of this service, so this won’t show up in your FlashEdge bill. # FlashEdge Storage pricing #### FlashEdge Storage list pricing * Storage costs $0.03 per GB for all regions. * $0.0065 per 1000 tier-1 requests ( PUT, COPY, POST, LIST Requests). * $0.0005 per 1000 tier-2 requests (GET Requests) * Data transfer out to FlashEdge CDN is free of charge and any data flowing to the public internet will be charged based on FlashEdge CDN pricing. * Data transfer out directly from FlashEdge Storage (this only happens when you download something directly from FlashEdge Storage through the file explorer): $0.09 per GB for US/EU regions (Data Transfer Out from FlashEdge to the Internet). Usually provided by the GET, HEAD, and OPTIONS HTTP methods. * File uploading (Data transfer IN) to FlashEdge Storage is free of charge. # FlashEdge Firewall pricing The FlashEdge Web Application Firewall is built into the FlashEdge CDN and helps protect your content and applications against common web threats, including Layer 7 (application layer) DDoS attacks, unwanted IP access, and traffic from undesired countries.\ \ The FlashEdge Firewall is available as an optional paid add-on separately for every distribution.\ \ All Firewall features are included in a single package, so enabling **Recommended Protection**, **Country Protection**, or **IP Address Protection** does not affect the price — it remains the same.
* **Price**: $12/month/30-days * **Billing model**: Usage-based, calculated weekly based on a daily usage. * **Daily cost**: $0.40 (charged only for days when the Firewall is active) ### How It Works You are only billed for the days during which the Firewall is enabled in your FlashEdge configuration. For example: * If you enable the Firewall for one FlashEdge distribution for 1 day in a given month, you'll be charged **$0.40**. * If you keep it enabled for the full month, the cost will be \~**$12.00**. * If you enable the Firewall for two distributions, you pay **$0.40 per day per distribution** — totaling **$0.80 per day**. The cost scales linearly with the number of distributions. This flexible model ensures you only pay for the protection you actually use. # FlashEdge Network ### FlashEdge CDN Network FlashEdge CDN is designed to deliver content swiftly and securely through a robust global network. With over 600+ strategically positioned Points of Presence (PoPs) worldwide, FlashEdge ensures that user requests are served from the nearest location, minimizing latency and enhancing performance. **FlashEdge CDN employs a multi-layered PoP caching strategy to ensure rapid and efficient content delivery across the globe.** The integration of a regional PoP, which serves as a pivotal hub within our caching hierarchy. This regional PoP collaborates with numerous smaller edge PoPs, creating a tiered caching system. When an edge PoP encounters a cache miss, it first tries to retrieve the requested content from the regional PoP instead of the origin server, significantly reducing the load on the origin and accelerating content delivery. {% hint style="info" %} This distributed architecture not only **accelerates content delivery but also offers high availability and fault tolerance by maintaining multiple copies of content across the network**. {% endhint %} {% content-ref url="/pages/pAmlIXjtbeRyRbgZt0jS" %} [List of FlashEdge CDN PoPs](/flashedge-network/list-of-flashedge-cdn-pops) {% endcontent-ref %} # List of FlashEdge CDN PoPs FlashEdge CDN network includes a large regional PoP for centralized caching and multiple smaller PoPs to ensure low-latency delivery closer to end users. Below is the list of our PoP locations. ### PoPs in Europe #### Normal PoPs Amsterdam *Netherlands* Athens *Greece* Barcelona *Spain* Berlin *Germany* Brussels *Belgium* Budapest *Hungary* Bucharest *Romania* Copenhagen *Denmark* Dublin *Ireland* Dusseldorf *Germany* Frankfurt *Germany* Hamburg *Germany* Helsinki *Finland* Lisbon *Portugal* London *Great Britain* Madrid *Spain* Manchester *Great Britain* Marseille *France* Milan *Italy* Munich *Germany* Oslo *Norway* Palermo *Italy* Paris *France* Prague *Czech Republic* Rome *Italy* Sofia *Bulgaria* Stockholm *Sweden* Vienna *Austria* Warsaw *Poland* Zagreb *Croatia* Zurich *Switzerland*
#### Small POPs Aurich *Germany* Birmingham *Great Britain* Bremen *Germany* Bremerhaven *Germany* Brentford *Great Britain* Bristol *Great Britain* Cardiff *Great Britain* Cloppenburg *Germany* Corsham *Great Britain* Edinburgh *Great Britain* Emden *Germany* Georgsmarienhuette *Germany* Glasgow *Great Britain* Gloucester *Great Britain* Hampshire *Great Britain* Hayes *Great Britain* Kent *Great Britain* Keynes *Great Britain* Leeds *Great Britain* Leer *Germany* Liverpool *Great Britain* London *Great Britain* Manchester *Great Britain* Middlesex *Great Britain* Milton Keynes *Great Britain* Newcastle *Great Britain* Nottingham *Great Britain* Oldenburg *Germany* Osnabrück *Germany* Papenburg *Germany* Sheffield *Great Britain* Stoke *Great Britain* Zeven *Germany*
#### Regional PoPs Dublin *Ireland* Frankfurt *Germany* London *UK* *** ### PoPs in North America #### Small POPs Abilene *United States* Alamogordo *United States* Amarillo *United States* Anchorage *United States* Ardmore *United States* Arvada *United States* Ashburn *United States* Atlanta *United States* Austin *United States* Bay City *United States* Beckley *United States* Beltsville *United States* Bend *United States* Biloxi *United States* Birmingham *United States* Bismarck *United States* Boerne *United States* Boise *United States* Bossier *United States* Boston *United States* Broken Arrow *United States* Bryan *United States* Butler *United States* Calgary *Canada* Canyon Lake *United States* Cincinnati *United States* Cleveland *United States* Commerce *United States* Contoocook *United States* Corpus Christi *United States* Dallas *United States* Denver *United States* Detroit *United States* Durham *United States* Edmonton *Canada* Elgin *United States* Englewood *United States* Eureka *United States* Evansville *United States* Fargo *United States* Fitzgerald *United States* Flagstaff *United States* Georgetown *United States* Grinnell *United States* Hawthorne *United States* Henrico *United States* Hicksville *United States* Hobbs *United States* Honolulu *United States* Hudson *United States* Charleston *United States* Charlotte *United States* Chicago *United States* Irvine *United States* Jacksonville *United States* Jonesboro *United States* Joplin *United States* Kansas City *United States* Kingwood *United States* Lake Havasu *United States* Lake Charles *United States* Las Vegas *United States* Lawrence *United States* Lexington *United States* Lincoln *United States* Lisle *United States* Little Rock *United States* Live Oak *United States* Louisville *United States* Lubbock *United States* Madison *United States* Memphis *United States* Miami *United States* Minneapolis *United States* Monroe *United States* Monterrey *Mexico* Mooresville *United States* Mt. Juliet *United States* Nashville *United States* Natchitoches *United States* New Orleans *United States* Norcross *United States* Norfolk *United States* North Lima *United States* Odessa *United States* Oklahoma City *United States* Omaha *United States* Orlando *United States* Oxford *United States* Palmerton *United States* Parkersburg *United States* Parsippany *United States* Phoenix *United States* Pittsburgh *United States* Pontotoc *United States* Prescott *United States* Puebla *Mexico* Regina *Canada* Richmond *United States* Rocky Mt *United States* Russellville *United States* Sacramento *United States* Salt Lake City *United States* San Angelo *United States* San Antonio *United States* San Diego *United States* San Francisco *United States* San Marcos *United States* Santa Clara *United States* Saskatoon *Canada* Seattle *United States* Sioux City *United States* Sioux Falls *United States* South Bend *United States* Southfield *United States* St George *United States* St Louis *United States* Starkville *United States* Tlalnepantla *Mexico* Tlaquepaque *Mexico* Toledo *United States* Torreón *Mexico* Truckee *United States* Vincennes *United States* Waco *United States* Waipahu *United States* Washington *United States* Watertown *United States* White Plains *United States* Wilkes Barre *United States* Winnipeg *Canada* Zelienople *United States* #### Normal PoPs Atlanta *United States* Boston *United States* Colombus *United States* Dallas *United States* Denver *United States* Detroit *United States* Houston *United States* Chicago *United States* Kansas City *United States* Los Angeles *United States* Miami *United States* Minneapolis *United States* Montreal *Canada* Nashville *United States* New York City *United States* Newark *United States* Philadelphia *United States* Phoenix *United States* Pittsburgh *United States* Portland *United States* Queretaro *Mexico* Salt Lake City *United States* San Francisco *United States* Seattle *United States* Tampa *United States* Toronto *Canada* Vancouver *Canada* Washington D.C. *United States* #### Regional PoPs California *USA* Northern Virginia *USA* Ohio *USA* Oregon *USA* *** ### PoPs in South America #### Normal PoPs Bogota *Colombia* Buenos Aires *Argentina* Fortaleza *Brazil* Lima *Peru* Rio de Janeiro *Brazil* Santiago *Chile* Sao Paulo *Brazil* #### Regional PoPs Sao Paulo *Brazil* *** ### PoPs in Middle East #### Normal PoPs Dubai *United Arab Emirates* Fujairah *United Arab Emirates* Istanbul *Turkey* Jeddah *Kingdom of Saudi Arabia* Manama *Bahrain* Muscat *Oman* Qatar *Qatar* Tel Aviv *Israel* PoPs in Africa Normal PoPs Cairo *Egypt* Cape Town *South Africa* Johannesburg *South Africa* Lagos *Nigeria* Nairobi *Kenya* ### PoPs in Asia Pacific Small POPs Ahmedabad *India* Ambala *India* Asansol MCN *India* Baroda *India* Bengaluru *India* Bhubaneshwar *India* Coimbatore *India* Delhi *India* Dombivli *India* Ernakulam *India* Guwahati *India* Haryana *India* Hosur *India* Hyderabad *India* Chennai *India* Jaipur *India* Kannur *India* Kanpur *India* Kirlampudi *India* Kolkata *India* Kozhikode *India* Lucknow *India* Ludhiana *India* Mangalore *India* Meerut *India* Mumbai *India* Nagpur *India* Nellore *India* New Delhi *India* Palghar *India* Pune *India* Rajahmundry *India* Rajkot *India* Ranchi *India* Shillong *India* Shimla *India* Srinagar *India* Surat *India* Thane *India* Thiruvananthapuram *India* Thrissur *India* Vijayawada *India* Warangal *India* #### Normal PoPs Bangkok *Thailand* Beijing *China* Bengaluru *India* Delhi *India* Hanoi *Vietnam* Ho Chi Minh City *Vietnam* Hong Kong *China* Hyderabad *India* Chennai *India* Jakarta *Indonesia* Kolkata *India* Kuala Lumpur *Malaysia* Manlia *Philippines* Mumbai *India* Osaka *Japan* Pune *India* Seoul *South Korea* Shanghai *China* Shenzhen *China* Singapore *Singapore* Taoyuan *Taiwan* Tokyo *Japan* Zhongwei *China* #### Regional PoPs Mumbai *India* Seoul *South Korea* Singapore *Singapore* Tokyo *Japan* *** ### PoPs in Australia and New Zealand #### Normal PoPs Auckland *New Zealand* Brisbane *Australia* Melbourne *Australia* Perth *Australia* Sydney *Australia* #### Regional PoPs Sydney *Australia* PoPs in EuropePoPs in EuropePoPs in Europe # FAQ {% content-ref url="/pages/Itd3j3FHdHQJoRZh2teY" %} [FlashEdge CDN FAQ](/faq/flashedge-cdn-faq) {% endcontent-ref %} {% content-ref url="/pages/2CVt8pABlUDdU9GoyEhP" %} [FlashEdge Storage FAQ](/faq/flashedge-storage-faq) {% endcontent-ref %} # FlashEdge CDN FAQ ### What can I do with FlashEdge CDN? * FlashEdge content delivery network (CDN) distributions make it easy for you to accelerate the delivery of content hosted on your resources by storing and serving it on a global delivery network. * FlashEdge distributions also help you enable your website to support HTTPS traffic by providing simple SSL certificate creation and hosting. * FlashEdge can help reduce the load on your resources and help your website handle large traffic spikes., and you pay as you go with a 14-day trial. * Easy setup can be completed with just a few clicks and begin without the need for contract negotiations or minimum commitments. ### **How does FlashEdge CDN enhance performance?** FlashEdge uses a network of edge locations and regional caches to store copies of your content. This means that when people ask for your content, FlashEdge responds from a spot close to them. This speeds things up because the requests don't have to travel far. For files that aren’t stored nearby, FlashEdge stays connected to your origin, so it can grab those files quickly. ### **What sorts of content does FlashEdge CDN support?** FlashEdge is designed to work with content that can be delivered through the HTTP or WebSocket protocols. This covers: * Dynamic web pages and applications like HTML, PHP, and JavaScript pages, along with WebSocket-powered applications. * Common static files used in web apps, such as images, audio, video, media files, and software downloads. * Additionally, FlashEdge supports the distribution of live or on-demand media streaming using HTTP. ### **How does FlashEdge help me cut down costs for distributing content online** In comparison to self-hosting, FlashEdge saves you from the expenses and complications of running cache servers across various Internet locations. It also removes the necessity to have extra capacity to handle sudden spikes in traffic. FlashEdge also employs methods such as combining similar viewer requests for a file at a specific spot into a single request to your main server. This eases the load on your main servers, lessening the need to expand your infrastructure, ultimately leading to more cost savings. ### Can I attach multiple origins? Yes, you can attach multiple origins, simply by creating them in the FlashEdge console. Just don’t forget to also create the correct cache behavior, so your traffic is divided correctly. ### Can I select what will be cached and what will be always forwarded to the origin? Yes, you can specify this via caching behaviors. You can, for example, select to only cache specific file types or paths from your origin. ### Do FlashEdge CDN distributions support SSL/TLS certificate creation? Yes. FlashEdge distributions make it easy to create, verify, and attach certificates directly from your distribution’s management page. ### How can I configure my distribution to redirect HTTP requests to HTTPS? FlashEdge distribution can automatically redirect all HTTP requests to HTTPS to ensure that your content is served securely. ### How can I configure my apex domain(example.com) to point to my FlashEdge distribution? At the moment this is not possible for usual DNS providers. You can contact us and we’ll try to solve this on demand. ### How do I know if my FlashEdge CDN distribution is working? Look for a status on Home in the console: you should see “Enabled” or “In progress”. If the status is “Disabled” check the Advanced tab in the distribution settings and Enable your distribution. You can try to hit the domain name given to you in the console (e.g. xxxxxx.flashedge.net). If there are any issues, try checking if your origin is publicly accessible. ### Can I delete cached content? Yes, you can delete all cached content by using the Invalidate Cache option on the Advanced tab in distribution settings. ### Does FlashEdge CDN automatically check if the files in the cache are up-to-date? No, FlashEdge is unable to check if the files in its cache are up-to-date and haven’t been changed. If you need to update the caches, you’ll need to invalidate the cache in the advanced settings of the distribution. ### Does FlashEdge CDN support preloading content into the caches? No. FlashEdge works based on the requests of your users. Usually, when there is a first request from the user, the second user will get the same file from the caches, but this also depends on geography. There are more than 200+ edge locations, but behind them, there are regional caches that can help with Cache hits significantly. # FlashEdge Storage FAQ ### What is FlashEdge Storage? FlashEdge Storage is a scalable and high-performance storage service that seamlessly integrates with FlashEdge CDN, providing reliable solutions for storing static assets, application data, and large media files. ### How is FlashEdge Storage accessed publicly? Every FlashEdge Storage requires a FlashEdge CDN distribution for public access. After creating a storage, you have to set up a CDN distribution to serve your content publicly. ### How can I privately manage files in FlashEdge Storage? Private access for browsing, uploading, and downloading files is facilitated through file explorers that support Amazon S3 and specific S3 buckets. The recommended options are detailed in the FlashEdge documentation. ### Can I use AWS CLI to manage FlashEdge Storage? Yes, you can use AWS CLI to manage FlashEdge Storage. After installing AWS CLI, configure it with your FlashEdge access keys and use standard AWS S3 commands to upload, download, and manage your files. ### Is it possible to connect to FlashEdge Storage using Cyberduck? Yes, Cyberduck, an open-source client, can connect to FlashEdge Storage. Configure a new connection in Cyberduck by selecting “Amazon S3” as the connection type and entering your FlashEdge Storage access key, secret key, and bucket name. ### How can I secure access to my FlashEdge Storage through HTTPS? To serve content securely via HTTPS with your custom domain, set up a FlashEdge CDN distribution linked to your FlashEdge Storage and configure your custom domain with SSL/TLS certificates as per the instructions in the FlashEdge documentation. ### Can my files be restored if I mistakenly remove them? If you accidentally delete files, we’ll not be able to recover them, as the nature of our backend doesn’t allow us to access the files in a different way than you. ### Are my files safe in FlashEdge Storage? Until you create a publicly accessible FlashEdge CDN distribution, your files will not be publicly available. Even after that, public access is only possible through the FlashEdge CDN distribution domain or, if you set it up, your own custom domain with HTTPS. ### Is encryption available in FlashEdge Storage? All files saved in FlashEdge Storage are encrypted. However, due to the nature and use case of FlashEdge Storage, which stores publicly accessible content, we don't offer any specific encryption settings.