rds-proxy-password-rotation 1.0.0__tar.gz

rds_proxy_password_rotation-1.0.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

rds_proxy_password_rotation-1.0.0/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.1
+Name: rds-proxy-password-rotation
+Version: 1.0.0
+Summary: A program to rotate the password of an RDS database accessed via a RDS proxy
+Home-page: https://github.com/Hapag-Lloyd/rds-proxy-password-rotation
+Author: Hapag-Lloyd AG
+Author-email: info@hlag.com
+Project-URL: Bug Tracker, https://github.com/Hapag-Lloyd/rds-proxy-password-rotation/issues
+Project-URL: repository, https://github.com/Hapag-Lloyd/rds-proxy-password-rotation
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aws-lambda-powertools==3.4.0
+Requires-Dist: boto3==1.35.83
+Requires-Dist: boto3-stubs[secretsmanager]==1.35.83
+Requires-Dist: dependency-injector==4.44.0
+Requires-Dist: pydantic==2.10.4
+Provides-Extra: test
+Requires-Dist: pytest==8.3.4; extra == "test"
+Requires-Dist: pytest-cov==6.0.0; extra == "test"
+Requires-Dist: uuid==1.30; extra == "test"
+Requires-Dist: nose==1.3.7; extra == "test"
+
+# rds-proxy-password-rotation
+
+:warning: **Work in progress** :warning:
+
+- implement step CREATE_SECRET
+- implement step SET_SECRET
+- implement step TEST_SECRET
+- implement step FINISH_SECRET
+- add Terraform module
+
+Python script for multi-user password rotation using RDS and RDS proxy. It supports a separate credential for the application.
+
+## Pre-requisites
+
+1. Python 3.10 or later
+2. For each db user:
+   1. Create a secret in AWS Secrets Manager with the following key-value pairs:
+      - `username`: The username for the user
+      - `password`: The password for the user
+      This credential will be used by the application to connect to the proxy. You may add additional key-value pairs as needed.
+   2. Clone the user in the database and grant the necessary permissions. We suggest to add a `-clone` suffix to the username.
+   3. Create two secrets (for the original user and the clone) in AWS Secrets Manager with the following key-value pairs:
+     - `username`: The username for the user
+     - `password`: The password for the user
+   These credentials are used by the proxy to connect to the database. You may add additional key-value pairs as needed.
+
+## Architecture
+
+![Architecture](assets/architecture.png)
+
+## Challenges with RDS and RDS Proxy
+
+RDS Proxy is a fully managed, highly available database proxy for Amazon Relational Database Service (RDS) that makes applications
+more scalable, more resilient to database failures, and more secure. It allows applications to pool and share database connections
+to improve efficiency and reduce the load on your database instances.
+
+However, RDS Proxy does not support multi-user password rotation out of the box. This script provides a solution to this problem.
+
+Using an RDS Proxy requires a secret in AWS Secrets Manager with the credentials to connect to the database. This secret is used by
+the proxy to connect to the database. The proxy allows the application to connect to the database using the same credentials and
+then forwards the requests to the database with the same credentials. This means that the credentials in the secret must be valid
+in the database at all times. But what if you want to rotate the password for the user that the proxy uses to connect to the
+database? You can’t just update the secret in SecretsManager because the proxy will stop working as soon as the secret is updated.
+And you can’t just update the password in the database because the proxy will stop working as soon as the password is updated.
+
+## Why password rotation is a good practice
+
+Password rotation is a good idea for several reasons:
+
+1. **Enhanced Security**: Regularly changing passwords reduces the risk of unauthorized access due to compromised credentials.
+2. **Mitigates Risk**: Limits the time window an attacker has to exploit a stolen password.
+3. **Compliance**: Many regulatory standards and security policies require periodic password changes.
+4. **Reduces Impact of Breaches**: If a password is compromised, rotating it ensures that the compromised password is no longer valid.
+5. **Encourages Good Practices**: Promotes the use of strong, unique passwords and discourages password reuse.

rds_proxy_password_rotation-1.0.0/README.md

