[Serverless] Add EIS to Security Billing Dimensions Page

[gaurav-elastic]

Description

We have started the phased rollout of the Elastic Inference Service to non-trial customers and this ticket is to add its pricing information to the Security Billing Dimensions page.

Page to Update

Security Billing Dimensions webpage

Add a new section for 'Elastic Inference Service' in the end of this document with this text:

"Elastic Inference Service ("EIS") [note link is to docs preview--link to actual EIS docs] enables you to leverage AI-powered search as a service without deploying a model in your serverless project. EIS is configured as a default LLM for use with the Security AI Assistant, Attack Discovery, and other applicable AI features available as part of your 'Complete' tier subscription. Use of the default Elastic LLM will utilize EIS tokens and incur related token-based add-on billing for your serverless project."

[leemthompo]

"Elastic Inference Service ("EIS") [note link is to docs preview--link to actual EIS docs]

Just 🚗 here, but FYI that doc page actually won't be going live with 9.0 AFAIU, @szabosteve can confirm next week. So EIS won't have a dedicated docs page immediately, but the default LLM will be mentioned in various spots, like AI Assistant docs, Playground etc.

[szabosteve]

Yes, I can confirm that the EIS leads team has decided not to publish conceptual docs for EIS in 9.0; we will deliver them in 9.1. In the meantime, the AI Assistant and Playground docs will mention the default LLM (called Elastic LLM) EIS is using. We also have reference docs for creating an inference endpoint with EIS that might also be helpful.

[gaurav-elastic]

Thanks for the above callouts! Based on this, lets publish this section without the hyperlink and then add them later once they are available.

[gaurav-elastic]

EIS rollout has been paused and the changes have been held back until the legal FAQs have been published. The changes to the doc are ready and commented out until then. I will update this ticket when we are ready.

[jmikell821]

Note from @gaurav-elastic on naming conventions here for when we publish this.