apache-airflow-providers-amazon 9.12.0__tar.gz → 9.13.0__tar.gz

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: apache-airflow-providers-amazon
-Version: 9.12.0
+Version: 9.13.0
 Summary: Provider package apache-airflow-providers-amazon for Apache Airflow
 Keywords: airflow-provider,amazon,airflow,integration
 Author-email: Apache Software Foundation <dev@airflow.apache.org>
@@ -38,7 +38,7 @@ Requires-Dist: marshmallow>=3
 Requires-Dist: aiobotocore[boto3]>=2.21.1 ; extra == "aiobotocore"
 Requires-Dist: apache-airflow-providers-apache-hive ; extra == "apache-hive"
 Requires-Dist: apache-airflow-providers-cncf-kubernetes>=7.2.0 ; extra == "cncf-kubernetes"
-Requires-Dist: apache-airflow-providers-common-messaging>=1.0.3 ; extra == "common-messaging"
+Requires-Dist: apache-airflow-providers-common-messaging>=2.0.0 ; extra == "common-messaging"
 Requires-Dist: apache-airflow-providers-exasol ; extra == "exasol"
 Requires-Dist: apache-airflow-providers-fab>=2.2.0 ; extra == "fab" and ( python_version < '3.13')
 Requires-Dist: apache-airflow-providers-ftp ; extra == "ftp"
@@ -55,8 +55,8 @@ Requires-Dist: apache-airflow-providers-salesforce ; extra == "salesforce"
 Requires-Dist: apache-airflow-providers-ssh ; extra == "ssh"
 Requires-Dist: apache-airflow-providers-standard ; extra == "standard"
 Project-URL: Bug Tracker, https://github.com/apache/airflow/issues
-Project-URL: Changelog, https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.12.0/changelog.html
-Project-URL: Documentation, https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.12.0
+Project-URL: Changelog, https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.13.0/changelog.html
+Project-URL: Documentation, https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.13.0
 Project-URL: Mastodon, https://fosstodon.org/@airflow
 Project-URL: Slack Chat, https://s.apache.org/airflow-slack
 Project-URL: Source Code, https://github.com/apache/airflow
@@ -104,9 +104,8 @@ Provides-Extra: standard
 
 Package ``apache-airflow-providers-amazon``
 
-Release: ``9.12.0``
+Release: ``9.13.0``
 
-Release Date: ``|PypiReleaseDate|``
 
 Amazon integration (including `Amazon Web Services (AWS) <https://aws.amazon.com/>`__).
 
@@ -118,12 +117,12 @@ This is a provider package for ``amazon`` provider. All classes for this provide
 are in ``airflow.providers.amazon`` python package.
 
 You can find package information and changelog for the provider
-in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.12.0/>`_.
+in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.13.0/>`_.
 
 Installation
 ------------
 
