diff --git a/.changeset/beige-trainers-run.md b/.changeset/beige-trainers-run.md
new file mode 100644
index 0000000000..70632a3e48
--- /dev/null
+++ b/.changeset/beige-trainers-run.md
@@ -0,0 +1,6 @@
+---
+'@backstage/backend-common': minor
+'@backstage/integration': minor
+---
+
+Add AWS S3 Url Reader
diff --git a/docs/integrations/aws-s3/locations.md b/docs/integrations/aws-s3/locations.md
new file mode 100644
index 0000000000..ec61b1e4a9
--- /dev/null
+++ b/docs/integrations/aws-s3/locations.md
@@ -0,0 +1,28 @@
+---
+id: locations
+sidebar_label: Locations
+title: Amazon Web Services S3 Locations
+# prettier-ignore
+description: Setting up an integration with Amazon Web Services S3
+---
+
+The AWS S3 integration supports loading catalog entities from from an S3 Bucket.
+Entities can be added to
+[static catalog configuration](../../features/software-catalog/configuration.md),
+or registered with the
+[catalog-import](https://github.com/backstage/backstage/tree/master/plugins/catalog-import)
+plugin.
+
+## Configuration
+
+To use this integration, add configuration to your root `app-config.yaml`:
+
+```yaml
+integrations:
+  awsS3:
+    accessKeyID: ${AWS_ACCESS_KEY_ID}
+    secretAccessKey: ${AWS_SECRET_ACCESS_KEY}
+```
+
+Then make sure the environment variables `AWS_ACCESS_KEY_ID` and
+`AWS_SECRET_ACCESS_KEY` are set when you run Backstage.