Doc only update to Amplify to explain platform setting for Next.js 14 SSG only applications

Updates to all tags descriptions.
Updates to all tags descriptions.

Author: aws-sdk-cpp-automation

VERSION

@@ -1 +1 @@
-1.11.404
+1.11.405

generated/src/aws-cpp-sdk-amplify/include/aws/amplify/model/App.h

@@ -142,7 +142,9 @@ namespace Model
      * <code>WEB</code>. For a dynamic server-side rendered (SSR) app, set the platform
      * type to <code>WEB_COMPUTE</code>. For an app requiring Amplify Hosting's
      * original SSR support only, set the platform type to
-     * <code>WEB_DYNAMIC</code>.</p>
+     * <code>WEB_DYNAMIC</code>.</p> <p>If you are deploying an SSG only app with
+     * Next.js 14 or later, you must use the platform type
+     * <code>WEB_COMPUTE</code>.</p>
      */
     inline const Platform& GetPlatform() const{ return m_platform; }
     inline bool PlatformHasBeenSet() const { return m_platformHasBeenSet; }

generated/src/aws-cpp-sdk-amplify/include/aws/amplify/model/CreateAppRequest.h

@@ -90,7 +90,14 @@ namespace Model
      * <code>WEB</code>. For a dynamic server-side rendered (SSR) app, set the platform
      * type to <code>WEB_COMPUTE</code>. For an app requiring Amplify Hosting's
      * original SSR support only, set the platform type to
-     * <code>WEB_DYNAMIC</code>.</p>
+     * <code>WEB_DYNAMIC</code>.</p> <p>If you are deploying an SSG only app with
+     * Next.js version 14 or later, you must set the platform type to
+     * <code>WEB_COMPUTE</code> and set the artifacts <code>baseDirectory</code> to
+     * <code>.next</code> in the application's build settings. For an example of the
+     * build specification settings, see <a
+     * href="https://docs.aws.amazon.com/amplify/latest/userguide/deploy-nextjs-app.html#build-setting-detection-ssg-14">Amplify
+     * build settings for a Next.js 14 SSG application</a> in the <i>Amplify Hosting
+     * User Guide</i>.</p>
      */
     inline const Platform& GetPlatform() const{ return m_platform; }
     inline bool PlatformHasBeenSet() const { return m_platformHasBeenSet; }

generated/src/aws-cpp-sdk-amplify/include/aws/amplify/model/UpdateAppRequest.h

@@ -90,7 +90,9 @@ namespace Model
      * <code>WEB</code>. For a dynamic server-side rendered (SSR) app, set the platform
      * type to <code>WEB_COMPUTE</code>. For an app requiring Amplify Hosting's
      * original SSR support only, set the platform type to
-     * <code>WEB_DYNAMIC</code>.</p>
+     * <code>WEB_DYNAMIC</code>.</p> <p>If you are deploying an SSG only app with
+     * Next.js version 14 or later, you must set the platform type to
+     * <code>WEB_COMPUTE</code>.</p>
      */
     inline const Platform& GetPlatform() const{ return m_platform; }
     inline bool PlatformHasBeenSet() const { return m_platformHasBeenSet; }

generated/src/aws-cpp-sdk-ivs/include/aws/ivs/IVSClient.h

@@ -51,15 +51,16 @@ namespace IVS
    * resource. A tag comprises a <i>key</i> and a <i>value</i>, both set by you. For
    * example, you might set a tag as <code>topic:nature</code> to label a particular
    * video category. See <a
-   * href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging
-   * Amazon Web Services Resources</a> for more information, including restrictions
-   * that apply to tags and "Tag naming limits and requirements"; Amazon IVS has no
-   * service-specific constraints beyond what is documented there.</p> <p>Tags can
-   * help you identify and organize your Amazon Web Services resources. For example,
-   * you can use the same tag for different resources to indicate that they are
-   * related. You can also use tags to manage access (see <a
+   * href="https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html">Best
+   * practices and strategies</a> in <i>Tagging Amazon Web Services Resources and Tag
+   * Editor</i> for details, including restrictions that apply to tags and "Tag
+   * naming limits and requirements"; Amazon IVS has no service-specific constraints
+   * beyond what is documented there.</p> <p>Tags can help you identify and organize
+   * your Amazon Web Services resources. For example, you can use the same tag for
+   * different resources to indicate that they are related. You can also use tags to
+   * manage access (see <a
    * href="https://docs.aws.amazon.com/IAM/latest/UserGuide/access_tags.html"> Access
-   * Tags</a>). </p> <p>The Amazon IVS API has these tag-related endpoints:
+   * Tags</a>). </p> <p>The Amazon IVS API has these tag-related operations:
    * <a>TagResource</a>, <a>UntagResource</a>, and <a>ListTagsForResource</a>. The
    * following resources support tagging: Channels, Stream Keys, Playback Key Pairs,
    * and Recording Configurations.</p> <p>At most 50 tags can be applied to a

generated/src/aws-cpp-sdk-ivs/include/aws/ivs/model/Channel.h

