linkage

ACM/_ACM.md

@@ -1,7 +1,7 @@
 # Amazon Certificate Manager
-Provisions, manages, and deploys public and private SSL/TLS certificate for use with AWS Services.
+Provisions, manages, and deploys public and private SSL/TLS certificate for use with [[AWS]] Services.
 
-ACM handles the complexity of creating and managing public SSL/TLS certificates for your AWS based websites and applications.
+ACM handles the complexity of creating and managing public SSL/TLS certificates for your [[AWS]] based websites and applications.
 
 ACM handles two kinds of certificates:
 1. Public - Certificates provided by ACM (Free)
@@ -9,7 +9,7 @@ ACM handles two kinds of certificates:
 
 ACM can handle multiple subdomains and wildcard domains (*.example.com).
 
-ACM can be attached to the following AWS resources:
+ACM can be attached to the following [[AWS]] resources:
 - [[ELB]]
 - [[_CloudFront|CloudFront]]
 - [[API Gateway]]

API Gateway/_API Gateway.md

@@ -1,5 +1,5 @@
 # [[API]] Gateway
-A front to some kind of application on AWS. 
+A front to some kind of application on [[AWS]]. 
 
 Can be one of three flavors:
 - [[REST]]

Athena/_Athena.md

@@ -1,5 +1,5 @@
 # Athena
 
