Merge branch 'add-migration-docs' into add-gen1-gen2-migrations

Author: josefaidt

.github/workflows/accessibility_scan.yml

@@ -8,7 +8,7 @@ env:
 jobs:
   accessibility:
     name: Runs accessibility scan on changed pages
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: Checkout branch
         uses: actions/checkout@0ad4b8fadaa221de15dcec353f45205ec38ea70b # v4.1.4
@@ -32,7 +32,7 @@ jobs:
             const buildDir = process.env.BUILD_DIR;
             return getChangedPages({github, context, buildDir});
       - name: Run site
-        run: | 
+        run: |
           python -m http.server 3000 -d ${{ env.BUILD_DIR }} &
           sleep 5
       - name: Run accessibility tests on changed/new MDX pages

.github/workflows/check_for_console_errors.yml

@@ -9,7 +9,7 @@ permissions:
   contents: read
 jobs:
   CheckConsoleErrors:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: Checkout repository
         uses: actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29 # v4.1.6

.github/workflows/check_pr_for_broken_links.yml

@@ -7,7 +7,7 @@ env:
   BUILD_DIR: 'client/www/next-build'
 jobs:
   CheckPRLinks:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-22.04
     steps:
       - name: Checkout repository
         uses: actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29 # v4.1.6

cspell.json

@@ -68,6 +68,7 @@
     "amazonaws",
     "amazonaws",
     "amazoncognito",
+    "amazonlinux",
     "AmazonPersonalizeProvider",
     "AmazonS3Client",
     "Amplif",
@@ -494,6 +495,7 @@
     "dataaccess",
     "dataacess",
     "databinding",
+    "datalogconfig",
     "dataset",
     "datasource",
     "DataSource",

src/directory/directory.mjs

@@ -292,6 +292,9 @@ export const directory = {
                     },
                     {
                       path: 'src/pages/[platform]/build-a-backend/data/custom-business-logic/connect-http-datasource/index.mdx'
+                    },
+                    {
+                      path: 'src/pages/[platform]/build-a-backend/data/custom-business-logic/batch-ddb-operations/index.mdx'
                     }
                   ]
                 },
@@ -337,6 +340,9 @@ export const directory = {
                 },
                 {
                   path: 'src/pages/[platform]/build-a-backend/data/aws-appsync-apollo-extensions/index.mdx'
+                },
+                {
+                  path: 'src/pages/[platform]/build-a-backend/data/enable-logging/index.mdx'
                 }
               ]
             },

src/pages/[platform]/build-a-backend/auth/concepts/passwordless/index.mdx

@@ -42,6 +42,8 @@ Passwordless authentication removes the security risks and user friction associa
 
 </Callout>
 
