From 6b05e171099da26483be278b6c5588eef3c6adf0 Mon Sep 17 00:00:00 2001
From: Kha Truong <64438356+khatruong2009@users.noreply.github.com>
Date: Tue, 30 Apr 2024 11:59:40 -0700
Subject: [PATCH] chore: fix broken links by adding inline filters (#7356)
* chore: fix broken links by adding inline filters
* chore: remove the line instead of use InlineFilter since flutter is the only platform with this page
* chore: remove getting started link under storage subheading that was being used as a placeholder
---
src/constants/feature-lists-data.ts | 6 ------
.../native_common/getting-started/common.mdx | 2 ++
.../native_common/getting-started/common.mdx | 2 ++
.../prev/build-a-backend/storage/import/index.mdx | 2 --
.../build-a-backend/storage/import/index.mdx | 13 +++++++++++++
5 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/src/constants/feature-lists-data.ts b/src/constants/feature-lists-data.ts
index f05d3579495..978eaee6a46 100644
--- a/src/constants/feature-lists-data.ts
+++ b/src/constants/feature-lists-data.ts
@@ -266,12 +266,6 @@ const featureListData = {
'Upload and download files to and from cloud storage with advanced controls like pausing and resuming upload operations.',
linkText: 'Upload and Download files',
link: 'build-a-backend/storage/upload/'
- },
- {
- content:
- 'Manage content through APIs for listing, accessing, and manipulating files. Set file permission levels, configure automatic events and triggers, and more.',
- linkText: 'Advanced file operations and access control',
- link: 'build-a-backend/storage/configure-access/'
}
],
heading: 'Storage'
diff --git a/src/fragments/lib-v1/graphqlapi/native_common/getting-started/common.mdx b/src/fragments/lib-v1/graphqlapi/native_common/getting-started/common.mdx
index 9fe3f614603..ea06a51a502 100644
--- a/src/fragments/lib-v1/graphqlapi/native_common/getting-started/common.mdx
+++ b/src/fragments/lib-v1/graphqlapi/native_common/getting-started/common.mdx
@@ -137,6 +137,8 @@ Congratulations! You've created a `Todo` object in your database. Check out the
- [Update data](/gen1/[platform]/prev/build-a-backend/graphqlapi/mutate-data/)
- [Subscribe to data](/gen1/[platform]/prev/build-a-backend/graphqlapi/subscribe-data/)
- [Concepts](/gen1/[platform]/prev/build-a-backend/graphqlapi/api-graphql-concepts/)
+
- [Configure authorization modes](/gen1/[platform]/prev/build-a-backend/graphqlapi/customize-authz-modes)
+
{/* TODO: * [Authorizing API calls with Cognito User Pool] */}
diff --git a/src/fragments/lib/graphqlapi/native_common/getting-started/common.mdx b/src/fragments/lib/graphqlapi/native_common/getting-started/common.mdx
index 873eff2a373..9a2e55c8f1d 100644
--- a/src/fragments/lib/graphqlapi/native_common/getting-started/common.mdx
+++ b/src/fragments/lib/graphqlapi/native_common/getting-started/common.mdx
@@ -141,6 +141,8 @@ Congratulations! You've created a `Todo` object in your database. Check out the
- [Update data](/gen1/[platform]/build-a-backend/graphqlapi/mutate-data/)
- [Subscribe to data](/gen1/[platform]/build-a-backend/graphqlapi/subscribe-data/)
- [Concepts](/gen1/[platform]/build-a-backend/graphqlapi/api-graphql-concepts/)
+
- [Configure authorization modes](/gen1/[platform]/build-a-backend/graphqlapi/customize-authorization-rules)
+
{/* TODO: * [Authorizing API calls with Cognito User Pool] */}
diff --git a/src/pages/[platform]/prev/build-a-backend/storage/import/index.mdx b/src/pages/[platform]/prev/build-a-backend/storage/import/index.mdx
index ff7da184d50..8e3f7a1ed37 100644
--- a/src/pages/[platform]/prev/build-a-backend/storage/import/index.mdx
+++ b/src/pages/[platform]/prev/build-a-backend/storage/import/index.mdx
@@ -67,8 +67,6 @@ By default, Amplify Libraries assumes that S3 buckets are configured with the fo
- `protected/{user_identity_id}/` - Readable by all users, but writable only by the creating user
- `private/{user_identity_id}/` - Only accessible for the individual user
-You can either configure your IAM role to use the Amplify-recommended policies or in your Amplify libraries configuration [overwrite the default storage path behavior](/[platform]/build-a-backend/storage/configure-access/#customize-object-key-path).
-
It is highly recommended to review your S3 bucket's CORS settings. Review the [recommendation guide here](/[platform]/build-a-backend/storage/set-up-storage/#amazon-s3-bucket-cors-policy-setup).
### Configuring IAM role to use Amplify-recommended policies
diff --git a/src/pages/gen1/[platform]/build-a-backend/storage/import/index.mdx b/src/pages/gen1/[platform]/build-a-backend/storage/import/index.mdx
index db7be1818c0..9486eaddaa3 100644
--- a/src/pages/gen1/[platform]/build-a-backend/storage/import/index.mdx
+++ b/src/pages/gen1/[platform]/build-a-backend/storage/import/index.mdx
@@ -67,8 +67,21 @@ By default, Amplify Libraries assumes that S3 buckets are configured with the fo
- `protected/{user_identity_id}/` - Readable by all users, but writable only by the creating user
- `private/{user_identity_id}/` - Only accessible for the individual user
+
+
You can either configure your IAM role to use the Amplify-recommended policies or in your Amplify libraries configuration [overwrite the default storage path behavior](/gen1/[platform]/build-a-backend/storage/configure-access/#customize-object-key-path).
+
+
It is highly recommended to review your S3 bucket's CORS settings. Review the [recommendation guide here](/gen1/[platform]/build-a-backend/storage/set-up-storage/#amazon-s3-bucket-cors-policy-setup).
### Configuring IAM role to use Amplify-recommended policies