Merge pull request #7357 from nmelehan-akamai/rc-v1.390.0

[Release] v1.390.0

Author: nmelehan-akamai

archetypes/content.md

@@ -3,8 +3,8 @@ slug: {{ path.Base .File.Dir }}
 title: "{{ replace (path.Base .File.Dir) "-" " " | title }}"
 description: "Two to three sentences describing your guide."
 og_description: "Optional two to three sentences describing your guide when shared on social media. If omitted, the `description` parameter is used within social links."
-authors: ["Linode"]
-contributors: ["Linode"]
+authors: ["Akamai"]
+contributors: ["Akamai"]
 published: {{ now.Format "2006-01-02" }}
 keywords: ['list','of','keywords','and key phrases']
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'

archetypes/marketplace.md

@@ -2,8 +2,8 @@
 title: "Deploy ___App_Name___ through the Linode Marketplace"
 description: "Two to three sentences describing your guide."
 og_description: "Two to three sentences describing your guide when shared on social media. Delete this if not needed."
-authors: ["Linode"]
-contributors: ["Linode"]
+authors: ["Akamai"]
+contributors: ["Akamai"]
 published: {{ now.Format "2006-01-02" }}
 keywords: ['list','of','keywords','and key phrases']
 tags: ["marketplace", "linode platform", "cloud manager"]

archetypes/section.md

@@ -2,8 +2,8 @@
 title: Section Title
 description: "A text passage which will appear below the title of the section on the section's page."
 og_description: 'Two to three sentences describing your guide when shared on social media.'