+Learn how to implement passwordless sign-in flows by [overriding the Cognito UserPool to enable the sign-in methods below](/[platform]/build-a-backend/auth/modify-resources-with-cdk/#override-cognito-userpool-to-enable-passwordless-sign-in-methods).
+
 {/* need a section about what a "preferred" factor is */}
 
 ## SMS OTP

src/pages/[platform]/build-a-backend/auth/connect-your-frontend/sign-in/index.mdx

@@ -812,6 +812,12 @@ func confirmSignIn() -> AnyCancellable {
 
 To sign in using an external identity provider such as Google, use the `signInWithRedirect` function.
 
+<Callout info>
+
+For guidance on configuring an external Identity Provider with Amplify see [External Identity Providers](/[platform]/build-a-backend/auth/concepts/external-identity-providers/)
+
+</Callout>
+
 ```ts
 import { signInWithRedirect } from "aws-amplify/auth"
 

src/pages/[platform]/build-a-backend/data/aws-appsync-apollo-extensions/index.mdx

@@ -320,6 +320,19 @@ You can alternatively download the introspection schema using the [`fetch-schema
 2. On the left side, select Schema
 3. When viewing your schema, there should a “Export schema” drop down. Select this and download the `schema.json` file.
 4. Add this file to your project as directed by [Apollo documentation](https://www.apollographql.com/docs/kotlin/advanced/plugin-recipes#specifying-the-schema-location) 
+
+### Type Mapping AppSync Scalars
+By default, [AWS AppSync Scalars](https://docs.aws.amazon.com/appsync/latest/devguide/scalars.html#graph-ql-aws-appsync-scalars) will default to the `Any` type. You can map these scalars to more explicit types by editing the `apollo` block in your `app/build.gradle[.kts]` file. In the example below, we are now mapping a few of our AppSync scalar types to `String` instead of `Any`. Additional improvements could be made by writing [custom class adapters](https://www.apollographql.com/docs/kotlin/essentials/custom-scalars#define-class-mapping) to convert date/time scalars into Kotlin date/time class types.
+
+```kotlin
+apollo {
+    service("{serviceName}") {
+        packageName.set("{packageName}")
+        mapScalarToKotlinString("AWSDateTime")
+        mapScalarToKotlinString("AWSEmail")
+    }
+}
+```
 </InlineFilter>
 
 ### Performing Queries, Mutations, and Subscriptions with Apollo client

src/pages/[platform]/build-a-backend/data/connect-to-existing-data-sources/connect-postgres-mysql-database/index.mdx

@@ -208,7 +208,7 @@ When deploying your app to production, you need to [add the database connection
 
 ## Rename generated models and fields
 
-To improve the ergonomics of your API, you might want to rename the generate fields or types to better accommodate your use case. Use the `renameModels()` and `renameModelFields()` modifiers to rename the auto-inferred data models and their fields.
+To improve the ergonomics of your API, you might want to rename the generate fields or types to better accommodate your use case. Use the `renameModels()` modifier to rename the auto-inferred data models.
 
 ```ts
 // Rename models or fields to be more idiomatic for frontend code

src/pages/[platform]/build-a-backend/data/custom-business-logic/batch-ddb-operations/index.mdx

@@ -0,0 +1,153 @@
+import { getCustomStaticPath } from '@/utils/getCustomStaticPath';
+
+export const meta = {
+  title: 'Batch DynamoDB Operations',
+  description:
+    'Batch DynamoDB Operations',
+  platforms: [
+    'android',
+    'angular',
+    'flutter',
+    'javascript',
+    'nextjs',
+    'react',
+    'react-native',
+    'swift',
+    'vue'
+  ]
+};
+
+export const getStaticPaths = async () => {
+  return getCustomStaticPath(meta.platforms);
+};
+
+export function getStaticProps() {
+  return {
+    props: {
+      meta
+    }
+  };
+}
+
+Batch DynamoDB operations allow you to add multiple items in single mutation.
+
+## Step 1 - Define a custom mutation
+
+```ts title="amplify/data/resource.ts"
+import { type ClientSchema, a, defineData } from '@aws-amplify/backend';
+
+const schema = a.schema({
+  // 1. Define your return type as a custom type or model
+  Post: a.model({
+    id: a.id(),
+    content: a.string(),
+    likes: a.integer()
+  }),
+
+  // 2. Define your mutation with the return type and, optionally, arguments
+  BatchCreatePost: a
+    .mutation()
+    // arguments that this query accepts
+    .arguments({
+      content: a.string().array()
+    })
+    .returns(a.ref('Post').array())
+    // only allow signed-in users to call this API
+    .authorization(allow => [allow.authenticated()])
+});
+
+export type Schema = ClientSchema<typeof schema>;
+
+export const data = defineData({
+  schema
+});
+```
+
+## Step 2 - Configure custom business logic handler code
+
+After your query or mutation is defined, you need to author your custom business logic using a [custom resolver powered by AppSync JavaScript resolver](https://docs.aws.amazon.com/appsync/latest/devguide/tutorials-js.html).
+
+Custom resolvers work on a "request/response" basis. You choose a data source, map your request to the data source's input parameters, and then map the data source's response back to the query/mutation's return type. Custom resolvers provide the benefit of no cold starts, less infrastructure to manage, and no additional charge for Lambda function invocations. Review [Choosing between custom resolver and function](https://docs.aws.amazon.com/appsync/latest/devguide/resolver-reference-overview-js.html#choosing-data-source).
+
+In your `amplify/data/resource.ts` file, define a custom handler using `a.handler.custom`.
+
+```ts title="amplify/data/resource.ts"
+import { type ClientSchema, a, defineData } from '@aws-amplify/backend';
+
+const schema = a.schema({
+  Post: a.model({
+    id: a.id(),
+    content: a.string(),
+    likes: a.integer()
+  }),
+
+  BatchCreatePost: a
+    .mutation()
+    .arguments({
+      contents: a.string().array()
+    })
+    .returns(a.ref('Post').array())
+    .authorization(allow => [allow.authenticated()])
+    // 1. Add the custom handler
+    .handler(
+      a.handler.custom({
+        dataSource: a.ref('Post'),
+        entry: './BatchCreatePostHandler.js',
+      })
+    )
+});
+
+export type Schema = ClientSchema<typeof schema>;
+
+export const data = defineData({
+  schema
+});
+```
+
+Amplify will store some values in the resolver context stash that can be accessed in the custom resolver.
+
+| Name                      | Description                                  |
+| ------------------------- | -------------------------------------------- |
+| awsAppsyncApiId           | The ID of the AppSync API.                   |
+| amplifyApiEnvironmentName | The Amplify api environment name. (`NONE` in sandbox) |
+
+The Amplify generated DynamoDB table names can be constructed from the variables in the context stash. The table name is in the format `<model-name>-<aws-appsync-api-id>-<amplify-api-environment-name>`. For example, the table name for the `Post` model would be `Post-123456-dev` where `123456` is the AppSync API ID and `dev` is the Amplify API environment name.
+
+```ts title="amplify/data/BatchCreatePostHandler.js"
+import { util } from '@aws-appsync/utils';
+
+export function request(ctx) {
+  var now = util.time.nowISO8601();
+
+  return {
+    operation: 'BatchPutItem',
+    tables: {
+      [`Post-${ctx.stash.awsAppsyncApiId}-${ctx.stash.amplifyApiEnvironmentName}`]: ctx.args.contents.map((content) =>
+        util.dynamodb.toMapValues({
+          content,
+          id: util.autoId(),
+          createdAt: now,
+          updatedAt: now,
+        })
+      ),
+    },
+  };
+}
+
+export function response(ctx) {
+  if (ctx.error) {
+    util.error(ctx.error.message, ctx.error.type);
+  }
+  return ctx.result.data[`Post-${ctx.stash.awsAppsyncApiId}-${ctx.stash.amplifyApiEnvironmentName}`];
+}
+```
+
+## Step 3 - Invoke the custom query or mutation
+
+From your generated Data client, you can find all your custom queries and mutations under the `client.queries.` and `client.mutations.` APIs respectively.
+
+```ts
+const { data, errors } = await client.mutations.BatchCreatePost({
+  contents: ['Post 1', 'Post 2', 'Post 3']
+});
+```