fix: broken links (#518)

docs/platform/concepts/service_backups.md

@@ -53,13 +53,13 @@ This operation may incur an additional cost to your project.
 Backups are encrypted and not available for download, but you can create your own
 backups with the appropriate tooling:
 
--   [PostgreSQL®](https://www.postgresql.org/docs/14/app-pgdump):
+-   [PostgreSQL®](https://www.postgresql.org/docs/current/app-pgdump.html):
     `pgdump`
 -   [MySQL®](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html):
     `mysqldump`
 -   [Caching](https://redis.io/docs/connect/cli/#remote-backups-of-rdb-files):
     `redis-cli`
--   [Cassandra®](https://docs.datastax.com/en/archived/cql/3.3/cql/cql_reference/cqlshCopy)
+-   [Cassandra®](https://docs.datastax.com/en/cql-oss/3.1/cql/cql_reference/copy_r.html)
     `cqlsh`
 -   [OpenSearch®](https://github.com/elasticsearch-dump/elasticsearch-dump):
     `elasticdump`

docs/products/kafka/kafka-connect/howto/snowflake-sink.md

@@ -7,13 +7,13 @@ The Apache Kafka Connect® Snowflake sink connector enables you to move data fro
 :::note
 See the full set of available parameters and configuration
 options in the [connector's
-documentation](https://docs.snowflake.net/manuals/user-guide/kafka-connector).
+documentation](https://docs.snowflake.com/en/user-guide/kafka-connector-overview).
 :::
 
 ## Prerequisites {#connect_sink_snowflake_prereq}
 
 - An Aiven for Apache Kafka® service
-  [with Apache Kafka Connect enabled](enable-connect) or a
+  [with Apache Kafka Connect enabled](/docs/products/kafka/kafka-connect/howto/enable-connect) or a
   [dedicated Aiven for Apache Kafka Connect cluster](/docs/products/kafka/kafka-connect/get-started#apache_kafka_connect_dedicated_cluster).
 
 - [Prepare the Snowflake account](snowflake-sink-prereq) and collect the following

docs/products/opensearch/howto/sample-dataset.md

@@ -248,7 +248,7 @@ You should be able to see the following structure:
 
 These are the fields you can play with. You can find information on
 dynamic mapping types [in the
-documentation](https://opensearch.org/docs/latest/field-types/index/#dynamic-mapping).
+documentation](https://opensearch.org/docs/latest/field-types/#dynamic-mapping).
 
 ## Sample queries with HTTP client
 

docs/products/postgresql/concepts/dba-tasks-pg.md

@@ -31,11 +31,11 @@ The `aiven_extras` extension, developed and maintained by Aiven, enables
 the `avnadmin` to perform superuser-like functionalities like:
 
 -   Manage
-    [subscriptions](https://www.postgresql.org/docs/current/catalog-pg-subscription)
+    [subscriptions](https://www.postgresql.org/docs/current/catalog-pg-subscription.html)
 -   Manage `auto_explain`
-    [functionality](https://www.postgresql.org/docs/current/auto-explain)
+    [functionality](https://www.postgresql.org/docs/current/auto-explain.html)
 -   Manage
-    [publications](https://www.postgresql.org/docs/current/sql-createpublication)
+    [publications](https://www.postgresql.org/docs/current/sql-createpublication.html)
 -   [Claim public schema ownership](/docs/products/postgresql/howto/claim-public-schema-ownership)
 
 You can install the `aiven_extras` extension executing the following

docs/products/postgresql/concepts/pg-connection-pooling.md

@@ -94,7 +94,7 @@ overloading the PostgreSQL database.
 :::note
 Since 9.6, PostgreSQL offers parallelization support enabling to [run
 queries in
-parallel](https://www.postgresql.org/docs/current/parallel-query)
+parallel](https://www.postgresql.org/docs/current/parallel-query.html)
 on multiple CPU cores.
 :::
 

docs/products/postgresql/concepts/pg-shared-buffers.md

@@ -208,5 +208,5 @@ forced ejection.
 ## Related pages
 
 For more information on shared buffers, see [Resource
-Consumption](https://www.postgresql.org/docs/current/runtime-config-resource)
+Consumption](https://www.postgresql.org/docs/current/runtime-config-resource.html)
 in the PostgreSQL documentation.

docs/products/postgresql/howto/create-manual-backups.md

@@ -10,7 +10,7 @@ window. Aiven stores the backups to the closest available cloud storage to
 enhance restore speed.
 
 Perform a backup of your database using the standard PostgreSQL
-`pg_dump` command. See the [pg_dump docs](https://www.postgresql.org/docs/current/app-pgdump),
+`pg_dump` command. See the [pg_dump docs](https://www.postgresql.org/docs/current/app-pgdump.html),
 but a typical command looks like:
 
 ```bash

docs/products/postgresql/howto/enable-jit.md

@@ -3,7 +3,7 @@ title: Enable JIT in PostgreSQL®
 sidebar_label: Enable JIT
 ---
 
-PostgreSQL® 11 introduces a new component in the execution engine, a [Just-in-Time (JIT) expression compiler](https://www.postgresql.org/docs/current/jit-reason).
+PostgreSQL® 11 introduces a new component in the execution engine, a [Just-in-Time (JIT) expression compiler](https://www.postgresql.org/docs/current/jit-reason.html).
 
 By default, the JIT feature is disabled for PostgreSQL 11 and enabled
 for all the subsequent PostgreSQL versions that Aiven supports. You can

docs/products/postgresql/howto/identify-pg-slow-queries.md

@@ -3,7 +3,7 @@ title: Identify PostgreSQL® slow queries
 sidebar_label: Identify slow queries
 ---
 
-Use the PostgreSQL® `pg_stat_statements` [extension](https://www.postgresql.org/docs/current/pgstatstatements) to find slow queries.
+Use the PostgreSQL® `pg_stat_statements` [extension](https://www.postgresql.org/docs/current/pgstatstatements.html) to find slow queries.
 
 ## Identify slow queries in the Console
 
@@ -27,7 +27,7 @@ Query statistics deduced via the `pg_stat_statements` are the following:
 
 You can also create custom queries using the `pg_stat_statements` view
 and use
-all the [available columns](https://www.postgresql.org/docs/current/pgstatstatements)
+all the [available columns](https://www.postgresql.org/docs/current/pgstatstatements.html)
 to investigate your use case.
 
 ## Prerequisites
@@ -92,7 +92,7 @@ wal_bytes           | numeric          |           |          |
 On older PostgreSQL versions, you might find different column names (for example,
 the column previously named `max_time` is now `max_exec_time`). Always
 refer to the [PostgreSQL® official
-documentation](https://www.postgresql.org/docs/current/pgstatstatements)
+documentation](https://www.postgresql.org/docs/current/pgstatstatements.html)
 with the version you are using for accurate column matching.
 
 :::tip
@@ -206,6 +206,6 @@ ORDER by (shared_blks_hit+shared_blks_dirtied) DESC limit 10;
 Once you have identified slow queries:
 
 - Inspect the query plan and execution using
-  [EXPLAIN ANALYZE](https://www.postgresql.org/docs/current/using-explain) to
+  [EXPLAIN ANALYZE](https://www.postgresql.org/docs/current/using-explain.html) to
   understand how to optimise your design to improve the performance.
 - [Optimize slow PostgreSQL® queries](/docs/products/postgresql/howto/optimize-pg-slow-queries).

docs/products/postgresql/howto/migrate-aiven-db-migrate.md

@@ -101,7 +101,7 @@ calls
 :::warning
 Running a logical replication migration twice on the same cluster creates
 duplicate data. Logical replication also has
-[limitations](https://www.postgresql.org/docs/current/logical-replication-restrictions)
+[limitations](https://www.postgresql.org/docs/current/logical-replication-restrictions.html)
 on what it can copy.
 :::
 

docs/products/postgresql/howto/migrate-db-to-aiven-via-console.md

@@ -29,7 +29,7 @@ With the console migration tool, you can migrate your data using one of these me
 The continuous migration method is used by default in the console. The continuous migration
 keeps the source database operational during the migration. This method
 uses [logical
-replication](https://www.postgresql.org/docs/current/logical-replication),
+replication](https://www.postgresql.org/docs/current/logical-replication.html),
 which enables data transfer not only for the data that has already been
 there in the source database when triggering the migration but also for
 any data written to the source database during the migration.
@@ -184,7 +184,7 @@ To use the default continuous migration method in the console:
 
     For more details on the configuration file's syntax, see [The
     pg_hba.conf
-    File](https://www.postgresql.org/docs/14/auth-pg-hba-conf).
+    File](https://www.postgresql.org/docs/14/auth-pg-hba-conf.html).
 
 -   Enable the logical replication.
 
@@ -301,7 +301,7 @@ It's recommended to migrate into an empty database. If you migrate into
 a populated database, colliding tables with primary keys are not
 affected, but tables without primary keys are appended. Check other
 limitations in [Logical replication
-restrictions](https://www.postgresql.org/docs/current/logical-replication-restrictions).
+restrictions](https://www.postgresql.org/docs/current/logical-replication-restrictions.html).
 :::
 
 Trigger the migration by selecting **Start migration** in the **Database

docs/products/postgresql/howto/migrate-pg-dump-restore.md

@@ -9,7 +9,7 @@ We recommend to migrate your PostgreSQL® database to Aiven by using
 [aiven-db-migrate](migrate-aiven-db-migrate).
 :::
 
-The [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump)
+The [`pg_dump`](https://www.postgresql.org/docs/current/app-pgdump.html)
 tool can be used to extract the data from your existing PostgreSQL
 database and
 [`pg_restore`](https://www.postgresql.org/docs/current/app-pgrestore)
@@ -147,7 +147,7 @@ use the `--no-comments` parameter in `pg_restore` to skip these queries.
 `pg_restore` offers similar `--no-XXX` options to switch off other,
 often unnecessary restore queries. More information is available in the
 [PostgreSQL
-documentation](https://www.postgresql.org/docs/current/app-pgrestore).
+documentation](https://www.postgresql.org/docs/current/app-pgrestore.html).
 :::
 
 ### Poor performance after migration
@@ -163,5 +163,5 @@ service after performing a major version upgrade to ensure the
 statistics are up-to-date.
 
 For more information about `ANALYZE`, you may see the official [SQL
-analyze](https://www.postgresql.org/docs/current/sql-analyze)
+analyze](https://www.postgresql.org/docs/current/sql-analyze.html)
 documentation.

docs/products/postgresql/howto/monitor-database-with-datadog.md

@@ -17,7 +17,7 @@ execution details, along with query and host metrics correlation.
 -   The
     [PostgreSQL extensions](/docs/products/postgresql/reference/list-of-extensions) - `pg_stat_statements` and `aiven_extras`, must be
     enabled by executing the following [CREATE
-    EXTENSION](https://www.postgresql.org/docs/current/sql-createextension)
+    EXTENSION](https://www.postgresql.org/docs/current/sql-createextension.html)
     SQL commands directly on the Aiven for PostgreSQL® database service.
 
 ```bash

docs/products/postgresql/howto/monitor-with-pgwatch2.md

@@ -52,7 +52,7 @@ On the Aiven for PostgreSQL instance to be monitored with pgwatch2:
 
     :::warning
     According to the [PostgreSQL
-    documentation](https://www.postgresql.org/docs/current/runtime-config-statistics),
+    documentation](https://www.postgresql.org/docs/current/runtime-config-statistics.html),
     setting `track_io_timing = on` can cause significant overhead.
     :::
 

docs/products/postgresql/howto/pagila.md

@@ -340,7 +340,7 @@ to answer some of these questions?
     </details>
 
 3.  The `film.description` has the `text` type, allowing for [full text
-    search](https://www.postgresql.org/docs/11/textsearch-intro)
+    search](https://www.postgresql.org/docs/current/textsearch.html)
     queries, what will you search for?
 
     <details><summary>

docs/products/postgresql/howto/pg-long-running-queries.md

@@ -11,7 +11,7 @@ either:
 
 -   [Aiven Console](https://console.aiven.io)
 -   [PostgreSQL®
-    shell](https://www.postgresql.org/docs/current/app-psql)
+    shell](https://www.postgresql.org/docs/current/app-psql.html)
     (`psql`)
 
 ## Terminate long running queries from the Aiven Console
@@ -37,7 +37,7 @@ SELECT pg_terminate_backend(pid);
 
 You can learn more about the `pg_terminate_backend()` function from the
 [official
-documentation](https://www.postgresql.org/docs/current/functions-admin).
+documentation](https://www.postgresql.org/docs/current/functions-admin.html).
 
 You can then use the following query to monitor currently running
 queries:
@@ -57,7 +57,7 @@ SET statement_timeout = 15000
 ```
 
 You may check the [client connection
-defaults](https://www.postgresql.org/docs/current/runtime-config-client)
+defaults](https://www.postgresql.org/docs/current/runtime-config-client.html)
 documentation for more information on the available session variables.
 
 ## Database user error

docs/products/postgresql/howto/pg-object-size.md

@@ -101,5 +101,5 @@ information, see
 
 ## Related pages
 
-- [PostgreSQL interactive terminal](https://www.postgresql.org/docs/15/app-psql)
-- [Database Object Management Functions](https://www.postgresql.org/docs/current/functions-admin#FUNCTIONS-ADMIN-DBOBJECT)
+- [PostgreSQL interactive terminal](https://www.postgresql.org/docs/15/app-psql.html)
+- [Database Object Management Functions](https://www.postgresql.org/docs/current/functions-admin#FUNCTIONS-ADMIN-DBOBJECT.html)

docs/products/postgresql/howto/use-dblink-extension.md

@@ -6,7 +6,7 @@ sidebar_label: Use the dblink extension
 `dblink` is a [PostgreSQL® extension](https://www.postgresql.org/docs/current/dblink) that allows you to connect to other PostgreSQL databases and to run arbitrary queries.
 
 With [Foreign Data
-Wrappers](https://www.postgresql.org/docs/current/postgres-fdw)
+Wrappers](https://www.postgresql.org/docs/current/postgres-fdw.html)
 (FDW) you can uniquely define a remote **foreign server** in order to
 access its data. The database connection details like hostnames are kept
 in a single place, and you only need to create once a **user mapping**

docs/products/postgresql/howto/use-pg-cron-extension.md

@@ -12,7 +12,7 @@ soon as the first run completes.
 
 ## CRON syntax
 
-The schedule uses the standard [cron syntax](https://omni.wikiwand.com/en/articles/Cron),
+The schedule uses the standard [cron syntax](https://en.wikipedia.org/wiki/Cron),
 where an asterisk (`*`) means _execute at every time interval_, and a specific number
 means _execute exclusively at this specific time_:
 

docs/tools/cli/service-cli.md

@@ -427,7 +427,7 @@ retrievable includes:
 
 -   the `public.pg_stat_statements` columns (see the [documentation for
     these statistics
-    columns](https://www.postgresql.org/docs/current/pgstatstatements))
+    columns](https://www.postgresql.org/docs/current/pgstatstatements.html))
     for Aiven for PostgreSQL services.
 -   the `performance_schema.events_statements_summary_by_digest` (refer
     to [documentation on the events information from the performance
@@ -436,8 +436,7 @@ retrievable includes:
 
 A description of the retrieved columns for Aiven for PostgreSQL can be
 found in the dedicated [PostgreSQL
-documentation](https://www.postgresql.org/docs/current/pgstatstatements)
-.
+documentation](https://www.postgresql.org/docs/current/pgstatstatements.html).
 
 | Parameter      | Information                                                                                        |
 | -------------- | -------------------------------------------------------------------------------------------------- |

scripts/check_links.sh

@@ -4,8 +4,12 @@ excludeList=(
     "aiven.io/?!docs"
 	  "aiven.io/docs/assets"
 	  "aiven.io/docs/images"
-    "aiven.io/community"
+    "aiven.io/blog"
     "aiven.io/build"
+    "aiven.io/community"
+    "aiven.io/developer"
+    "aiven.io/mysql"
+    ".*twitter.com"
     ".*cdn.sanity.io"
     ".*console.cloud.google.com"
     ".*docs.npmjs.com"