certification:awscertifiedsolutionarchitecprofessional
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| certification:awscertifiedsolutionarchitecprofessional [2024/01/25 10:56] – skipidar | certification:awscertifiedsolutionarchitecprofessional [2024/02/03 12:21] (current) – skipidar | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| * Coralogix, and | * Coralogix, and | ||
| * Elastic. | * Elastic. | ||
| + | * When connecting to S3 from **on-prem**, | ||
| + | * Gateway endpoints [[https:// | ||
| + | * for migration of **AuroraDB** **to another AWS account**, with **minimal downtime** - [[https:// | ||
| + | * | ||
| Line 74: | Line 78: | ||
| * you should **not use CIDR** as this will open the communication from other EC2 instances on the subnet as well. It is **recommended to use security group IDs** | * you should **not use CIDR** as this will open the communication from other EC2 instances on the subnet as well. It is **recommended to use security group IDs** | ||
| * {{https:// | * {{https:// | ||
| + | * {{https:// | ||
| * **AWS Security Groups** | * **AWS Security Groups** | ||
| * can't block by Ports. | * can't block by Ports. | ||
| Line 196: | Line 201: | ||
| * is probably <color # | * is probably <color # | ||
| * {{https:// | * {{https:// | ||
| - | * A **Virtual Private Gateway** | + | * A **Virtual Private Gateway** alias **virtual gateway** |
| * A virtual private gateway is the VPN concentrator on the Amazon side of the Site-to-Site VPN connection. You create a virtual private gateway and attach it to the VPC from which you want to create the Site-to-Site VPN connection. | * A virtual private gateway is the VPN concentrator on the Amazon side of the Site-to-Site VPN connection. You create a virtual private gateway and attach it to the VPC from which you want to create the Site-to-Site VPN connection. | ||
| * https:// | * https:// | ||
| Line 210: | Line 215: | ||
| * Site-to-Site VPN connection with AWS Direct Connect {{https:// | * Site-to-Site VPN connection with AWS Direct Connect {{https:// | ||
| * Private IP Site-to-Site VPN connection with AWS Direct Connect {{https:// | * Private IP Site-to-Site VPN connection with AWS Direct Connect {{https:// | ||
| + | * Direct Connect - summary https:// | ||
| + | * only ONE **Virtual Gateway (VGW)** can be attached per VPC | ||
| + | * Each connection requires a **Virtual Interface (VIF)** | ||
| + | * {{https:// | ||
| * AWS **Placement Groups** - use to group EC2 machines, to achive minimal latency between High-performance apps relying on low latency. | * 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 | * adding the instance to a group | ||
| Line 256: | Line 265: | ||
| * Can generate **System Manager Patch compliance report** | * Can generate **System Manager Patch compliance report** | ||
| * reference Systems Manager properties - **by name of property** from RDS environment variable | * reference Systems Manager properties - **by name of property** from RDS environment variable | ||
| + | * AWS Systems Manager > State Manager | ||
| + | * configuration management, like " | ||
| + | * ensure that the instances are bootstrapped with specific software at startup | ||
| + | * The following list describes the types of tasks you can perform with State Manager: | ||
| + | * Bootstrap instances with specific software at start-up | ||
| + | * **Download and update agents** on a defined schedule, including SSM Agent | ||
| + | * Configure **network** settings | ||
| + | * **Join instances to a Windows domain** (Windows instances only) | ||
| + | * Patch instances with software updates throughout their lifecycle | ||
| + | * **Run scripts** on Linux and Windows managed instances throughout their lifecycle | ||
| + | * AWS Systems Manager > **SESSION Manager** | ||
| + | * the SSH console with port 22 | ||
| * VPC Sharing | * VPC Sharing | ||
| * within the **same organization** - allows to **share subnets of a VPC** for reuse in another accounts. | * within the **same organization** - allows to **share subnets of a VPC** for reuse in another accounts. | ||
| Line 292: | Line 313: | ||
| * **serverless** - a clusters whose capacity is scaled automatically according to the specified minimum and maximum capacity values | * **serverless** - a clusters whose capacity is scaled automatically according to the specified minimum and maximum capacity values | ||
| * **provisioned DB cluster** - **capacity is managed manually** by creating DB instancesa single primary DB instance (writer) and multiple Aurora Read-Replicas | * **provisioned DB cluster** - **capacity is managed manually** by creating DB instancesa single primary DB instance (writer) and multiple Aurora Read-Replicas | ||
| - | | + | |
| + | * Multi-master - 2 Master instances. With same storage attached. | ||
| + | * {{https:// | ||
| | | ||
| - | * **Global | + | * **RDS Global |
| - | | + | * Cross-region Global DB replication happens |
| - | * **Aurora Postgres** - can NOT cross-replicate between regions | + | * only **one writer instance in the primary AWS Region**, and all write operations must be directed to that instance. |
| - | * Failover (when region fails) or Switchover (when planned) happens in seconds but **surprisingly manually** | + | * **Aurora MySQL** - **can** have global tables cross-regions |
| - | * Each Aurora DB cluster has **one cluster endpoint** and **one primary DB instance**. A **cluster endpoint (or writer endpoint)** for an Aurora | + | |
| - | * https:// | + | * https://docs.aws.amazon.com/ |
| - | * After detaching the read-replica in another region | + | * {{https:// |
| - | * Manual promotion of read replica: | + | * Manual promotion of secondary-cluster: |
| * Region is down: {{https:// | * Region is down: {{https:// | ||
| * Remove read replica from global: {{https:// | * Remove read replica from global: {{https:// | ||
| Line 307: | Line 330: | ||
| * Get new endpoints {{https:// | * Get new endpoints {{https:// | ||
| * Add to DNS {{https:// | * Add to DNS {{https:// | ||
| + | * **Cross Region replication** - means there are read replica installed in other regions | ||
| + | * Cross-region Read replication happens **synchronously**, | ||
| + | * **Aurora MySQL** can do cross-region Aurora Replicas | ||
| + | * **Aurora Postgres** - can NOT [[https:// | ||
| + | * Failover (when region fails) or Switchover (when planned) happens in seconds but **surprisingly manually** | ||
| + | * Each Aurora DB cluster has **one cluster endpoint** and **one primary DB instance**. A **cluster endpoint (or writer endpoint)** for an Aurora DB cluster connects to the current primary DB instance for that DB cluster. This **cluster-endpoint** is the **only one that can perform write operations** such as DDL statements. Because of this, the cluster endpoint is the one that you connect to when you first set up a cluster or when your cluster only contains a single DB instance. | ||
| + | * https:// | ||
| + | * After detaching the read-replica in another region - the **endpoint of the new Write-cluster** in a new region after the failover - **changes**. Application must know the new endpoint, or cross regional DNS must be in place. | ||
| * EC2 | * EC2 | ||
| * Emphimeral **Ec2 instance volumes** - **doesnt support snapshots**. Only EBS does. | * Emphimeral **Ec2 instance volumes** - **doesnt support snapshots**. Only EBS does. | ||
| Line 345: | Line 376: | ||
| * Weighted routing policy – Use to route traffic to multiple resources in proportions that you specify. | * Weighted routing policy – Use to route traffic to multiple resources in proportions that you specify. | ||
| * https:// | * https:// | ||
| - | * AWS **Database Migration Service (DMS)** | + | * AWS **Database Migration Service (DMS)** |
| * With AWS DMS, you can discover your source data stores, convert your source schemas, and migrate your data. | * With AWS DMS, you can discover your source data stores, convert your source schemas, and migrate your data. | ||
| * At a basic level, AWS DMS is a server in the AWS Cloud that runs replication software. You create a source and target connection to tell AWS DMS where to extract data from and where to load it. | * At a basic level, AWS DMS is a server in the AWS Cloud that runs replication software. You create a source and target connection to tell AWS DMS where to extract data from and where to load it. | ||
| Line 610: | Line 641: | ||
| * from e.g. IP spoofing | * from e.g. IP spoofing | ||
| * AWS Elastic Beanstalk - deployment strategy https:// | * AWS Elastic Beanstalk - deployment strategy https:// | ||
| + | * https:// | ||
| * **All at once**: Replace all v1 with v2 at the same time. Failure not handled. | * **All at once**: Replace all v1 with v2 at the same time. Failure not handled. | ||
| * **Canary**: A v2 is deployed and observed. If successful, all remaining v2 instances are deployed immediately. | * **Canary**: A v2 is deployed and observed. If successful, all remaining v2 instances are deployed immediately. | ||
certification/awscertifiedsolutionarchitecprofessional.1706180197.txt.gz · Last modified: by skipidar