@@ -159,10 +159,11 @@ namespace Model
     /**
      * <p>Tags attached to the resource. Array of 1-50 maps, each of the form
      * <code>string:string (key:value)</code>. See <a
-     * href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging
-     * Amazon Web Services Resources</a> for more information, including restrictions
-     * that apply to tags and "Tag naming limits and requirements"; Amazon IVS has no
-     * service-specific constraints beyond what is documented there.</p>
+     * href="https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html">Best
+     * practices and strategies</a> in <i>Tagging Amazon Web Services Resources and Tag
+     * Editor</i> for details, including restrictions that apply to tags and "Tag
+     * naming limits and requirements"; Amazon IVS has no service-specific constraints
+     * beyond what is documented there.</p>
      */
     inline const Aws::Map<Aws::String, Aws::String>& GetTags() const{ return m_tags; }
     inline bool TagsHasBeenSet() const { return m_tagsHasBeenSet; }

generated/src/aws-cpp-sdk-ivs/include/aws/ivs/model/ChannelSummary.h

@@ -113,10 +113,11 @@ namespace Model
     /**
      * <p>Tags attached to the resource. Array of 1-50 maps, each of the form
      * <code>string:string (key:value)</code>. See <a
-     * href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging
-     * Amazon Web Services Resources</a> for more information, including restrictions
-     * that apply to tags and "Tag naming limits and requirements"; Amazon IVS has no
-     * service-specific constraints beyond what is documented there.</p>
+     * href="https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html">Best
+     * practices and strategies</a> in <i>Tagging Amazon Web Services Resources and Tag
+     * Editor</i> for details, including restrictions that apply to tags and "Tag
+     * naming limits and requirements"; Amazon IVS has no service-specific constraints
+     * beyond what is documented there.</p>
      */
     inline const Aws::Map<Aws::String, Aws::String>& GetTags() const{ return m_tags; }
     inline bool TagsHasBeenSet() const { return m_tagsHasBeenSet; }

generated/src/aws-cpp-sdk-ivs/include/aws/ivs/model/CreateChannelRequest.h

@@ -110,10 +110,11 @@ namespace Model
     /**
      * <p>Array of 1-50 maps, each of the form <code>string:string (key:value)</code>.
      * See <a
-     * href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging
-     * Amazon Web Services Resources</a> for more information, including restrictions
-     * that apply to tags and "Tag naming limits and requirements"; Amazon IVS has no
-     * service-specific constraints beyond what is documented there.</p>
+     * href="https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html">Best
+     * practices and strategies</a> in <i>Tagging Amazon Web Services Resources and Tag
+     * Editor</i> for details, including restrictions that apply to tags and "Tag
+     * naming limits and requirements"; Amazon IVS has no service-specific constraints
+     * beyond what is documented there.</p>
      */
     inline const Aws::Map<Aws::String, Aws::String>& GetTags() const{ return m_tags; }
     inline bool TagsHasBeenSet() const { return m_tagsHasBeenSet; }

generated/src/aws-cpp-sdk-ivs/include/aws/ivs/model/CreatePlaybackRestrictionPolicyRequest.h

@@ -99,10 +99,11 @@ namespace Model
     /**
      * <p>Array of 1-50 maps, each of the form <code>string:string (key:value)</code>.
      * See <a
-     * href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging
-     * Amazon Web Services Resources</a> for more information, including restrictions
-     * that apply to tags and "Tag naming limits and requirements"; Amazon IVS has no
-     * service-specific constraints beyond what is documented there.</p>
+     * href="https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html">Best
+     * practices and strategies</a> in <i>Tagging Amazon Web Services Resources and Tag
+     * Editor</i> for details, including restrictions that apply to tags and "Tag
+     * naming limits and requirements"; Amazon IVS has no service-specific constraints
+     * beyond what is documented there.</p>
      */
     inline const Aws::Map<Aws::String, Aws::String>& GetTags() const{ return m_tags; }
     inline bool TagsHasBeenSet() const { return m_tagsHasBeenSet; }

generated/src/aws-cpp-sdk-ivs/include/aws/ivs/model/CreateRecordingConfigurationRequest.h

@@ -67,10 +67,11 @@ namespace Model
     /**
      * <p>Array of 1-50 maps, each of the form <code>string:string (key:value)</code>.
      * See <a
-     * href="https://docs.aws.amazon.com/general/latest/gr/aws_tagging.html">Tagging
-     * Amazon Web Services Resources</a> for more information, including restrictions
-     * that apply to tags and "Tag naming limits and requirements"; Amazon IVS has no
-     * service-specific constraints beyond what is documented there.</p>
+     * href="https://docs.aws.amazon.com/tag-editor/latest/userguide/best-practices-and-strats.html">Best
+     * practices and strategies</a> in <i>Tagging Amazon Web Services Resources and Tag
+     * Editor</i> for details, including restrictions that apply to tags and "Tag
+     * naming limits and requirements"; Amazon IVS has no service-specific constraints
+     * beyond what is documented there.</p>
      */
     inline const Aws::Map<Aws::String, Aws::String>& GetTags() const{ return m_tags; }
     inline bool TagsHasBeenSet() const { return m_tagsHasBeenSet; }