From 72951206d331353ed83d75aae113c26bbdb431d0 Mon Sep 17 00:00:00 2001 From: Michele Cereda Date: Wed, 11 Dec 2024 19:48:53 +0100 Subject: [PATCH] chore(ansible): improve upon rds restoration --- knowledge base/cloud computing/aws/iam.md | 2 +- knowledge base/cloud computing/aws/rds.md | 25 +++++++++++++++++++++ snippets/ansible/commands.sh | 27 +++++++++++++---------- snippets/ansible/tasks.yml | 27 ++++++++++++++--------- 4 files changed, 58 insertions(+), 23 deletions(-) diff --git a/knowledge base/cloud computing/aws/iam.md b/knowledge base/cloud computing/aws/iam.md index 9e5c0dd..0a30f62 100644 --- a/knowledge base/cloud computing/aws/iam.md +++ b/knowledge base/cloud computing/aws/iam.md @@ -9,7 +9,7 @@ Authorization is provided by sending requests to grant the principal access to _ Such access is given in response to the authorization request **only** if _policies_ exist that grant the principal permission to the _actions_ **and** the _resources_ defined in the request. -
+
Example When first signing in to the console, one lands on the console's homepage. At this point, one isn't accessing any diff --git a/knowledge base/cloud computing/aws/rds.md b/knowledge base/cloud computing/aws/rds.md index d7f65e2..39c5e37 100644 --- a/knowledge base/cloud computing/aws/rds.md +++ b/knowledge base/cloud computing/aws/rds.md @@ -110,6 +110,29 @@ If any maintenance event is scheduled before the window, it's **initiated** in t complete during the 30-minute maintenance window, while larger events may take more.
Maintenance windows are paused when their DB instances are stopped. +> Watch out for changes application order and timing. +> +>
+> Example: creating a DB instance from snapshot with defined Parameter Group +> +> 1. The request of creation from snapshot is received by the AWS APIs.
+> The Parameter Group's name is defined here. +> +> 1. The DB instance is created with a **default** Parameter Group. +> +> The Parameter group **is** due for change, but this does **NOT** come up as a pending modified value.
+> Checks for pending changes **will** miss it. +> +> 1. The DB instance's state goes from `creating` to `backing-up`.
+> This backup usually takes very little for some unknown reason. +> +> 1. The change in Parameter Group is applied now, requiring the DB instance to be rebooted.
+> The instance's state goes to `modifying`, then `rebooting`. +> +> 1. **NOW** the instance is ready for use. +> +>
+ ## Engine ### PostgreSQL @@ -746,6 +769,7 @@ Solution: reboot the source and target instance and retry. - [Amazon RDS DB instances] - [Maintaining a DB instance] - [Disabling AWS RDS backups when creating/updating instances?] +- [Viewing instance status]