From 4fc5812504b208f55dd883785fd13021c95ae102 Mon Sep 17 00:00:00 2001 From: Michele Cereda Date: Sat, 30 Mar 2024 18:54:35 +0100 Subject: [PATCH] chore(kb): improve article readibility --- knowledge base/cloud computing/aws/README.md | 25 ++++++++++++++++++++ knowledge base/cloud computing/oci/README.md | 16 +++++++------ 2 files changed, 34 insertions(+), 7 deletions(-) diff --git a/knowledge base/cloud computing/aws/README.md b/knowledge base/cloud computing/aws/README.md index bbf691c..0200856 100644 --- a/knowledge base/cloud computing/aws/README.md +++ b/knowledge base/cloud computing/aws/README.md @@ -1,5 +1,6 @@ # Amazon Web Services +1. [Networking](#networking) 1. [Services](#services) 1. [CloudWatch](#cloudwatch) 1. [Resource constraints](#resource-constraints) @@ -7,6 +8,25 @@ 1. [Further readings](#further-readings) 1. [Sources](#sources) +## Networking + +VPCs define isolated virtual networking environments.
+AWS accounts include one default VPC for each AWS Region. These allow for immediate launch and connection to EC2 +instances. + +Subnets are ranges of IP addresses in VPCs.
+Each subnet resides in a single Availability Zone.
+_Public_ subnets have a direct route to an Internet gateway. Resources in public subnets **can** access the public +Internet.
+_Private_ subnets do **not** have a direct route to an Internet gateway. Resources in private subnets **require** a NAT +device to access the public internet. + +Gateways connect VPCs to other networks.
+[_Internet gateways_][connect to the internet using an internet gateway] connect VPCs to the Internet.
+[_NAT gateways_][nat gateways] allow resources in private subnets to connect to the Internet, other VPCs, or on-premises +networks. They can communicate with services outside the VPC, but cannot receive unsolicited connection requests.
+[_VPC endpoints_][access aws services through aws privatelink] connect VPCs to AWS services privately, without the need of Internet gateways or NAT devices. + ## Services | Service | Description | @@ -67,6 +87,7 @@ From [Using service-linked roles]: - [Constraints for tags][constraints tag] - [What is CloudWatch] +- [What is Amazon VPC?] - [Introduction to AWS IAM AssumeRole] - [AWS JSON policy elements: Principal] @@ -81,11 +102,15 @@ From [Using service-linked roles]: [ec2]: ec2.md +[access aws services through aws privatelink]: https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html [aws json policy elements: principal]: https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html [best practices for tagging aws resources]: https://docs.aws.amazon.com/whitepapers/latest/tagging-best-practices/tagging-best-practices.html +[connect to the internet using an internet gateway]: https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html [constraints tag]: https://docs.aws.amazon.com/directoryservice/latest/devguide/API_Tag.html +[nat gateways]: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html [services that publish cloudwatch metrics]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/aws-services-cloudwatch-metrics.html [using service-linked roles]: https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html +[what is amazon vpc?]: https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html [what is cloudwatch]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html diff --git a/knowledge base/cloud computing/oci/README.md b/knowledge base/cloud computing/oci/README.md index 0d60d54..a78b964 100644 --- a/knowledge base/cloud computing/oci/README.md +++ b/knowledge base/cloud computing/oci/README.md @@ -7,17 +7,21 @@ 1. [Networking](#networking) 1. [Access to the Internet](#access-to-the-internet) 1. [Further readings](#further-readings) -1. [Sources](#sources) + 1. [Sources](#sources) ## Concepts ### Compartments -Compartments are tenancy-wide and extend across regions. They can also be nested to create hierarchies up to 6 levels deep. +Compartments are tenancy-wide and extend across regions.
+They can be nested to create hierarchies up to 6 levels deep. -After creating a compartment, you need to write at least one policy for it; until then, no one can access it except administrators or users who have permissions set at the tenancy level. When creating sub-compartments, they inherit access permissions from compartments higher up their hierarchy. +After creating a compartment, one needs to write at least one (access) policy for it; until then, no one can access it +but administrators or users with permissions at the _tenancy_ level.
+When creating sub-compartments, users inherit access permissions from compartments higher up their hierarchy. -Before deleting a compartment, all its resources must have been moved, deleted or terminated, including any policies attached to the compartment itself. +Before deleting a compartment, all resources in it **must** have been moved, deleted or terminated.
+This includes **any policies** attached to the compartment itself. ### Networking @@ -35,9 +39,7 @@ Before deleting a compartment, all its resources must have been moved, deleted o - [Compute images] - [Connect to private compute instances using OCI Bastion Service] -## Sources - -All the references in the [further readings] section, plus the following: +### Sources - [Required keys and OCIDs]