Lumen help
Access information to help you manage your content delivery network (CDN) services. View handbooks with processes and contacts.
Learn how to manage your CDN and Vyvx services using Media portal. Also, access support for the Media portal API.
You can edit a scheduled report to change its frequency, recipients, appended message, or audience its visible to.
If you want to view the data for a scheduled CDN usage report without waiting for the report to run, you can manually trigger the report to run in Media portal.
If you no longer need Media portal to run and send a scheduled report, you can delete it.
You can view Lua-scripting definitions CDN Support has added to a configuration (at your request).
If you need to re-upload a certificate, certificate bundle, private key, or change a private key password, you can make the necessary changes rather than adding a new certificate.
Creating an accept-encoding definition allows you to specify extensions and compression types that should be accepted if included in a client’s request.
Use a response-header definition to return custom header responses to specific requests.
When you add a property to a configuration, you have to add at least one property-based setting (traffic type). You can add additional property-based settings at the same time, but you can add more later using the instructions below. Remember that the CDN applies these property-based settings to all requests to any alias defined within the property.
If you no longer need a configuration, you can delete it from its service component ID (SCID). You can delete a configuration only if it isn't currently promoted to an environment.
You can view a history of the configurations promoted to the staging and production environments for a service component ID (SCID).
Once you push a configuration to a production slot, Lumen adds the CName (canonical name) information for each of the aliases. You can view the CName information in Media portal.
You can view the status of your certificates to see which certificates are ready to use and which need your attention—maybe requiring edits.
Dynamic content transformation (DCT) allows your origin server to serve a single variant of an object, either identity or gzip, and have the Lumen CDN dynamically transform that content into the desired variant. Use a DCT definition to specify the file extensions you want DCT applied to.
To do A/B testing with configurations in production, you can enable a second production slot for a SCID. Once you enable the second production slot, you can then change the traffic allocation for the slots.
Use log-streaming endpoint definitions to specify when, where, and how you want log streaming information posted to your endpoint. Logs are batched in a JSON-formatted payload and posted to your endpoint in near real time (<5 minutes).
You create an AWS4 authentication definition to provide your authentication information to AWS requests sent by HTTP.
Using Media portal, you can create a configuration to tell the Lumen CDN (content delivery network) what to do when it receives requests for your content. Once you have a configuration ready, you deploy it (promote it) to either your staging or production environment.
You create a property to define the origin (and any aliases) and settings that apply to all requests to any alias defined in the property. Once you create a property, you can then add criteria-based settings (match rules) that apply when specific criteria are met.