diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 36a75f292..7cd9b82d6 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -39,7 +39,6 @@ jobs:
           - "alice"
           - "apollo"
           - "arcc"
-          - "aws_tower"
           - "awsbatch"
           - "azurebatch"
           - "bi"
diff --git a/README.md b/README.md
index 035f21b72..9d056ec6a 100644
--- a/README.md
+++ b/README.md
@@ -93,7 +93,6 @@ Currently documentation is available for the following systems:
 - [APOLLO](docs/apollo.md)
 - [ARCC](docs/arcc.md)
 - [AWSBATCH](docs/awsbatch.md)
-- [AWS_TOWER](docs/aws_tower.md)
 - [AZUREBATCH](docs/azurebatch.md)
 - [BIGPURPLE](docs/bigpurple.md)
 - [BI](docs/bi.md)
@@ -258,10 +257,12 @@ Currently documentation is available for the following pipelines within specific
 - ampliseq
   - [BINAC](docs/pipeline/ampliseq/binac.md)
   - [UPPMAX](docs/pipeline/ampliseq/uppmax.md)
+- atacseq
+  - [SBC_SHARC](docs/pipeline/atacseq/sbc_sharc.md)
+- chipseq
+  - [SBC_SHARC](docs/pipeline/chipseq/sbc_sharc.md)
 - cutandrun
   - [UNC_LONGLEAF](docs/pipeline/cutandrun/unc_longleaf.md)
-- demultiplex
-  - [AWS_TOWER](docs/pipeline/demultiplex/aws_tower.md)
 - eager
   - [EVA](docs/pipeline/eager/eva.md)
 - funcscan
diff --git a/conf/aws_tower.config b/conf/aws_tower.config
deleted file mode 100644
index ab7786d4c..000000000
--- a/conf/aws_tower.config
+++ /dev/null
@@ -1,21 +0,0 @@
-//Nextflow config file for running on AWS batch
-params {
-    config_profile_description = 'AWS Batch with Tower Profile'
-    config_profile_contact = 'Gisela Gabernet (@ggabernet)'
-    config_profile_url = 'https://aws.amazon.com/batch/'
-}
-
-timeline {
-    overwrite = true
-}
-report {
-    overwrite = true
-}
-trace {
-    overwrite = true
-}
-dag {
-    overwrite = true
-}
-
-process.executor = 'awsbatch'
diff --git a/docs/aws_tower.md b/docs/aws_tower.md
deleted file mode 100644
index 6274bf394..000000000
--- a/docs/aws_tower.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# nf-core/configs: AWS Batch with Tower Configuration
-
-To be used when submitting jobs to AWS Batch by using Tower Forge. If you are not using Tower Forge, consider using the profile `awsbatch` where you can directly specify the Batch queue, AWS region and AWS cli path.
-
-This profile defines `awsbatch` as executor, and allows `overwrite` of `trace`, `timeline`, `report` and `dag` to allow resuming pipelines.