@@ -0,0 +1,54 @@
+# rds-proxy-password-rotation
+
+:warning: **Work in progress** :warning:
+
+- implement step CREATE_SECRET
+- implement step SET_SECRET
+- implement step TEST_SECRET
+- implement step FINISH_SECRET
+- add Terraform module
+
+Python script for multi-user password rotation using RDS and RDS proxy. It supports a separate credential for the application.
+
+## Pre-requisites
+
+1. Python 3.10 or later
+2. For each db user:
+   1. Create a secret in AWS Secrets Manager with the following key-value pairs:
+      - `username`: The username for the user
+      - `password`: The password for the user
+      This credential will be used by the application to connect to the proxy. You may add additional key-value pairs as needed.
+   2. Clone the user in the database and grant the necessary permissions. We suggest to add a `-clone` suffix to the username.
+   3. Create two secrets (for the original user and the clone) in AWS Secrets Manager with the following key-value pairs:
+     - `username`: The username for the user
+     - `password`: The password for the user
+   These credentials are used by the proxy to connect to the database. You may add additional key-value pairs as needed.
+
+## Architecture
+
+![Architecture](assets/architecture.png)
+
+## Challenges with RDS and RDS Proxy
+
+RDS Proxy is a fully managed, highly available database proxy for Amazon Relational Database Service (RDS) that makes applications
+more scalable, more resilient to database failures, and more secure. It allows applications to pool and share database connections
+to improve efficiency and reduce the load on your database instances.
+
+However, RDS Proxy does not support multi-user password rotation out of the box. This script provides a solution to this problem.
+
+Using an RDS Proxy requires a secret in AWS Secrets Manager with the credentials to connect to the database. This secret is used by
+the proxy to connect to the database. The proxy allows the application to connect to the database using the same credentials and
+then forwards the requests to the database with the same credentials. This means that the credentials in the secret must be valid
+in the database at all times. But what if you want to rotate the password for the user that the proxy uses to connect to the
+database? You can’t just update the secret in SecretsManager because the proxy will stop working as soon as the secret is updated.
+And you can’t just update the password in the database because the proxy will stop working as soon as the password is updated.
+
+## Why password rotation is a good practice
+
+Password rotation is a good idea for several reasons:
+
+1. **Enhanced Security**: Regularly changing passwords reduces the risk of unauthorized access due to compromised credentials.
+2. **Mitigates Risk**: Limits the time window an attacker has to exploit a stolen password.
+3. **Compliance**: Many regulatory standards and security policies require periodic password changes.
+4. **Reduces Impact of Breaches**: If a password is compromised, rotating it ensures that the compromised password is no longer valid.
+5. **Encourages Good Practices**: Promotes the use of strong, unique passwords and discourages password reuse.

rds_proxy_password_rotation-1.0.0/pyproject.toml

@@ -0,0 +1,3 @@
+[build-system]
+requires = ['setuptools==75.6.0']
+build-backend = 'setuptools.build_meta'

rds_proxy_password_rotation-1.0.0/setup.cfg

@@ -0,0 +1,44 @@
+[metadata]
+name = rds-proxy-password-rotation
+version = 1.0.0
+author = Hapag-Lloyd AG
+author_email = info@hlag.com
+description = A program to rotate the password of an RDS database accessed via a RDS proxy
+long_description = file: README.md
+long_description_content_type = text/markdown
+url = https://github.com/Hapag-Lloyd/rds-proxy-password-rotation
+project_urls = 
+	Bug Tracker = https://github.com/Hapag-Lloyd/rds-proxy-password-rotation/issues
+	repository = https://github.com/Hapag-Lloyd/rds-proxy-password-rotation
+classifiers = 
+	Programming Language :: Python :: 3
+	License :: OSI Approved :: Apache Software License
+	Operating System :: OS Independent
+
+[options]
+package_dir = 
+	= src
+packages = find:
+python_requires = >=3.10
+install_requires = 
+	aws-lambda-powertools==3.4.0
+	boto3==1.35.83
+	boto3-stubs[secretsmanager]==1.35.83
+	dependency-injector==4.44.0
+	pydantic==2.10.4
+
+[options.extras_require]
+test = 
+	pytest==8.3.4
+	pytest-cov==6.0.0
+	uuid==1.30
+	
+	nose==1.3.7
+
+[options.packages.find]
+where = src
+
+[egg_info]
+tag_build = 
+tag_date = 0
+

