AWS appsync documentation change
Summary
Updated internal documentation links by adding double slashes after the domain in URLs
Security assessment
The changes only modify URL formatting (adding extra slashes) without altering security content. No security vulnerabilities, features, or incidents are referenced in the changes. The least-privilege policy mention remains unchanged and is not the focus of the update.
Diff
diff --git a/appsync/latest/devguide/designing-your-schema.md b/appsync/latest/devguide/designing-your-schema.md index 160eeb17a..c53b711e3 100644 --- a//appsync/latest/devguide/designing-your-schema.md +++ b//appsync/latest/devguide/designing-your-schema.md @@ -21 +21 @@ AWS AppSync allows you to define and configure GraphQL schemas. The following se -We recommend reviewing the [Schemas](https://docs.aws.amazon.com/appsync/latest/devguide/schema-components.html) section before continuing. +We recommend reviewing the [Schemas](https://docs.aws.amazon.com//appsync/latest/devguide/schema-components.html) section before continuing. @@ -27 +27 @@ GraphQL is a powerful tool for implementing API services. According to [GraphQL' -This section covers the very first part of your GraphQL implementation, the schema. Using the quote above, a schema plays the role of "providing a complete and understandable description of the data in your API". In other words, a GraphQL schema is a textual representation of your service's data, operations, and the relations between them. The schema is considered the main entry point for your GraphQL service implementation. Unsurprisingly, it's often one of the first things you make in your project. We recommend reviewing the [Schemas](https://docs.aws.amazon.com/appsync/latest/devguide/schema-components.html) section before continuing. +This section covers the very first part of your GraphQL implementation, the schema. Using the quote above, a schema plays the role of "providing a complete and understandable description of the data in your API". In other words, a GraphQL schema is a textual representation of your service's data, operations, and the relations between them. The schema is considered the main entry point for your GraphQL service implementation. Unsurprisingly, it's often one of the first things you make in your project. We recommend reviewing the [Schemas](https://docs.aws.amazon.com//appsync/latest/devguide/schema-components.html) section before continuing. @@ -29 +29 @@ This section covers the very first part of your GraphQL implementation, the sche -To quote the [Schemas](https://docs.aws.amazon.com/appsync/latest/devguide/schema-components.html) section, GraphQL schemas are written in the _Schema Definition Language_ (SDL). SDL is composed of types and fields with an established structure: +To quote the [Schemas](https://docs.aws.amazon.com//appsync/latest/devguide/schema-components.html) section, GraphQL schemas are written in the _Schema Definition Language_ (SDL). SDL is composed of types and fields with an established structure: @@ -74 +74 @@ In GraphQL, the entities `Author` and `Book` represent two different object type -As you can see, the type representations are very close to the diagram. However, the methods are where it gets a bit trickier. These will be placed in one of a few special object types as a field. Their special object categorization depends on their behavior. GraphQL contains three fundamental special object types: queries, mutations, and subscriptions. For more information, see [Special objects](https://docs.aws.amazon.com/appsync/latest/devguide/graphql-types.html#special-object-components). +As you can see, the type representations are very close to the diagram. However, the methods are where it gets a bit trickier. These will be placed in one of a few special object types as a field. Their special object categorization depends on their behavior. GraphQL contains three fundamental special object types: queries, mutations, and subscriptions. For more information, see [Special objects](https://docs.aws.amazon.com//appsync/latest/devguide/graphql-types.html#special-object-components). @@ -218 +218 @@ CLI -When using the CLI, make sure you have the correct permissions to access and create resources in the service. You may want to set [least-privilege](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege) policies for non-admin users who need to access the service. For more information about AWS AppSync policies, see [Identity and access management for AWS AppSync](https://docs.aws.amazon.com/appsync/latest/devguide/security-iam.html). +When using the CLI, make sure you have the correct permissions to access and create resources in the service. You may want to set [least-privilege](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege) policies for non-admin users who need to access the service. For more information about AWS AppSync policies, see [Identity and access management for AWS AppSync](https://docs.aws.amazon.com//appsync/latest/devguide/security-iam.html). @@ -222 +222 @@ Additionally, we recommend reading the console version first if you haven't done - 1. If you haven't already done so, [install](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html) the AWS CLI, then add your [configuration](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-quickstart.html). + 1. If you haven't already done so, [install](https://docs.aws.amazon.com//cli/latest/userguide/cli-chap-getting-started.html) the AWS CLI, then add your [configuration](https://docs.aws.amazon.com//cli/latest/userguide/cli-configure-quickstart.html). @@ -357 +357 @@ Here's an example: -In this step, we added a generic object type with a required `id` field stored as `ID`, a `title` field stored as a `String`, and a `date` field stored as an `AWSDateTime`. To see a list of types and fields and what they do, see [Schemas](https://docs.aws.amazon.com/appsync/latest/devguide/schema-components.html). To see a list of scalars and what they do, see the [Type reference](https://docs.aws.amazon.com/appsync/latest/devguide/type-reference.html). +In this step, we added a generic object type with a required `id` field stored as `ID`, a `title` field stored as a `String`, and a `date` field stored as an `AWSDateTime`. To see a list of types and fields and what they do, see [Schemas](https://docs.aws.amazon.com//appsync/latest/devguide/schema-components.html). To see a list of scalars and what they do, see the [Type reference](https://docs.aws.amazon.com/appsync/latest/devguide/type-reference.html). @@ -402 +402 @@ An output will be returned in the CLI. Here's an example: -In this step, we added a generic object type with a required `id` field stored as `ID`, a `title` field stored as a `String`, and a `date` field stored as an `AWSDateTime`. To see a list of types and fields and what they do, see [Schemas](https://docs.aws.amazon.com/appsync/latest/devguide/schema-components.html). To see a list of scalars and what they do, see [Type reference](https://docs.aws.amazon.com/appsync/latest/devguide/type-reference.html). +In this step, we added a generic object type with a required `id` field stored as `ID`, a `title` field stored as a `String`, and a `date` field stored as an `AWSDateTime`. To see a list of types and fields and what they do, see [Schemas](https://docs.aws.amazon.com//appsync/latest/devguide/schema-components.html). To see a list of scalars and what they do, see [Type reference](https://docs.aws.amazon.com/appsync/latest/devguide/type-reference.html).