-You can install this package on top of an existing Airflow 2 installation (see ``Requirements`` below
+You can install this package on top of an existing Airflow installation (see ``Requirements`` below
 for the minimum Airflow version supported) via
 ``pip install apache-airflow-providers-amazon``
 
@@ -186,5 +185,5 @@ Dependent package
 ========================================================================================================================  ====================
 
 The changelog for the provider package can be found in the
-`changelog <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.12.0/changelog.html>`_.
+`changelog <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.13.0/changelog.html>`_.
 

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/README.rst

@@ -23,9 +23,8 @@
 
 Package ``apache-airflow-providers-amazon``
 
-Release: ``9.12.0``
+Release: ``9.13.0``
 
-Release Date: ``|PypiReleaseDate|``
 
 Amazon integration (including `Amazon Web Services (AWS) <https://aws.amazon.com/>`__).
 
@@ -37,12 +36,12 @@ This is a provider package for ``amazon`` provider. All classes for this provide
 are in ``airflow.providers.amazon`` python package.
 
 You can find package information and changelog for the provider
-in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.12.0/>`_.
+in the `documentation <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.13.0/>`_.
 
 Installation
 ------------
 
-You can install this package on top of an existing Airflow 2 installation (see ``Requirements`` below
+You can install this package on top of an existing Airflow installation (see ``Requirements`` below
 for the minimum Airflow version supported) via
 ``pip install apache-airflow-providers-amazon``
 
@@ -105,4 +104,4 @@ Dependent package
 ========================================================================================================================  ====================
 
 The changelog for the provider package can be found in the
-`changelog <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.12.0/changelog.html>`_.
+`changelog <https://airflow.apache.org/docs/apache-airflow-providers-amazon/9.13.0/changelog.html>`_.

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/auth-manager/manage/index.rst

@@ -158,15 +158,24 @@ This is equivalent to the :doc:`Viewer role in Flask AppBuilder <apache-airflow-
     principal in Airflow::Group::"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
     action in [
       Airflow::Action::"Configuration.GET",
+      Airflow::Action::"Configuration.LIST",
       Airflow::Action::"Connection.GET",
+      Airflow::Action::"Connection.LIST",
       Airflow::Action::"Custom.GET",
+      Airflow::Action::"Custom.LIST",
       Airflow::Action::"Dag.GET",
+      Airflow::Action::"Dag.LIST",
       Airflow::Action::"Menu.MENU",
       Airflow::Action::"Pool.GET",
+      Airflow::Action::"Pool.LIST",
       Airflow::Action::"Variable.GET",
+      Airflow::Action::"Variable.LIST",
       Airflow::Action::"Asset.GET",
+      Airflow::Action::"Asset.LIST",
       Airflow::Action::"AssetAlias.GET",
+      Airflow::Action::"AssetAlias.LIST",
       Airflow::Action::"Backfill.GET",
+      Airflow::Action::"Backfill.LIST",
       Airflow::Action::"View.GET"
     ],
     resource
@@ -183,17 +192,24 @@ This is equivalent to the :doc:`User role in Flask AppBuilder <apache-airflow-pr
     principal in Airflow::Group::"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
     action in [
       Airflow::Action::"Configuration.GET",
+      Airflow::Action::"Configuration.LIST",
       Airflow::Action::"Connection.GET",
+      Airflow::Action::"Connection.LIST",
       Airflow::Action::"Custom.GET",
+      Airflow::Action::"Custom.LIST",
       Airflow::Action::"Dag.GET",
+      Airflow::Action::"Dag.LIST",
       Airflow::Action::"Menu.MENU",
       Airflow::Action::"Pool.GET",
+      Airflow::Action::"Pool.LIST",
       Airflow::Action::"Variable.GET",
+      Airflow::Action::"Variable.LIST",
       Airflow::Action::"Asset.GET",
+      Airflow::Action::"Asset.LIST",
       Airflow::Action::"View.GET",
       Airflow::Action::"Dag.POST",
       Airflow::Action::"Dag.PUT",
-      Airflow::Action::"Dag.DELETE",
+      Airflow::Action::"Dag.DELETE"
     ],
     resource
   );
@@ -209,13 +225,20 @@ This is equivalent to the :doc:`Op role in Flask AppBuilder <apache-airflow-prov
     principal in Airflow::Group::"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
     action in [
       Airflow::Action::"Configuration.GET",
+      Airflow::Action::"Configuration.LIST",
       Airflow::Action::"Connection.GET",
+      Airflow::Action::"Connection.LIST",
       Airflow::Action::"Custom.GET",
+      Airflow::Action::"Custom.LIST",
       Airflow::Action::"Dag.GET",
+      Airflow::Action::"Dag.LIST",
       Airflow::Action::"Menu.MENU",
       Airflow::Action::"Pool.GET",
+      Airflow::Action::"Pool.LIST",
       Airflow::Action::"Variable.GET",
+      Airflow::Action::"Variable.LIST",
       Airflow::Action::"Asset.GET",
+      Airflow::Action::"Asset.LIST",
       Airflow::Action::"View.GET",
       Airflow::Action::"Dag.POST",
       Airflow::Action::"Dag.PUT",
@@ -230,19 +253,17 @@ This is equivalent to the :doc:`Op role in Flask AppBuilder <apache-airflow-prov
       Airflow::Action::"Variable.PUT",
       Airflow::Action::"Variable.DELETE",
       Airflow::Action::"Asset.POST",
