rebranded to byoc

.github/vale/dicts/aiven.dic

@@ -22,6 +22,7 @@ boolean
 boot
 Bucardo
 business
+BYOC
 Cassandra
 Centrify
 checkpointing

.github/vale/styles/Aiven/capitalization_headings.yml

@@ -21,6 +21,7 @@ exceptions:
   - Boot
   - Business
   - BYOA
+  - BYOC
   - Cassandra
   - ClickHouse
   - CloudWatch

docs/platform/concepts.rst

@@ -51,9 +51,9 @@ Learn about some of the key concepts for working with Aiven platform:
 
   Add (and remove) storage on the fly without upgrading your plan.
 
-* :doc:`Bring your own account (BYOA) </docs/platform/concepts/byoa>`.
+* :doc:`Bring your own cloud (BYOC) </docs/platform/concepts/byoa>`.
 
-  BYOA is an optional setup feature that allows you to purchase your Aiven services through your existing Cloud Provider.
+  BYOC is an optional setup feature that allows you to purchase your Aiven services through your existing Cloud Provider.
 
 * :doc:`Enhanced Compliance Environments (ECE) </docs/platform/concepts/enhanced-compliance-env>`.
 

docs/platform/concepts/aiven-node-firewall-configuration.rst

@@ -6,7 +6,7 @@ The iptables configuration is generated dynamically at runtime depending on serv
 Intra-node connections are limited to point-to-point connections to specific IP addresses. All traffic to ports that are not required for the service to function is rejected instead of dropped to avoid timeouts.
 Service ports that you can connect to depend on the service type and deployment type. The configuration can also affect the ports that are available:
 
-* Is the service in a public network, :doc:`dedicated VPC </docs/platform/howto/manage-vpc-peering>`, virtual cloud account, or a  :doc:`Bring Your Own Account (BYOA) </docs/platform/concepts/byoa>` setup ?
+* Is the service in a public network, :doc:`dedicated VPC </docs/platform/howto/manage-vpc-peering>`, virtual cloud account, or a  :doc:`Bring Your Own Cloud (BYOC) </docs/platform/concepts/byoa>` setup ?
 * Have you configured IP ranges in  user_config.ip_filter?
 * Have you :doc:`enabled public internet access for services in a VPC </docs/platform/howto/public-access-in-vpc>`?
 
@@ -45,6 +45,6 @@ Enhanced compliance environments
 --------------------------------
 In `Enhanced Compliance Environments (ECE) <https://docs.aiven.io/docs/platform/concepts/enhanced-compliance-env>`_, there is additional filtering at VPC level and a SOCKS5 proxy. ECE environments have more variable configurations because we provide more flexibility for configuring these to meet your requirements. Typically, ECE nodes are accessible only over VPC connections and are not exposed to the internet. This results in layered firewalls with cloud-provider SDN firewalls and individual node-specific iptables rules.
 
-BYOA environments
+BYOC environments
 -----------------
-With the BYOA deployment model, you deploy Aiven services under your own cloud accounts. This gives you greater control over deployment configuration, but the VM-level firewall configurations are set at deployment time according to Aiven base configurations. You can apply additional firewalls using your cloud service provider's configuration options.
+With the BYOC deployment model, you deploy Aiven services under your own cloud accounts. This gives you greater control over deployment configuration, but the VM-level firewall configurations are set at deployment time according to Aiven base configurations. You can apply additional firewalls using your cloud service provider's configuration options.

docs/platform/concepts/byoa.rst

@@ -1,29 +1,29 @@
-Bring your own account (BYOA)
-=============================
+Bring your own cloud (BYOC)
+===========================
 
 Aiven services are usually deployed on Aiven managed infrastructure, using
 Aiven managed security protocols, and backed by Aiven managed storage and backups.
 This provides the most seamless, straight forward, and de-risked approach to deploying
 Aiven services. However, there are cases where this approach is not appropriate, such
 as the need to achieve strict regulatory compliance.
 
-In cases like these, Aiven offers customers the ability to instead BYOA (Bring
-Your Own Account).  BYOA allows customers to manage their own infrastructure,
+In cases like these, Aiven offers customers the ability to instead BYOC (Bring
+Your Own Cloud).  BYOC allows customers to manage their own infrastructure,
 their own security posture and keep their data in their own cloud.
 
-When to consider bringing your own account
-------------------------------------------
+When to consider bringing your own cloud
+----------------------------------------
 
-There are three major reasons to utilize BYOA:
+There are three major reasons to utilize BYOC:
 