rds_proxy_password_rotation-1.0.0/src/rds_proxy_password_rotation.egg-info/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.1
+Name: rds-proxy-password-rotation
+Version: 1.0.0
+Summary: A program to rotate the password of an RDS database accessed via a RDS proxy
+Home-page: https://github.com/Hapag-Lloyd/rds-proxy-password-rotation
+Author: Hapag-Lloyd AG
+Author-email: info@hlag.com
+Project-URL: Bug Tracker, https://github.com/Hapag-Lloyd/rds-proxy-password-rotation/issues
+Project-URL: repository, https://github.com/Hapag-Lloyd/rds-proxy-password-rotation
+Classifier: Programming Language :: Python :: 3
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: aws-lambda-powertools==3.4.0
+Requires-Dist: boto3==1.35.83
+Requires-Dist: boto3-stubs[secretsmanager]==1.35.83
+Requires-Dist: dependency-injector==4.44.0
+Requires-Dist: pydantic==2.10.4
+Provides-Extra: test
+Requires-Dist: pytest==8.3.4; extra == "test"
+Requires-Dist: pytest-cov==6.0.0; extra == "test"
+Requires-Dist: uuid==1.30; extra == "test"
+Requires-Dist: nose==1.3.7; extra == "test"
+
+# rds-proxy-password-rotation
+
+:warning: **Work in progress** :warning:
+
+- implement step CREATE_SECRET
+- implement step SET_SECRET
+- implement step TEST_SECRET
+- implement step FINISH_SECRET
+- add Terraform module
+
+Python script for multi-user password rotation using RDS and RDS proxy. It supports a separate credential for the application.
+
+## Pre-requisites
+
+1. Python 3.10 or later
+2. For each db user:
+   1. Create a secret in AWS Secrets Manager with the following key-value pairs:
+      - `username`: The username for the user
+      - `password`: The password for the user
+      This credential will be used by the application to connect to the proxy. You may add additional key-value pairs as needed.
+   2. Clone the user in the database and grant the necessary permissions. We suggest to add a `-clone` suffix to the username.
+   3. Create two secrets (for the original user and the clone) in AWS Secrets Manager with the following key-value pairs:
+     - `username`: The username for the user
+     - `password`: The password for the user
+   These credentials are used by the proxy to connect to the database. You may add additional key-value pairs as needed.
+
+## Architecture
+
+![Architecture](assets/architecture.png)
+
+## Challenges with RDS and RDS Proxy
+
+RDS Proxy is a fully managed, highly available database proxy for Amazon Relational Database Service (RDS) that makes applications
+more scalable, more resilient to database failures, and more secure. It allows applications to pool and share database connections
+to improve efficiency and reduce the load on your database instances.
+
+However, RDS Proxy does not support multi-user password rotation out of the box. This script provides a solution to this problem.
+
+Using an RDS Proxy requires a secret in AWS Secrets Manager with the credentials to connect to the database. This secret is used by
+the proxy to connect to the database. The proxy allows the application to connect to the database using the same credentials and
+then forwards the requests to the database with the same credentials. This means that the credentials in the secret must be valid
+in the database at all times. But what if you want to rotate the password for the user that the proxy uses to connect to the
+database? You can’t just update the secret in SecretsManager because the proxy will stop working as soon as the secret is updated.
+And you can’t just update the password in the database because the proxy will stop working as soon as the password is updated.
+
+## Why password rotation is a good practice
+
+Password rotation is a good idea for several reasons:
+
+1. **Enhanced Security**: Regularly changing passwords reduces the risk of unauthorized access due to compromised credentials.
+2. **Mitigates Risk**: Limits the time window an attacker has to exploit a stolen password.
+3. **Compliance**: Many regulatory standards and security policies require periodic password changes.
+4. **Reduces Impact of Breaches**: If a password is compromised, rotating it ensures that the compromised password is no longer valid.
+5. **Encourages Good Practices**: Promotes the use of strong, unique passwords and discourages password reuse.

rds_proxy_password_rotation-1.0.0/src/rds_proxy_password_rotation.egg-info/SOURCES.txt

@@ -0,0 +1,9 @@
+LICENSE
+README.md
+pyproject.toml
+setup.cfg
+src/rds_proxy_password_rotation.egg-info/PKG-INFO
+src/rds_proxy_password_rotation.egg-info/SOURCES.txt
+src/rds_proxy_password_rotation.egg-info/dependency_links.txt
+src/rds_proxy_password_rotation.egg-info/requires.txt
+src/rds_proxy_password_rotation.egg-info/top_level.txt

rds_proxy_password_rotation-1.0.0/src/rds_proxy_password_rotation.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

rds_proxy_password_rotation-1.0.0/src/rds_proxy_password_rotation.egg-info/requires.txt

@@ -0,0 +1,11 @@
+aws-lambda-powertools==3.4.0
+boto3==1.35.83
+boto3-stubs[secretsmanager]==1.35.83
+dependency-injector==4.44.0
+pydantic==2.10.4
+
+[test]
+pytest==8.3.4
+pytest-cov==6.0.0
+uuid==1.30
+nose==1.3.7

rds_proxy_password_rotation-1.0.0/src/rds_proxy_password_rotation.egg-info/top_level.txt

@@ -0,0 +1 @@
+