Differences

This shows you the differences between two versions of the page.

--- certification:awscertifiedsolutionarchitecprofessional [2024/01/30 16:19] – skipidar
+++ certification:awscertifiedsolutionarchitecprofessional [2024/02/03 12:21] (current) – skipidar
@@ Line 27: / Line 27: @@
       * Coralogix, and
       * Elastic.
+  * When connecting to S3 from **on-prem**, **DONT use Gateway endpoints** for Amazon **S3**
+    * Gateway endpoints [[https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html | Do not allow access from on premises]]
+  * for migration of **AuroraDB** **to another AWS account**, with **minimal downtime** - [[https://aws.amazon.com/blogs/database/perform-cross-account-amazon-aurora-mysql-migration-with-minimal-downtime/ | use DataBaseMigration DMS replication]]
+  *
@@ Line 211: / Line 215: @@
       * Site-to-Site VPN connection with AWS Direct Connect {{https://docs.aws.amazon.com/images/vpn/latest/s2svpn/images/vpn-direct-connect.png}}
       * Private IP Site-to-Site VPN connection with AWS Direct Connect {{https://docs.aws.amazon.com/images/vpn/latest/s2svpn/images/private-ip-dx.png}}
+  * Direct Connect - summary https://jayendrapatil.com/aws-direct-connect-dx/
+    * only ONE **Virtual Gateway (VGW)** can be attached per VPC
+    * Each connection requires a **Virtual Interface (VIF)**
+    * {{https://jayendrapatil.com/wp-content/uploads/2016/05/screen-shot-2016-05-17-at-1-56-15-pm.png}}
   * AWS **Placement Groups** - use to group EC2 machines, to achive minimal latency between High-performance apps relying on low latency.
     * adding the instance to a group
@@ Line 311: / Line 319: @@
     * **RDS Global Databases** - means there are **async secondary clusters** cross regions
       * Cross-region Global DB replication happens **Asynchronously**, using [[https://docs.aws.amazon.com/prescriptive-guidance/latest/aurora-replication-options/aurora-global-database.html | block storage replication]]
+      * only **one writer instance in the primary AWS Region**, and all write operations must be directed to that instance.
       * **Aurora MySQL** - **can** have global tables cross-regions
       * **Aurora Postgres** - **can** have global tables cross-regions [[https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Replication.html|cross-replicate between regions]]
       * https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-disaster-recovery.html#aurora-global-database-failover
       * {{https://docs.aws.amazon.com/images/AmazonRDS/latest/AuroraUserGuide/images/aurora-global-db-managed-failover-1.png}}
-      * Manual promotion of read replica:
+      * Manual promotion of secondary-cluster:
         * Region is down: {{https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2021/03/01/Screen-Shot-2021-03-01-at-17.36.25.png}}
         * Remove read replica from global: {{https://d2908q01vomqb2.cloudfront.net/887309d048beef83ad3eabf2a79a64a389ab1c9f/2021/02/25/DBBLOG-1244-12.png}}