-      Airflow::Action::"Asset.PUT",
       Airflow::Action::"Asset.DELETE",
       Airflow::Action::"Backfill.POST",
-      Airflow::Action::"Backfill.PUT",
-
+      Airflow::Action::"Backfill.PUT"
     ],
     resource
   );
 
-Give DAG specific permissions to a group of users
+Give Dag specific permissions to a group of users
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The policy below gives all DAG related permissions of the DAG ``test`` to a group of users.
+The policy below gives all Dag related permissions of the Dag ``test`` to a group of users.
 
  ::
 
@@ -252,7 +273,7 @@ The policy below gives all DAG related permissions of the DAG ``test`` to a grou
     resource == Airflow::Dag::"test"
   );
 
-The policy below gives all DAG related permissions of the DAGs ``financial-1`` and ``financial-2`` to a group of users.
+The policy below gives all Dag related permissions of the Dags ``financial-1`` and ``financial-2`` to a group of users.
 
  ::
 
@@ -262,7 +283,7 @@ The policy below gives all DAG related permissions of the DAGs ``financial-1`` a
     resource in [Airflow::Dag::"financial-1", Airflow::Dag::"financial-2"]
   );
 
-The policy below gives access to logs of the DAG ``test`` to a group of users.
+The policy below gives access to logs of the Dag ``test`` to a group of users.
 
  ::
 
@@ -282,7 +303,7 @@ For example, if both one **permit** and one **forbid** policies match the reques
 This can be useful if, for example, you want to restrict access to a specific user who belongs to a group that is
 granted all permissions.
 
-The policy below removes access of DAGs ``secret-dag-1`` and ``secret-dag-2`` from a specific user.
+The policy below removes access of Dags ``secret-dag-1`` and ``secret-dag-2`` from a specific user.
 
  ::
 

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/changelog.rst

@@ -26,6 +26,60 @@
 Changelog
 ---------
 