-1. **Compliance**: Aiven offers managed environments for several standard compliance regulations such as HIPAA, PCI DSS and GDPR. However, if you have strict regulatory requirements, or special compliance requirements, BYOA may be the best option for you.
-2. **Network auditing**: If you require visibility of all traffic within any VPC you operate in or need frequent auditing capabilities, BYOA is potentially a good fit. BYOA gives you the ability to audit network metadata but not the actual contents.
-3. **Fine grained network control**: BYOA requires only some specific network access (e.g. service management and troubleshooting), otherwise allowing you to customize your network to meet any internal requirements or requirements of your customers.
+1. **Compliance**: Aiven offers managed environments for several standard compliance regulations such as HIPAA, PCI DSS and GDPR. However, if you have strict regulatory requirements, or special compliance requirements, BYOC may be the best option for you.
+2. **Network auditing**: If you require visibility of all traffic within any VPC you operate in or need frequent auditing capabilities, BYOC is potentially a good fit. BYOC gives you the ability to audit network metadata but not the actual contents.
+3. **Fine grained network control**: BYOC requires only some specific network access (e.g. service management and troubleshooting), otherwise allowing you to customize your network to meet any internal requirements or requirements of your customers.
 
 Who is eligible?
 ----------------
 
-The BYOA setup is a bespoke service offered on a case-by-case basis, and not
+The BYOC setup is a bespoke service offered on a case-by-case basis, and not
 all cloud providers support it yet. Therefore customers must meet the following
 requirements:
 
@@ -36,18 +36,18 @@ requirements:
 When to use a standard Aiven deployment
 ---------------------------------------
 
-BYOA deployments are not automated and they add additional complexity for communicating
+BYOC deployments are not automated and they add additional complexity for communicating
 to the Aiven control plane, service management, key management and security.
 
 In most cases customers can meet their regulatory and business requirements by utilizing
 a standard Aiven deployment or :doc:`Enhanced Compliance Environment </docs/platform/concepts/enhanced-compliance-env>`. In fact, 99% of Aiven
-customers are able to meet their requirements without BYOA. If you would like to understand
-BYOA better or are unsure which deployment model is the best fit for you, please contact our sales department [email protected].
+customers are able to meet their requirements without BYOC. If you would like to understand
+BYOC better or are unsure which deployment model is the best fit for you, please contact our sales department [email protected].
 
 Pricing and billing
 -------------------
 
-Unlike Aiven's standard all-inclusive pricing, the BYOA setup has custom
+Unlike Aiven's standard all-inclusive pricing, the BYOC setup has custom
 pricing depending on the nature of your requirements. Customers entering this
 arrangement are responsible for all cloud infrastructure and network traffic
 charges.
@@ -56,18 +56,18 @@ charges.
 
 For a cost estimate and analysis, please contact [email protected].
 
-Architecture of BYOA deployments
+Architecture of BYOC deployments
 --------------------------------
 
-With BYOA, you can use any standard Aiven method (e.g. :doc:`CLI </docs/tools/cli>`, :doc:`Terraform </docs/tools/terraform>`) to manage your services and generally have the same user experience as with the regular Aiven deployment model.
+With BYOC, you can use any standard Aiven method (e.g. :doc:`CLI </docs/tools/cli>`, :doc:`Terraform </docs/tools/terraform>`) to manage your services and generally have the same user experience as with the regular Aiven deployment model.
 
-BYOA standard
+BYOC standard
 '''''''''''''
 
 .. image:: /images/platform/byoa-standard.png
    :alt: Overview architecture diagram with VPC set up
 
-A standard BYOA deployment requires the customer to create a Virtual Private Cloud (VPC)
+A standard BYOC deployment requires the customer to create a Virtual Private Cloud (VPC)
 dedicated to Aiven services within each region they want to operate. Aiven will access these
 VPCs via a static IP address and then route traffic through a proxy for additional security.
 In order to accomplish this, Aiven will utilize a bastion host, logically separated from the
@@ -78,28 +78,28 @@ host and the service nodes will reside in a customer managed VPC, they will not
 
 Depending on the service being used, Aiven will take regular backups to enable forking,
 Point in Time Recovery (PITR) and disaster recovery. These backups by default will not
-reside in the customer’s cloud account. If there is a requirement to have all backups
-in your own account we can do this as well. Aiven will need object storage and permissions
+reside in the customer’s cloud. If there is a requirement to have all backups
+in your own cloud, we can do this as well. Aiven will need object storage and permissions
 to read and write in order to accomplish this. Please bear in mind that all backups are
 encrypted using Aiven managed keys and that the customer will be responsible for managing
 object storage configurations.
 
