Share your ideas

New Requirement from Akamai: Max. 5k CPCodes per Contract

Thus far each tenant is assigned a unique set of Akamai CPCodes upon onboarding. We maintain a pool of sets of CPCodes. Once this pool runs low, new sets are requested from Akamai automatically.

Now Akamai urges us to send back CPCodes which are no longer in use so they can recycle them. Akamai (in form of Saurin Makim) told us that they won't be able to handle more than 5000 CPCodes on our contract. As far as I can tell, we already hit that "limit".

The following questions need to be answered:

* At which point in time after a tenant has offboarded may Akamai recycle a CPCode (recycling would also clear any billing/traffic data Akamai has stored)?
* Do we need to persist billing data outside of Akamai?
* What happens once we do require more than 5000 CPCodes? Do we need a new contract?

A proposed workflow:

* Generate log output which can be easily queried containing all required information
* Pull that info monthly and send to Akamai per email. (Could be done by Ops?)

  • Guest
  • Feb 25 2020
What is your industry? Non-Industry Specific
What is the idea priority? High