-Amazon Athena is like a library with a massive, disorganised warehouse of books (your data in [[_S3|S3]]). Instead of hiring a librarian to manually sort and read every book each time you ask a question, Athena uses a card catalog system (AWS Glue Data Catalog). You write a query like `find all books by author X published after 2000` on a slip of paper (SQL Query). The catalog tells Athena exactly which shelves and boxes contain relevant books, so it only opens those boxes and scans those pages. Each book is read by a team of temporary workers (distributed query engine) who work in parallel, each reading different pages and jotting down answers on sticky notes. The workers then hand their notes to a foreman (coordinator) who combines them into a single answer. Crucially, the workers never move the books or write in them - they just read. They are paid per page read (data scanned), so you want the catalog to be precise to avoid paying for scanning the entire warehouse. If the catalog is wrong (a box contains fictions when it's actually non-fiction), the workers might miss books or scan irrelevant ones, wasting time and money. Athena's power is that it can query any book in any format (CSV, JSON, Parquet), as long as the catalog describes how to interpret it, and it never alters the original books.
+Amazon Athena is like a library with a massive, disorganised warehouse of books (your data in [[_S3|S3]]). Instead of hiring a librarian to manually sort and read every book each time you ask a question, Athena uses a card catalog system ([[AWS]] Glue Data Catalog). You write a query like `find all books by author X published after 2000` on a slip of paper (SQL Query). The catalog tells Athena exactly which shelves and boxes contain relevant books, so it only opens those boxes and scans those pages. Each book is read by a team of temporary workers (distributed query engine) who work in parallel, each reading different pages and jotting down answers on sticky notes. The workers then hand their notes to a foreman (coordinator) who combines them into a single answer. Crucially, the workers never move the books or write in them - they just read. They are paid per page read (data scanned), so you want the catalog to be precise to avoid paying for scanning the entire warehouse. If the catalog is wrong (a box contains fictions when it's actually non-fiction), the workers might miss books or scan irrelevant ones, wasting time and money. Athena's power is that it can query any book in any format (CSV, JSON, Parquet), as long as the catalog describes how to interpret it, and it never alters the original books.
 
 

CloudFront/_CloudFront.md

@@ -10,7 +10,7 @@
 - [[_CloudFront|CloudFront]] can stream [[Videos On Demand]] using [[ISS Microsoft Smooth Streaming]]
 
 ### Core components
-**Origin**: Location where all original files are located. Examples include: S3, EC2, ELB, Route53.
+**Origin**: Location where all original files are located. Examples include: [[_S3|S3]], EC2, ELB, Route53.
 **Edge Locations**: Compute located strategically close to end users.
 **Regional Caches**: Compute located in board geographical locations to speed up requests for edge locations.
 **Distribution**: A collection of Edge locations and Regional Cache that defines how cached content should behave.
@@ -76,7 +76,7 @@ The more people hit the cache, the better the application performance will be.
 ### Cache Policy
 A **Cache Policy** determines the **Cache Key**.
 
-AWS has managed **Cache Policies** for use:
+[[AWS]] has managed **Cache Policies** for use:
 - `Amplify`
 - `CachingDisabled`
 - `CachingOptimized`
@@ -117,7 +117,7 @@ Happens when there is a cache miss and CloudFront must reach out to Origin to re
 
 ### Response Header Policy
 Allows you to modify the HTTP Headers in the response that viewers will see.
-AWS has managed policies for you to use and you can make your own also.
+[[AWS]] has managed policies for you to use and you can make your own also.
 
 ⚠️ If you are dealing with CORS, you will be setting things here, as this will mess with them.
 
@@ -126,11 +126,11 @@ AWS has managed policies for you to use and you can make your own also.
 Lots of drawbacks. Not available anymore.
 
 ## Origin Access Control
-Same as Origin Access Identity, makes sure that an S3 bucket is only accessible through **CloudFront** and not the internet.
+Same as Origin Access Identity, makes sure that an [[_S3|S3]] bucket is only accessible through **CloudFront** and not the internet.
 
 Overview:
 * Enhanced sec.
-* Comprehensive HTTP support.
-* Supports uploading and downloading encrypted S3 objects with SSE-KMS.
-* Supports accessing S3 in all AWS Regions.
+* Comprehensive [[HTTP]] support.
+* Supports uploading and downloading encrypted [[_S3|S3]] objects with SSE-KMS.
+* Supports accessing [[_S3|S3]] in all [[AWS]] Regions.
 

CodeBuild/_CodeBuild.md

@@ -15,7 +15,7 @@
 4. Push into a bucket, or any other AWS SDK action (I think?)
 
 ## Build Environments
-The Docker images that run the CodeBuild, can be managed by AWS or you. If you need specific software, you need to make an image and upload it to ECR and reference it in the pipeline.
+The Docker images that run the CodeBuild, can be managed by [[AWS]] or you. If you need specific software, you need to make an image and upload it to ECR and reference it in the pipeline.
 
 ## `buildspec.yml`
 - Provides the build instructions.

CodeCommit/_CodeCommit.md

@@ -1,5 +1,5 @@
 # CodeCommit
-A fully-managed source control service that hosts secure Git-based repositories. (GitHub for AWS)
+A fully-managed source control service that hosts secure Git-based repositories. (GitHub for [[AWS]])
 
 ## Special features
 - In scope with many compliance programs (HIPPA).
@@ -7,5 +7,5 @@ A fully-managed source control service that hosts secure Git-based repositories.
 - Can handle repositories with large numbers of files or branches, large file sizes and lengthy revision histories.
 - No limit on the size of your repositories or on the file types you can store.
 - Keeps your repositories close to your production resources in AWS Cloud, which helps to increase the speed and frequency of your development life-cycle.
-- Uses IAM to control which AWS users have access to which repositories.
+- Uses IAM to control which [[AWS]] users have access to which repositories.
 

CodeDeploy/_CodeDeploy.md

@@ -1,8 +1,8 @@
 # CodeDeploy
 - A fully managed deploy service in the cloud.
-- Can deploy EC2, On-Prem, Lambda, or ECS.
+- Can deploy EC2, On-Prem, [[_Lambda|Lambda]], or ECS.
 - Rapidly release new features.
-- Update AWS Lambda function versions.
+- Update AWS [[_Lambda|Lambda]] function versions.
 - Avoid downtime during application deployments.
 - Integrates with existing CI/CD tools eg. Jenkins, [[_CodePipeline|CodePipeline]].
 - Integrates with existing management tools eg. Puppet, Chef, Ansible.

ELB/_ELB.md

@@ -1,5 +1,5 @@
 # Elastic Load Balancer
-An ELB is a general term for multiple types of "load balancer" in AWS. 
+An ELB is a general term for multiple types of "load balancer" in [[AWS]]. 
 
 Examples include:
 - [[_ALB|Application Load Balancer]]

Lambda/_Lambda.md

@@ -1,3 +1,4 @@
 # Lambda
-Placeholder.
+#Placeholder
+A Docker container or a runner that runs code for you. At a high level, it can run code behind an [[API Gateway|API Gateway]], interact with basically all [[AWS]] Resources (most commonly [[_S3|S3]], [[_DynamoDB|DynamoDB]], other [[_Lambda|Lambdas]]). 
 

Route 53/Use Cases.md

@@ -1,10 +1,10 @@
 # [[_Route53|Route 53]] Use Cases
-Use Route 53 to get your custom domains to point at your AWS Resources. 
+Use Route 53 to get your custom domains to point at your [[AWS]] Resources. 
 
 ![route_53_routing_example.png](./route_53_routing_example.png)
 1. Incoming internet traffic.
 2. Route traffic to our web backed by [[_ALB|ALB]].
 3. Route traffic to an instance we use to tweak our AMI.
-4. Route traffic to [[_API Gateway|API Gateway]], which powers our API.
+4. Route traffic to [[_API Gateway|API Gateway]], which powers our [[API]].
 5. Route traffic to [[_CloudFront|CloudFront]] which serves our [[_S3|S3]] static hosted website.
 6. Route traffic to an Elastic IP (EIP), which is a static IP that hosts a game server.

Route 53/_Route53.md

@@ -1,12 +1,12 @@
 # Route 53
-A DNS with AWS Services.
+A DNS with [[AWS]] Services.
 
 You can:
-- Register and manage domains
-- Create various records sets on a domain
-- Implement compex traffic flows (Blue/Green[^1], failovers)
+- Register and manage domains.
+- Create various records sets on a domain.
+- Implement complex traffic flows (Blue/Green[^1], failovers).
 - Continuously monitor records via health checks.
-- Resolve VPC's outside of AWS.
+- Resolve [[_VPC|VPC]]'s outside of [[AWS]].
 
 [^1]: See [[Deployments|Deployments]].
 

VPC/_VPC.md

@@ -1,4 +1,4 @@
 # VPC
 Virtual Private Connection. 
 
-A private link between 2 places. It can be used as a way to connect 2 different AWS accounts 
+A private link between 2 places. It can be used as a way to connect 2 different [[AWS]] accounts via a link that only these two accounts can use. Consider this a [[VPN]] between two places that is managed by [[AWS]].

X-Ray/_X-Ray.md

@@ -1,5 +1,5 @@
 # X-Ray
-AWS [[_X-Ray|X-Ray]] is a AWS Managed service for diagnosing issues (performance and failures) in a microservice architecture. The main idea is that you pass headers in your calls, AWS picks up on those headers and looks at the propagation of the requests across bits of AWS.
+[[_X-Ray|AWS X-Ray]] is a [[AWS]] Managed service for diagnosing issues (performance and failures) in a microservice architecture. The main idea is that you pass headers in your calls, [[AWS]] picks up on those headers and looks at the propagation of the requests across bits of [[AWS]].
 
 It's a distributed tracing system. 
 
@@ -17,7 +17,7 @@ flowchart LR
 
 ## X-Ray SDK
 - The SDK provides **interceptors** to trace HTTP requests
-- **Client handlers** to **instrument** AWS SDK clients that your application uses to call other AWS Services
+- **Client handlers** to **instrument** AWS SDK clients that your application uses to call other [[AWS]] Services
 - A HTTP Client to use to instrument calls to other internal and external HTTP web services
 
 ## X-Ray Instrumentation
@@ -38,7 +38,7 @@ Comes with [[_Elastic BeanStalk]] and [[_Lambda]] by default.
 
 * **Subsegments**:
     * More granular timing information.
-    * Can contain calls to other AWS services
+    * Can contain calls to other [[AWS]] services.
 
 * **Service Graph**:
     * Just the UI graph in the Console.

_Concepts/Deployments.md

@@ -1,4 +1,4 @@
-# AWS Deployments
+# [[AWS]] Deployments
 
 [[_CodeDeploy|CodeDeploy]]
 [[_Elastic BeanStalk|_Elastic BeanStalk]]
@@ -9,7 +9,7 @@
 |  `CodeDeploy` |  Blue/Green | Higher Cost |  Make a new set of instances, install the latest version, start the latest version and then validate them. Once validated, they replace and existing instance in the ELB. The old instances can be terminated or kept running. | EC2 / On-Prem, Lambda & ECS.  |
 |  `ElasticBeanstalk` |  All at Once | Downtime |  Default policy. Takes everything out of service. Recreates the instances and boots them again. Fastest deployment for EB. | EB |
 |  `ElasticBeanstalk` |  Rolling | Lowered Capacity |  Slowly switch out instances over time. Safer than **All at Once**.  | EB |
-|  `ElasticBeanstalk` |  Rolling with Aditional Batches | Higher Cost |  You spin up an extra batch. Then you switch out the old instances over time until one is left, which you discard. | EB |
+|  `ElasticBeanstalk` |  Rolling with Additional Batches | Higher Cost |  You spin up an extra batch. Then you switch out the old instances over time until one is left, which you discard. | EB |
 |  `ElasticBeanstalk` |  Immutable | Higher Cost |  You spin up an entire extra Auto Scailing Group, then once ready, point the ELB to the new ASG. The safest way to deploy applications because the old instances remain. | EB |
 |  `ElasticBeanstalk` |  Blue/Green | Higher Cost |  You spin up an entire extra ELB, then switch out the URLs. | EB |
 |  `ElasticBeanstalk` |  Traffic Shifting | Higher Cost |  You spin up and extra ELB, the split the traffic between the two, until you are satisfied your application works. | EB |

_Concepts/Glossary/AWS.md

@@ -0,0 +1,2 @@
+# [[AWS]]
+Amazon Web Services. Plain and simple.

_Concepts/Glossary/VPN.md

@@ -0,0 +1,2 @@
+# VPN
+Virtual Private Network. Secures connections between two networks.