-authors: ["Linode"]
-contributors: ["Linode"]
+authors: ["Akamai"]
+contributors: ["Akamai"]
 published: {{ now.Format "2006-01-02" }}
 keywords: ["keyword1", "keyword2"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'

archetypes/shortguide.md

@@ -3,7 +3,7 @@ title: "{{ replace .TranslationBaseName "-" " " | title }}"
 description: 'Two to three sentences describing your guide.'
 keywords: []
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
-contributors: ["Linode"]
+contributors: ["Akamai"]
 published: {{ now.Format "2006-01-02" }}
 modified: {{ now.Format "2006-01-02" }}
 headless: true

docs/guides/applications/cloud-storage/understanding-storage-solutions/index.md

@@ -0,0 +1,182 @@
+---
+slug: understanding-storage-solutions
+title: "Understanding Storage Solutions"
+description: "This guide connects the storage architectures requirements of modern applications (data types, access patterns, and performance) to available storage solutions."
+authors: ["Akamai"]
+contributors: ["Akamai"]
+published: 2025-10-30
+keywords: ['storage solutions','block storage','object storage','managed databases','akamai netstorage','akamai edgekv']
+license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+---
+
+Modern applications require diverse storage architectures to handle different data types, access patterns, and performance requirements. Selecting the wrong storage solution can lead to performance bottlenecks, unnecessary costs, and limits that make it hard to grow.
+
+Akamai's portfolio includes multiple storage technologies, each optimized for specific use cases. This analysis covers block storage, object storage, managed databases, Akamai NetStorage, and EdgeKV to help you make informed architectural decisions.
+
+## Block Storage
+
+Block storage partitions data into fixed-size blocks stored on attached volumes. To be used, these volumes must be mounted to compute instances as virtual disks. They provide low-level storage that operating systems can format with any file system.
+
+Block storage delivers consistent, fast response times and high input/output performance, making it suitable for structured workloads requiring frequent read/write operations. The direct-attached nature ensures consistent performance because volumes connect to instances over the data center's high-speed internal network rather than the public internet. This reduces latency and provides predictable I/O operations.
+
+[Akamai's Block Storage service](https://www.linode.com/products/block-storage/) attaches directly to Akamai compute instances, providing persistent storage that survives instance lifecycle changes. Volumes can be resized, detached, and reattached as needed.
+
+### Primary Use Cases for Block Storage
+
+- Persistent storage for virtual machines
+- Operating system boot volumes
+
+    {{< note >}}
+    Not all providers use block storage for boot volumes. For example, Akamai compute instances use bundled storage for boot, with block storage used for additional capacity.
+    {{< /note >}}
+
+### Block Storage Cost Structure
+
+[Akamai Block Storage pricing](https://www.linode.com/pricing/#block-storage) is based on allocated storage space per month, regardless of actual usage or access frequency. This predictable pricing model simplifies capacity planning.
+
+## Object Storage
+
+Object storage treats data as discrete objects, each containing the data payload, metadata, and a unique identifier. This S3-style storage architecture uses a flat namespace that differs fundamentally from traditional hierarchical file systems. Objects are accessible via HTTP-based APIs and S3-compatible tools, such as [s3cmd](https://s3tools.org/s3cmd).
+
+This architecture works well with unstructured data--including images, videos, backups, and log files. Object storage systems scale up easily, and they can offer additional durability if users choose to replicate their data across multiple servers and geographic regions.
+
+[Akamai Object Storage](https://www.linode.com/products/object-storage/) provides S3-compatible APIs, and users can store data copies in multiple locations for backup and speed. The service integrates seamlessly with existing S3-compatible tools and workflows. For Akamai Object Storage, the [Linode CLI](https://techdocs.akamai.com/cloud-computing/docs/using-the-linode-cli-with-object-storage) can also be used to access objects.
+
+### Primary Use Cases for Object Storage
+
+- Static website assets (CSS, JavaScript, images)
+- Media storage and content delivery
+- Data archival and disaster recovery
+- Application backups and logs
+
+### Object Storage Cost Structure
+
+[Pricing for object storage](https://www.linode.com/pricing/#object-storage) is typically charged per GB stored, plus data transfer fees. This model offers cost efficiency for large-scale storage requirements, backed by high durability guarantees.
+
+## Managed Databases
+
+Databases differ from general storage by providing a managed query layer and enforcing relationships among structured data. They optimize for relational or document-based operations rather than simple file storage.
+
+Database software handles indexing, consistency guarantees, and transaction processing. They provide query languages (SQL, NoSQL APIs) and manage complex operations like joins, aggregations, and concurrent access control.
+
+Managed database services provision databases in the cloud so that users don't have to install and maintain the software on compute instances. Akamai offers [managed PostgreSQL and MySQL databases](https://www.linode.com/products/databases/) with automated backups, scaling, and maintenance. These services handle database maintenance for you while providing high availability.
+
+### Primary Use Cases for Managed Databases
+
+- Web and mobile application backends
+- Real-time analytics and reporting
+- Business data modeling and relationships
+- Applications requiring ACID compliance for reliable transactions
+
+### Managed Database Cost Structure
+
+Managed databases include compute resources, storage, maintenance, and monitoring in their [pricing](https://www.linode.com/pricing/#databases). Higher costs reflect the additional services: automated backups, scaling capabilities, and guaranteed availability.
+
+## Akamai NetStorage
+
+[NetStorage](https://techdocs.akamai.com/netstorage/docs/welcome-to-netstorage) is Akamai's established object storage solution that predates the S3 era. It stores files as objects and delivers them via HTTP, similar to modern object storage systems. The service integrates tightly with Akamai's CDN infrastructure, which is optimized for media files and content distribution. NetStorage serves as origin storage for CDN-delivered content.
+
+A key feature of NetStorage is automatic content replication across geographical regions. This keeps the stored content available at all times, even if one area is hit by a power outage or some sort of network congestion.
+
+### Primary Use Cases for Akamai NetStorage
+
+- Media content origin storage for CDN delivery
+- Software distribution and updates
+- Large file hosting for global audiences
+
+### Akamai NetStorage Cost Structure
+
+NetStorage pricing is calculated based on the amount of data stored (either by GB stored or by average GB stored).
+
+## Akamai EdgeKV
+
+[EdgeKV](https://www.akamai.com/products/edgekv) provides a distributed key-value store for edge computing applications. Unlike traditional storage solutions, EdgeKV stores small pieces of data close to users, powering edge-native architectures for the fastest possible access. EdgeKV is sold separately from [EdgeWorkers](https://www.akamai.com/products/serverless-computing-edgeworkers), but it requires EdgeWorkers to function.
+
+This service handles configuration data, user preferences, authentication tokens, and other small pieces of information that applications need quickly. EdgeKV is not suitable for large or persistent data storage.
+
+### Primary Use Cases for Akamai EdgeKV
+
+- Configuration data and application settings
+- User preferences and personalization data
+- Authentication tokens and session data
+- Feature flags and A/B testing variables
+- Small cache values for edge applications
+
+### Akamai EdgeKV Cost Structure
+
+Pricing for EdgeKV is based on the number of operations (reads, writes, deletes, lists) performed, as well as the size of objects (measured in GB) held in durable storage.
+
+## Choosing the Right Solution
+
+When selecting storage for your applications, it is essential to evaluate several key factors. The right choice depends on what your enterprise requires across this mix of factors. The table below provides a concise overview of those factors:
+
+| Storage Type | Data Structure | Performance Profile | Durability | Scalability |
+| :---- | :---- | :---- | :---- | :---- |
+| Object Storage | Objects with metadata | High throughput, eventual consistency | High (replicated) | Very high |
+| Block Storage | Fixed-size blocks | Consistent and predictable for moderate I/O needs | High (persistent) | Scales with instance |
+| Managed Databases | Structured (tables, docs) | High consistency, indexed queries | High (redundant \+ backups) | Scales vertically and horizontally |
+| Akamai NetStorage | Object-like | Optimized for media workflows and software downloads | High | High |
+| EdgeKV | Key-value pairs | Ultra-low latency at the edge | Medium | Edge-scaled |
+
+### Data Type and Structure
+
+Consider this table to map your applications' data types to storage solutions:
+
+| Requirement | Recommended Solution |
+| :---- | :---- |
+| Structured data with relationships | Managed Databases |
+| Unstructured files (images, videos, backups) | Object Storage |
+| File system access for applications | Block Storage |
+| Small configuration values | EdgeKV |
+
+### Access Patterns
+
+Consider this table to map your applications' access patterns (frequency of access, type of operations) to storage solutions:
+
+| Requirement | Recommended Solution |
+| :---- | :---- |
+| Frequent updates and writes | Block Storage, Managed Databases |
+| Infrequent reads with high durability | Object Storage |
+| Fast access to small data worldwide | EdgeKV |
+| Software/media delivery and CDN integration | NetStorage |
+
+### Performance Requirements
+
+Consider this table to map your applications' speed and consistency requirements to storage solutions:
+
+| Requirement | Recommended Solution |
+| :---- | :---- |
+| Fastest response times for databases | Block Storage |
+| High throughput for large files | Object Storage |
+| Ultra-fast edge access | EdgeKV |
+| Optimized media delivery | NetStorage |
+
+### Integration and Compatibility
+
+Consider this table to map existing tools and infrastructure you may already be using to storage solutions:
+
+| Requirement | Recommended Solution |
+| :---- | :---- |
+| Direct attachment to servers | Block Storage |
+| S3-compatible tools and APIs | Object Storage |
+| Database drivers and connection pooling | Managed Databases |
+| CDN and content delivery workflows | NetStorage |
+
+### Budget Considerations
+
+Consider this table to map your cost structures and budget priorities to storage solutions:
+
+| Requirement | Recommended Solution |
+| :---- | :---- |
+| Lowest cost at scale | Object Storage |
+| Predictable monthly costs | Block Storage |
+| Full-service management included | Managed Databases |
+| Integrated CDN pricing | NetStorage |
+
+## Conclusion
+
+Each storage solution addresses specific architectural requirements. Object storage excels for unstructured data at scale, while block storage provides high-performance attached storage. Managed databases handle complex data relationships, and NetStorage integrates with CDN workflows.
+
+Evaluate your data characteristics, access patterns, performance requirements, and budget constraints before making storage decisions. The optimal choice aligns with your application architecture, scalability objectives, and operational requirements.
+
+For applications that require modern object storage capabilities, Akamai Object Storage offers S3-compatible APIs with geographic distribution and competitive pricing.

docs/guides/security/vulnerabilities/hackersploit-note-shortguide/index.md

@@ -0,0 +1,15 @@
+---
+slug: hackersploit-note-shortguide
+title: "HackerSploit Red Team Series Deprecated Note"
+description: "A note that instructs readers the original repository is no longer available on the internet."
+authors: ["Linode"]
+contributors: ["Linode"]
+published: 2025-09-01
+keywords: []
+license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+headless: true
+show_on_rss_feed: false
+---
+{{< note type="note" >}}
+This series has been deprecated. The original repository is no longer available on the internet, and the link has been removed.
+{{< /note >}}

docs/guides/security/vulnerabilities/hackersploit-red-team-series/index.md

@@ -8,6 +8,7 @@ published: 2021-11-03
 keywords: ['security']
 tags: ['security']
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+deprecated: true
 ---
 
 The rate of data breaches and APT attacks has been rapidly increasing during the period of COVID-19. Organizations are starting to recognize that their IT infrastructure has weaknesses and vulnerabilities, at great expense to their operations and customer data. For medium to large enterprise organizations, a defense-in-depth strategy that includes testing your defenses is required. This is where red teaming comes into play.

docs/guides/security/vulnerabilities/linux-defense-evasion-hiding-linux-processes/index.md

@@ -8,10 +8,13 @@ published: 2021-11-03
 keywords: ['security']
 tags: ['security']
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+deprecated: true
 ---
 
 {{% content "hackersploit-red-team-series-note-shortguide" %}}
 
+{{% content "hackersploit-note-shortguide" %}}
+
 {{% content "hackersploit-caution-shortguide" %}}
 
 ## Before You Begin

docs/guides/security/vulnerabilities/linux-red-team-defense-evasion-rootkits/index.md

@@ -8,10 +8,13 @@ published: 2021-11-03
 keywords: ['security']
 tags: ['security']
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+deprecated: true
 ---
 
 {{% content "hackersploit-red-team-series-note-shortguide" %}}
 
+{{% content "hackersploit-note-shortguide" %}}
+
 {{% content "hackersploit-caution-shortguide" %}}
 
 ## Before You Begin

docs/guides/security/vulnerabilities/linux-red-team-exploitation-techniques/index.md

@@ -8,10 +8,13 @@ published: 2021-11-03
 keywords: ['security']
 tags: ['security']
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+deprecated: true
 ---
 
 {{% content "hackersploit-red-team-series-note-shortguide" %}}
 
+{{% content "hackersploit-note-shortguide" %}}
+
 {{% content "hackersploit-caution-shortguide" %}}
 
 ## MITRE ATT&CK Exploitation and Initial Access Techniques
@@ -202,7 +205,7 @@ It is possible to use the Kali Linux GUI in VirtualBox to perform the instructio
 
 ## Port Scanning
 
-The first step in the exploitation phase involves scanning the target server for open ports. The scan lists the services and their respective service versions running on the open ports. Port scanning was briefly explored in the [reconnaissance phase](/docs/guides/red-team-reconnaissance-techniques/). This section shows how to scan open ports and perform enumeration in more detail with the nmap tool.
+The first step in the exploitation phase involves scanning the target server for open ports. The scan lists the services and their respective service versions running on the open ports. This section shows how to scan open ports and perform enumeration in more detail with the nmap tool.
 
 ### Port Scanning with nmap
 
@@ -276,7 +279,7 @@ Nmap done: 1 IP address (1 host up) scanned in 47.02 seconds
     | 111 | RPC |
     | 55995 | RPC |
 
-    We are also able to deduce from the service version banners that the target is running Debian. This information is relevant during the [privilege escalation phase](/docs/guides/linux-red-team-privilege-escalation-techniques/).
+    We are also able to deduce from the service version banners that the target is running Debian.
 
 ## Web Server Enumeration
 
@@ -561,8 +564,7 @@ The kernel version on the target system can be found by running:
 
     uname -a
 
-The output shows the target system is running an outdated kernel. This information is useful during the [privilege escalation phase](/docs/guides/linux-red-team-privilege-escalation-techniques/):
-
+The output shows the target system is running an outdated kernel.
 {{< output >}}
 Linux Raven 3.16.0-6-amd64 #1 SMP Debian 3.16.57-2 (2018-07-14) x86_64 GNU/Linux
 {{< /output >}}
@@ -693,8 +695,7 @@ mysql>
 
 We have now been able to obtain an initial foothold on the target system and take control of the MySQL database server. The next steps for targeting Linux systems include:
 
-- [Elevating your privileges on the target system](/docs/guides/linux-red-team-privilege-escalation-techniques/)
+- Elevating your privileges on the target system
 
-- [Establishing persistence to maintain access](/docs/guides/linux-red-team-persistence-techniques/)
+- Establishing persistence to maintain access
 
-Visit the [HackerSploit Red Team parent page](/docs/guides/hackersploit-red-team-series/) to navigate to other parts of this guide series.