Automated Akamai Activation Change Log
Every morning, WebRun signs in to Akamai Control Center, reads the activations from the last day across your property configurations, records which version went to staging and which to production, notes who submitted each and any note they left, texts you when a production activation was not on the change calendar, and posts the log to Telegram.
Akamai
read overnight activations
How do I track which Akamai configurations were activated overnight?
WebRun logs your Akamai changes every morning. It reads the last day of activations in Control Center, records the property, version, network, submitter and timestamp for each, texts the platform lead about production pushes outside the change window, and posts the full change log to Telegram.
- An unexplained config change is caught before it becomes an incident
- Every activation carries a name and a timestamp
- Production pushes outside the change window get a same-morning text
Built for platform leads · SRE teams · web operations · security engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
control.akamai.comin a real browser with your saved login - no setup, no API keys. -
1
Akamai - read overnight activations
WebRun opens Akamai to read overnight activations. - Sign in to Akamai Control Center and open the activation history for the last day
- For each property configuration, record the version activated, the network, and the timestamp
- Note who submitted the activation and any note left on it
- Separate staging activations from production ones, and list the CP codes affected
Done when Every activation from the last day has a property, a version, a network, and a person.
-
2
Twilio - text unexpected pushes
twilio.com
WebRun opens Twilio to text unexpected pushes. - Text the platform lead when a production activation was not on the change calendar
- Name the property, the version, the time, and who submitted it
- Send nothing on mornings where every production push was expected
- Never roll back or activate a version: WebRun reports and the platform lead decides
Done when The platform lead has been told about any unexplained production activation.
-
3
Telegram - post the change log
telegram.org
WebRun opens Telegram to post the change log. - Post the change log to the platform channel, production first then staging
- Show property, version, network, person, and timestamp on each line
- Carry the previous day's log link so a sequence of changes reads in order
Done when The platform channel has the last day's activation log.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Akamai
Sign in once
Every action is checked against this policy before it runs.
Questions, answered
Can it roll back a configuration?
No. WebRun reads activation history and reports it. Rolling back a version or activating a new one stays with your platform lead, because either action changes live traffic handling.
How does it know a push was unexpected?
You give it the change calendar or the window when production pushes are planned. Any production activation outside that window gets a text with the property, the version, and the person who submitted it.
Does it cover staging as well as production?
Yes. Both networks are logged, listed separately, with production first. Staging activations give the context for what is about to reach production, so they stay in the log.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.