An origin server is a physical location that ​Akamai​ uses to get your actual content. This behavior is required in all properties that retrieve content from an origin.

This behavior in the Default Rule

Origin Server is a mandatory behavior in the Default Rule. An error message is revealed if you delete it, and you need to re-add it. However, you can include an additional instance of the Origin Server behavior in a custom rule outside of the Default Rule. This lets you override what's set in the Default Rule in favor of an alternate origin for various purposes: authorization requests, redirects for downloads, access-denials, failover settings, redirects for special user agents, language settings, or for other needs.

How to configure this behavior

You can set up different types of origin server and there are prerequisites you need to meet before you start applying settings in this behavior. To help with this, we've set up start-to-finish workflows:

• The NetStorage origin server workflow. Here, you use ​Akamai​'s NetStorage service to serve as your origin. It helps automate some of the more complex processes required to set up an origin and integrate it with your Object Delivery property.

• The custom origin server workflow. Follow this workflow if you have your own origin server that holds all of your website or app content that you want to deliver to your end users.

• The third-party origin server workflow. Take a look at this workflow if you're using a third-party cloud provider, such as Amazon Web Services or Google Cloud Storage to serve as your origin server.