Skip to content

[Amplify JS] updated messaging #5105

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 9, 2023
Merged

[Amplify JS] updated messaging #5105

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/fragments/lib/auth/js/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Authorization is often done in one of two ways:
1. Clients pass the tokens to the backend that perform custom logic to allow or deny actions
1. Clients sign the requests and the backend validates the signature, allowing or denying actions depending on predefined policy. The predefined rules are known as [IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies.html) policies and automatically configured by the Amplify CLI.

The first mode is a common authorization method for REST or GraphQL APIs, while the second mode is necessary for interfacing with AWS services such as S3, Pinpoint, Sumerian, and others.
The first mode is a common authorization method for REST or GraphQL APIs, while the second mode is necessary for interfacing with AWS services such as S3, Pinpoint, and others.

## Sign-up and sign-in

Expand Down
4 changes: 3 additions & 1 deletion src/fragments/lib/xr/getting-started.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
<Callout warning>

Your Sumerian scenes will no longer be available as of 2/21/2023. Consequently, the XR category will be unavailable. You can use Babylon.js, an open source 3D engine to author scenes in the future. Please see [Babylon.js sample](https://github.com/aws-samples/aws-tools-for-babylonjs-editor) for examples on using Babylon.js and publishing your scenes with Amplify Hosting.
The Amazon Sumerian service is no longer accepting new customers. Existing customer scenes will not be available after February 21, 2023. The AWS Amplify XR features depend on the Amazon Sumerian service to function and as a result, will no longer be available.

For more information, please see: https://aws.amazon.com/sumerian/

</Callout>

Expand Down
3 changes: 2 additions & 1 deletion src/fragments/lib/xr/sceneapi.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
<Callout warning>

Your Sumerian scenes will no longer be available as of 2/21/2023. Consequently, the XR category will be unavailable. You can use Babylon.js, an open source 3D engine to author scenes in the future. Please see [Babylon.js sample](https://github.com/aws-samples/aws-tools-for-babylonjs-editor) for examples on using Babylon.js and publishing your scenes with Amplify Hosting.
The Amazon Sumerian service is no longer accepting new customers. Existing customer scenes will not be available after February 21, 2023. The AWS Amplify XR features depend on the Amazon Sumerian service to function and as a result, will no longer be available.

For more information, please see: https://aws.amazon.com/sumerian/
</Callout>

## Using optional progress handlers and options
Expand Down