Edge

Configure

The configuration for Edge Powered by Akamai starts with the Property Manager configuration. This configuration is accessible through CDN > Properties. As part of the onboarding process for Edge Powered by Akamai, a default configuration utilizing Acquia’s best practices is initially completed, tuned, and activated based on the details obtained during the discovery call.

Versioning

Property configurations are automatically maintained in versions. After a property configuration is activated in the staging or production environment, the version cannot be modified. If new modifications are needed, a new version of the property must be started. By utilizing version control, various configurations can be compared to determine the modifications between them. This helps with troubleshooting a regression and debugging issues between versions.

Hostnames

All hostnames that are to be pointed to Akamai must match a property hostname in the configuration. Adding a hostname to the property configuration is the first step to onboarding a new domain to the Akamai platform. Acquia recommends that you use the same network for all hostnames in the property configuration. If your current Edge Hostnames end with edgesuite.net, continue to utilize the Standard TLS network. Otherwise, if the current Edge Hostnames end with edgekey. net, continue to utilize the Enhanced TLS network. When adding a new hostname, the SSL certificate must be selected as Standard TLS (edgesuite.net hostnames) or Enhanced TLS (edgekey.net hostnames) to determine the network traffic to be utilized.

Rules

Each property configuration is created with a set of rules. These rules control various aspects of your Akamai implementation such as origin hostname, CDN caching, and browser caching. Rules are executed in a top-down order, and lower rules can override the settings of rules that are higher in the configuration. This means that more specific rules must be lower in the property configuration.

Activation

After the configuration changes are complete, the property must be activated on the Akamai network. Prior to activation, ensure that there are no errors or warnings that are created as part of the implementation. Errors, warnings, and notices are displayed at the bottom of the Akamai property configuration and can be expanded to review the information provided. Activation must always be performed first to the staging network and then have spoof testing performed to ensure no regressions are introduced. After the staging is successful, the property configuration can be deployed to the production network. After deploying the property configuration to the production network, perform validation to ensure that everything on your production application is working as expected.