-BYOA with IPsec ingress
+BYOC with IPsec ingress
 '''''''''''''''''''''''
 
 .. image:: /images/platform/byoa-ipsec-ingress.png
    :alt: Overview architecture diagram with IPsec tunnel
 
-A slight variation on a standard BYOA deployment enables Aiven to manage a customer's
+A slight variation on a standard BYOC deployment enables Aiven to manage a customer's
 services through an IPsec tunnel. This deployment can be beneficial if management over
 the public internet is infeasible or adds additional complexity.
 
-BYOA with direct IPsec ingress
+BYOC with direct IPsec ingress
 ''''''''''''''''''''''''''''''
 
 .. image:: /images/platform/byoa-ipsec-ingress-direct.png
    :alt: Overview architecture diagram with direct IPsec access
 
-Again a slight variation on a standard BYOA deployment enables Aiven to manage a customer's
+Again a slight variation on a standard BYOC deployment enables Aiven to manage a customer's
 services through a direct IPsec tunnel. This deployment can be beneficial if there is a
 desire to reduce the number of Aiven managed components.

docs/platform/concepts/enhanced-compliance-env.rst

@@ -67,7 +67,7 @@ Although not exhaustive, Aiven is capable of supporting both the Health Insuranc
 Accountability Act (HIPAA) and the Payment Card Industry Data Security Standard (PCI DSS)
 compliances. If you require compliance beyond these please contact our sales department so we
 can better understand your specific needs. Additionally, we also offer an alternative deployment
-option -- :doc:`Bring Your Own Account (BYOA) </docs/platform/concepts/byoa>`.
+option -- :doc:`Bring Your Own Cloud (BYOC) </docs/platform/concepts/byoa>`.
 
 Migrating
 ----------------

docs/products/grafana/concepts/grafana-features.rst

@@ -7,7 +7,7 @@ Key features of Aiven for Grafana® include:
 
 Quick and flexible deployment options
 -------------------------------------
-With Aiven for Grafana, you can enjoy a quick and flexible deployment process, ensuring production-ready Grafana clusters are available in 10 minutes. You have the flexibility to choose your preferred public cloud platform for deployment from over 100 regions supported. The deployment process also includes high-performance nodes to enhance performance. Aiven supports the Bring-Your-Own-Account (BYOA) deployment model, enabling you to meet strict control requirements. 
+With Aiven for Grafana, you can enjoy a quick and flexible deployment process, ensuring production-ready Grafana clusters are available in 10 minutes. You have the flexibility to choose your preferred public cloud platform for deployment from over 100 regions supported. The deployment process also includes high-performance nodes to enhance performance. Aiven supports the Bring-Your-Own-Cloud (BYOC) deployment model, enabling you to meet strict control requirements. 
 
 Integrate with existing Aiven tools and data infrastructure
 --------------------------------------------------------------

docs/products/kafka/howto/kafka-custom-serde-encrypt.rst

@@ -7,7 +7,7 @@ With the Aiven platform there are several deployment models available to meet yo
 
 - Enhanced Compliance Environments (ECE) to satisfy additional compliance needs such as HIPPA and PCI-DSS
 
-- Bring your own account (BYOA) which allows deployment of Aiven services directly into your cloud account
+- Bring your own cloud (BYOC) which allows deployment of Aiven services directly into your cloud account
 
 In addition to the above, all data transmitted to the Aiven services is encrypted in transit and at rest. 
 

docs/products/redis/concepts/overview.rst

@@ -19,7 +19,7 @@ Aiven for Redis has many features that make it easy and stress-free to use:
 
 * **Managed service:** Aiven for Redis is fully managed, so you don't have to worry about setup, management, or updates. Aiven provides tools and integrations to help you easily use Redis in your data pipelines.
 
-* **Fast and easy deployment:** Aiven for Redis provides production-ready Redis service within a few minutes. You can deploy Redis to the cloud of your choice from 5 public clouds and over 100 regions. Aiven uses high-performance clusters with carefully selected instance types and storage options for top-notch performance. A Bring-your-own-account (BYOA) deployment model is available for strict control requirements.
+* **Fast and easy deployment:** Aiven for Redis provides production-ready Redis service within a few minutes. You can deploy Redis to the cloud of your choice from 5 public clouds and over 100 regions. Aiven uses high-performance clusters with carefully selected instance types and storage options for top-notch performance. A Bring-your-own-cloud (BYOC) deployment model is available for strict control requirements.
 
 * **Integration with data infrastructure:** Aiven ensures secure network connectivity using VPC peering, PrivateLink, or TransitGateway technologies. Aiven integrates with various observability tooling, including Datadog, Prometheus, and Jolokia, or you can use Aiven's observability tools for improved monitoring and logging.