+9.13.0
+......
+
+
+Release Date: ``|PypiReleaseDate|``
+
+Features
+~~~~~~~~
+
+* ``feature: Add OpenLineage support for transfer operators between GCS and S3 (#54269)``
+* ``Update HiveToDynamoDBOperator to support Polars (#54221)``
+* ``Update 'SqlToS3Operator' to support Polars and deprecate 'read_pd_kwargs' (#54195)``
+
+Bug Fixes
+~~~~~~~~~
+
+* ``Fix SqlToS3Operator _partition_dataframe for proper polars support (#54588)``
+* ``fixing file extension issue on SqlToS3Operator (#54187)``
+* ``Fix connection management for EKS token generation (#55195)``
+* ``Retry on more edge cases for bedrock (#55201)``
+
+Misc
+~~~~
+
+* ``Refactor Common Queue Interface (#54651)``
+* ``Introduce 'LIST' logic in AWS auth manager (#54987)``
+* ``Move secrets_masker over to airflow_shared distribution (#54449)``
+* ``Handle task-sdk connection retrieval import error in BaseHook (#54692)``
+* ``Remove end_from_trigger attribute in trigger (#54567)``
+* ``Remove redundant exception handling in AWS hook (#54485)``
+* ``Remove end_from_trigger attribute in trigger (#54531)``
+* ``Unify error handling when connection is not found in aws hook (#54299)``
+* ``Fix a small typo and improve logging in bedrock error handling (#55271)``
+
+Doc-only
+~~~~~~~~
+
+* ``Make term Dag consistent in providers docs (#55101)``
+* ``Mark Batch Executor as stable (#54924)``
+
+.. Below changes are excluded from the changelog. Move them to
+   appropriate section above if needed. Do not delete the lines(!):
+   * ``Remove airflow.models.DAG (#54383)``
+   * ``Add missing test for amazon/aws/executors/ecs/boto_schema.py (#54930)``
+   * ``Move trigger_rule utils from 'airflow/utils'  to 'airflow.task'and integrate with Execution API spec (#53389)``
+   * ``Make AWS notifier tests db independent (#54668)``
+   * ``Replace API server's direct Connection access workaround in BaseHook (#54083)``
+   * ``Switch pre-commit to prek (#54258)``
+   * ``Mock AWS during Athena tests (#54576)``
+   * ``make bundle_name not nullable (#47592)``
+   * ``Add CI support for SQLAlchemy 2.0 (#52233)``
+   * ``Fix Airflow 2 reference in README/index of providers (#55240)``
+   * ``Update models used in bedrock system tests (#55229)``
+
 9.12.0
 ......
 

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/example-dags.rst

@@ -15,9 +15,9 @@
     specific language governing permissions and limitations
     under the License.
 
-Example DAGs
+Example Dags
 ============
 
-You can learn how to use Amazon AWS integrations by analyzing the source code of the example DAGs:
+You can learn how to use Amazon AWS integrations by analyzing the source code of the example Dags:
 
 * `Amazon AWS <https://github.com/apache/airflow/tree/providers-amazon/|version|/providers/amazon/tests/system/amazon/aws>`__

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/executors/batch-executor.rst

@@ -16,8 +16,6 @@
     under the License.
 
 
-.. warning::
-   The Batch Executor is alpha/experimental at the moment and may be subject to change without warning.
 .. |executorName| replace:: Batch
 .. |dockerfileLink| replace:: `here <https://github.com/apache/airflow/blob/main/providers/amazon/src/airflow/providers/amazon/aws/executors/Dockerfile>`__
 .. |configKwargs| replace:: SUBMIT_JOB_KWARGS
@@ -115,8 +113,8 @@ used by the Batch Executor, the appropriate policy needs to be attached to the E
 Additionally, the role also needs to have at least the ``CloudWatchLogsFullAccess``
 (or ``CloudWatchLogsFullAccessV2``) policies. The Job Role is the role that is
 used by the containers to make AWS API requests. This role needs to have
-permissions based on the tasks that are described in the DAG being run.
-If you are loading DAGs via an S3 bucket, this role needs to have
+permissions based on the tasks that are described in the Dag being run.
+If you are loading Dags via an S3 bucket, this role needs to have
 permission to read the S3 bucket.
 
 To create a new Job Role or Execution Role, follow the steps

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/executors/ecs-executor.rst

@@ -134,8 +134,8 @@ ECS Executor, this role needs to have at least the
 ``AmazonECSTaskExecutionRolePolicy`` as well as the
 ``CloudWatchLogsFullAccess`` (or ``CloudWatchLogsFullAccessV2``) policies. The Task Role is the role that is
 used by the containers to make AWS API requests. This role needs to have
-permissions based on the tasks that are described in the DAG being run.
-If you are loading DAGs via an S3 bucket, this role needs to have
+permissions based on the tasks that are described in the Dag being run.
+If you are loading Dags via an S3 bucket, this role needs to have
 permission to read the S3 bucket.
 
 To create a new Task Role or Task Execution Role, follow the steps

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/executors/general.rst

@@ -150,12 +150,12 @@ have python 3.10 installed.
 
 .. BEGIN LOADING_DAGS_OVERVIEW
 
-Loading DAGs
+Loading Dags
 ~~~~~~~~~~~~
 
-There are many ways to load DAGs on a container used by |executorName|. This Dockerfile
+There are many ways to load Dags on a container used by |executorName|. This Dockerfile
 is preconfigured with two possible ways: copying from a local folder, or
-downloading from an S3 bucket. Other methods of loading DAGs are
+downloading from an S3 bucket. Other methods of loading Dags are
 possible as well.
 
 .. END LOADING_DAGS_OVERVIEW
@@ -165,11 +165,11 @@ possible as well.
 From S3 Bucket
 ^^^^^^^^^^^^^^
 
-To load DAGs from an S3 bucket, uncomment the entrypoint line in the
-Dockerfile to synchronize the DAGs from the specified S3 bucket to the
+To load Dags from an S3 bucket, uncomment the entrypoint line in the
+Dockerfile to synchronize the Dags from the specified S3 bucket to the
 ``/opt/airflow/dags`` directory inside the container. You can optionally
 provide ``container_dag_path`` as a build argument if you want to store
-the DAGs in a directory other than ``/opt/airflow/dags``.
+the Dags in a directory other than ``/opt/airflow/dags``.
 
 Add ``--build-arg s3_uri=YOUR_S3_URI`` in the docker build command.
 Replace ``YOUR_S3_URI`` with the URI of your S3 bucket. Make sure you
@@ -194,10 +194,10 @@ build arguments.
 From Local Folder
 ^^^^^^^^^^^^^^^^^
 
-To load DAGs from a local folder, place your DAG files in a folder
+To load Dags from a local folder, place your Dag files in a folder
 within the docker build context on your host machine, and provide the
 location of the folder using the ``host_dag_path`` build argument. By
-default, the DAGs will be copied to ``/opt/airflow/dags``, but this can
+default, the Dags will be copied to ``/opt/airflow/dags``, but this can
 be changed by passing the ``container_dag_path`` build-time argument
 during the Docker build process:
 
@@ -205,7 +205,7 @@ during the Docker build process:
 
    docker build -t my-airflow-image --build-arg host_dag_path=./dags_on_host --build-arg container_dag_path=/path/on/container .
 
-If choosing to load DAGs onto a different path than
+If choosing to load Dags onto a different path than
 ``/opt/airflow/dags``, then the new path will need to be updated in the
 Airflow config.
 

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/executors/index.rst

@@ -25,5 +25,5 @@ Amazon Executors
     :maxdepth: 1
 
     ECS Executor <ecs-executor>
-    Batch Executor (experimental) <batch-executor>
+    Batch Executor <batch-executor>
     Lambda Executor (experimental) <lambda-executor>

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/executors/lambda-executor.rst

@@ -122,7 +122,7 @@ provider package.
 The most secure method is to use IAM roles. When creating a Lambda Function
 Definition, you are able to select an execution role. This role needs
 permissions to publish messages to the SQS queues and to write to CloudWatchLogs
-or S3 if using AWS remote logging and/or using S3 to synchronize dags
+or S3 if using AWS remote logging and/or using S3 to synchronize Dags
 (e.g. ``CloudWatchLogsFullAccess`` or ``CloudWatchLogsFullAccessV2``).
 The AWS credentials used on the Scheduler need permissions to
 describe and invoke Lambda functions as well as to describe and read/delete
@@ -170,12 +170,12 @@ From S3 Bucket
 ^^^^^^^^^^^^^^
 
 Dags can be loaded from S3 when using the provided example app.py, which
-contains logic to synchronize the DAGs from S3 to the local filesystem of
+contains logic to synchronize the Dags from S3 to the local filesystem of
 the Lambda function (see the app.py code |appHandlerLink|).
 
 To load Dags from an S3 bucket add ``--build-arg s3_uri=YOUR_S3_URI`` in
 the docker build command. Replace ``YOUR_S3_URI`` with the URI of your S3
-bucket/path containing your dags. Make sure you have the appropriate
+bucket/path containing your Dags. Make sure you have the appropriate
 permissions to read from the bucket.
 
 .. code-block:: bash

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/index.rst

@@ -66,7 +66,7 @@
     :maxdepth: 1
     :caption: Resources
 
-    Example DAGs <example-dags>
+    Example Dags <example-dags>
     PyPI Repository <https://pypi.org/project/apache-airflow-providers-amazon/>
     Installing from sources <installing-providers-from-sources>
 
@@ -87,9 +87,7 @@ apache-airflow-providers-amazon package
 Amazon integration (including `Amazon Web Services (AWS) <https://aws.amazon.com/>`__).
 
 
-Release: 9.12.0
-
-Release Date: ``|PypiReleaseDate|``
+Release: 9.13.0
 
 Provider package
 ----------------
@@ -100,7 +98,7 @@ All classes for this package are included in the ``airflow.providers.amazon`` py
 Installation
 ------------
 
-You can install this package on top of an existing Airflow 2 installation via
+You can install this package on top of an existing Airflow installation via
 ``pip install apache-airflow-providers-amazon``.
 For the minimum Airflow version supported, see ``Requirements`` below.
 
@@ -168,5 +166,5 @@ Downloading official packages
 You can download officially released packages and verify their checksums and signatures from the
 `Official Apache Download site <https://downloads.apache.org/airflow/providers/>`_
 
-* `The apache-airflow-providers-amazon 9.12.0 sdist package <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.12.0.tar.gz>`_ (`asc <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.12.0.tar.gz.asc>`__, `sha512 <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.12.0.tar.gz.sha512>`__)
-* `The apache-airflow-providers-amazon 9.12.0 wheel package <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.12.0-py3-none-any.whl>`_ (`asc <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.12.0-py3-none-any.whl.asc>`__, `sha512 <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.12.0-py3-none-any.whl.sha512>`__)
+* `The apache-airflow-providers-amazon 9.13.0 sdist package <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.13.0.tar.gz>`_ (`asc <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.13.0.tar.gz.asc>`__, `sha512 <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.13.0.tar.gz.sha512>`__)
+* `The apache-airflow-providers-amazon 9.13.0 wheel package <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.13.0-py3-none-any.whl>`_ (`asc <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.13.0-py3-none-any.whl.asc>`__, `sha512 <https://downloads.apache.org/airflow/providers/apache_airflow_providers_amazon-9.13.0-py3-none-any.whl.sha512>`__)

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/logging/s3-task-handler.rst

@@ -125,7 +125,7 @@ With the above configurations, Webserver and Worker Pods can access Amazon S3 bu
 
 - Using Airflow Web UI
 
-  The final step to create connections under Airflow UI before executing the DAGs.
+  The final step to create connections under Airflow UI before executing the Dags.
 
   * Login to Airflow Web UI with ``admin`` credentials and Navigate to ``Admin -> Connections``
   * Create connection for ``Amazon Web Services`` and select the options (Connection ID and Connection Type) as shown in the image.
@@ -141,6 +141,6 @@ With the above configurations, Webserver and Worker Pods can access Amazon S3 bu
 
 Step4: Verify the logs
 ~~~~~~~~~~~~~~~~~~~~~~
-* Execute example DAGs
+* Execute example Dags
 * Verify the logs in S3 bucket
-* Verify the logs from Airflow UI from DAGs log
+* Verify the logs from Airflow UI from Dags log

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/message-queues/index.rst

@@ -1,4 +1,4 @@
- .. Licensed to the Apache Software Foundation (ASF) under one
+.. Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
     regarding copyright ownership.  The ASF licenses this file
@@ -23,21 +23,12 @@ Amazon SQS Queue Provider
 
 Implemented by :class:`~airflow.providers.amazon.aws.queues.sqs.SqsMessageQueueProvider`
 
-The Amazon SQS Queue Provider is a message queue provider that uses
-Amazon Simple Queue Service (SQS) as the underlying message queue system.
-It allows you to send and receive messages using SQS queues in your Airflow workflows.
-The provider supports both standard and FIFO queues, and it provides features
-such as message visibility timeout, message retention period, and dead-letter queues.
-
-The queue must be matching this regex:
 
-.. exampleinclude:: /../src/airflow/providers/amazon/aws/queues/sqs.py
-    :language: python
-    :dedent: 0
-    :start-after: [START queue_regexp]
-    :end-before: [END queue_regexp]
+The Amazon SQS Queue Provider is a :class:`~airflow.providers.common.messaging.providers.base_provider.BaseMessageQueueProvider` that uses
+Amazon Simple Queue Service (SQS) as the underlying message queue system.
+It allows you to send and receive messages using SQS queues in your Airflow workflows with :class:`~airflow.providers.common.messaging.triggers.msg_queue.MessageQueueTrigger` common message queue interface.
 
 
-The queue parameter is passed directly to ``sqs_queue`` parameter of the underlying
-:class:`~airflow.providers.amazon.aws.triggers.sqs.SqsSensorTrigger` class, and passes
-all the kwargs directly to the trigger constructor if added.
+.. include:: /../src/airflow/providers/amazon/aws/queues/sqs.py
+    :start-after: [START sqs_message_queue_provider_description]
+    :end-before: [END sqs_message_queue_provider_description]

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/notifications/chime_notifier_howto_guide.rst

@@ -21,7 +21,7 @@ How-to Guide for Chime notifications
 Introduction
 ------------
 Chime notifier (:class:`airflow.providers.amazon.aws.notifications.chime.ChimeNotifier`) allows users to send
-messages to a Chime chat room setup via a webhook using the various ``on_*_callbacks`` at both the DAG level and Task level
+messages to a Chime chat room setup via a webhook using the various ``on_*_callbacks`` at both the Dag level and Task level
 
 
 Example Code:
@@ -30,16 +30,16 @@ Example Code:
 .. code-block:: python
 
     from datetime import datetime
-    from airflow import DAG
+    from airflow import Dag
     from airflow.providers.standard.operators.bash import BashOperator
     from airflow.providers.amazon.aws.notifications.chime import send_chime_notification
 
-    with DAG(
+    with Dag(
         dag_id="mydag",
         schedule="@once",
         start_date=datetime(2023, 6, 27),
         on_success_callback=[
-            send_chime_notification(chime_conn_id="my_chime_conn", message="The DAG {{ dag.dag_id }} succeeded")
+            send_chime_notification(chime_conn_id="my_chime_conn", message="The Dag {{ dag.dag_id }} succeeded")
         ],
         catchup=False,
     ):

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/notifications/sns.rst

@@ -23,7 +23,7 @@ How-to Guide for Amazon Simple Notification Service (Amazon SNS) notifications
 Introduction
 ------------
 `Amazon SNS <https://aws.amazon.com/sns/>`__ notifier :class:`~airflow.providers.amazon.aws.notifications.sns.SnsNotifier`
-allows users to push messages to a SNS Topic using the various ``on_*_callbacks`` at both the DAG level and Task level.
+allows users to push messages to a SNS Topic using the various ``on_*_callbacks`` at both the Dag level and Task level.
 
 
 Example Code:
@@ -32,14 +32,14 @@ Example Code:
 .. code-block:: python
 
     from datetime import datetime
-    from airflow import DAG
+    from airflow import Dag
     from airflow.providers.standard.operators.bash import BashOperator
     from airflow.providers.amazon.aws.notifications.sns import send_sns_notification
 
     dag_failure_sns_notification = send_sns_notification(
         aws_conn_id="aws_default",
         region_name="eu-west-2",
-        message="The DAG {{ dag.dag_id }} failed",
+        message="The Dag {{ dag.dag_id }} failed",
         target_arn="arn:aws:sns:us-west-2:123456789098:TopicName",
     )
     task_failure_sns_notification = send_sns_notification(
@@ -49,7 +49,7 @@ Example Code:
         target_arn="arn:aws:sns:us-west-2:123456789098:AnotherTopicName",
     )
 
-    with DAG(
+    with Dag(
         dag_id="mydag",
         schedule="@once",
         start_date=datetime(2023, 1, 1),

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/notifications/sqs.rst

@@ -23,7 +23,7 @@ How-to Guide for Amazon Simple Queue Service (Amazon SQS) notifications
 Introduction
 ------------
 `Amazon SQS <https://aws.amazon.com/sqs/>`__ notifier :class:`~airflow.providers.amazon.aws.notifications.sqs.SqsNotifier`
-allows users to push messages to an Amazon SQS Queue using the various ``on_*_callbacks`` at both the DAG level and Task level.
+allows users to push messages to an Amazon SQS Queue using the various ``on_*_callbacks`` at both the Dag level and Task level.
 
 
 Example Code:
@@ -32,14 +32,14 @@ Example Code:
 .. code-block:: python
 
     from datetime import datetime, timezone
-    from airflow import DAG
+    from airflow import Dag
     from airflow.providers.standard.operators.bash import BashOperator
     from airflow.providers.amazon.aws.notifications.sqs import send_sqs_notification
 
     dag_failure_sqs_notification = send_sqs_notification(
         aws_conn_id="aws_default",
         queue_url="https://sqs.eu-west-1.amazonaws.com/123456789098/MyQueue",
-        message_body="The DAG {{ dag.dag_id }} failed",
+        message_body="The Dag {{ dag.dag_id }} failed",
     )
     task_failure_sqs_notification = send_sqs_notification(
         aws_conn_id="aws_default",
@@ -48,7 +48,7 @@ Example Code:
         message_body="The task {{ ti.task_id }} failed",
     )
 
-    with DAG(
+    with Dag(
         dag_id="mydag",
         schedule="@once",
         start_date=datetime(2023, 1, 1, tzinfo=timezone.utc),

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/operators/athena/athena_boto.rst

@@ -48,7 +48,7 @@ to run a query in Amazon Athena.
 
 In the following example, we query an existing Athena table and send the results to
 an existing Amazon S3 bucket.  For more examples of how to use this operator, please
-see the `Sample DAG <https://github.com/apache/airflow/blob/|version|/providers/amazon/tests/system/amazon/aws/example_athena.py>`__.
+see the `Sample Dag <https://github.com/apache/airflow/blob/|version|/providers/amazon/tests/system/amazon/aws/example_athena.py>`__.
 
 .. exampleinclude:: /../../amazon/tests/system/amazon/aws/example_athena.py
     :language: python

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/operators/emr/emr.rst

@@ -53,12 +53,12 @@ Create an EMR job flow
 You can use :class:`~airflow.providers.amazon.aws.operators.emr.EmrCreateJobFlowOperator` to
 create a new EMR job flow.  The cluster will be terminated automatically after finishing the steps.
 
-The default behaviour is to mark the DAG Task node as success as soon as the cluster is launched
+The default behaviour is to mark the Dag Task node as success as soon as the cluster is launched
 (``wait_policy=None``).
 It is possible to modify this behaviour by using a different ``wait_policy``. Available options are:
 
-- ``WaitPolicy.WAIT_FOR_COMPLETION`` - DAG Task node waits for the cluster to be running
-- ``WaitPolicy.WAIT_FOR_STEPS_COMPLETION`` - DAG Task node waits for the cluster to terminate
+- ``WaitPolicy.WAIT_FOR_COMPLETION`` - Dag Task node waits for the cluster to be running
+- ``WaitPolicy.WAIT_FOR_STEPS_COMPLETION`` - Dag Task node waits for the cluster to terminate
 
 
 This operator can be run in deferrable mode by passing ``deferrable=True`` as a parameter.

{apache_airflow_providers_amazon-9.12.0 → apache_airflow_providers_amazon-9.13.0}/docs/operators/emr/emr_eks.rst

@@ -45,7 +45,7 @@ Create an Amazon EMR EKS virtual cluster
 
 
 The ``EmrEksCreateClusterOperator`` will create an Amazon EMR on EKS virtual cluster.
-The example DAG below shows how to create an EMR on EKS virtual cluster.
+The example Dag below shows how to create an EMR on EKS virtual cluster.
 
 To create an Amazon EMR cluster on Amazon EKS, you need to specify a virtual cluster name,
 the eks cluster that you would like to use , and an eks namespace.
@@ -93,7 +93,7 @@ for more details on job configuration.
     :end-before: [END howto_operator_emr_eks_config]
 
 We pass the ``virtual_cluster_id`` and ``execution_role_arn`` values as operator parameters, but you
-can store them in a connection or provide them in the DAG. Your AWS region should be defined either
+can store them in a connection or provide them in the Dag. Your AWS region should be defined either
 in the ``aws_default`` connection as ``{"region_name": "us-east-1"}`` or a custom connection name
 that gets passed to the operator with the ``aws_conn_id`` parameter. The operator returns the Job ID of the job run.