Improve AWS Roadmap (#7401)

* SES

* S3

* Route 53

* Cloudwatch

* Cloudfront

src/data/roadmaps/aws/content/105-s3/100-buckets-objects.md

@@ -1,3 +1,7 @@
 # Buckets / Objects
 
 In AWS S3, a "bucket" is a container for data. It is used to store objects. The objects include files or, more technically, any type of data that can be stored in the form of files. In terms of hierarchy, buckets are at the top level in AWS S3. Inside these buckets, you can store any number of objects. An object consists of a file and optionally any metadata that describes that file. It's important to note that you can also store folders within these buckets and inside these folders, you can again store objects. Object keys are unique within a bucket and they help in identifying and retrieving the object.
+
+Visit the following resources to learn more:
+
+- [@official@Bucket / Object](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingBucket.html)

src/data/roadmaps/aws/content/105-s3/101-lifecycle.md

@@ -1,3 +1,7 @@
 # Bucket / Object Lifecycle
 
 AWS S3 Lifecycle is a feature within the AWS S3 resources that allows users to manage their objects so that they are automatically transferred to different storage classes or expire at the end of their lifetimes. It facilitates transitioning objects between different storage classes at set times or according to specified conditions, and can also automate the cleanup of expired objects to help reduce storage consumed by obsolete data. A lifecycle can be applied to a bucket or a subset of objects. Note that each transition or expiration activity is a separate action within the lifecycle.
+
+Visit the following resources to learn more:
+
+- [@official@Bucket / Object Lifecycle](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)

src/data/roadmaps/aws/content/105-s3/102-storage-types/100-standard.md

@@ -1,3 +1,7 @@
 # Standard
 
 Amazon S3 Standard storage is designed for general-purpose storage of frequently accessed data. It provides low latency and high throughput, making it suitable for a wide variety of use cases, including cloud applications, dynamic websites, content distribution, mobile and gaming applications, and big data analytics. S3 Standard offers high durability, availability, and performance object storage for both small and large objects. You have immediate access to your data and can retrieve it at any time, making it a versatile choice for many different AWS workloads.
+
+Visit the following resources to learn more:
+
+- [@official@AWS S3 Standard](https://aws.amazon.com/s3/pricing/)

src/data/roadmaps/aws/content/105-s3/102-storage-types/101-s3-ia.md

@@ -1,3 +1,7 @@
 # S3-IA
 
 Amazon S3 Infrequent Access (S3 IA) is a storage class in Amazon S3 designed for data that is accessed less frequently, but requires rapid access when needed. S3 IA offers the high durability, high throughput, and low latency of Amazon S3 Standard, with a lower cost per GB for storage and a per GB retrieval fee. This makes S3 IA suitable for long-term storage, backups, and as a data store for disaster recovery files.
+
+Visit the following resources to learn more:
+
+- [@official@AWS S3-IA](https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html)

src/data/roadmaps/aws/content/105-s3/102-storage-types/102-gladier.md

@@ -1,3 +1,7 @@
 # Glacier
 
 AWS Glacier is a secure, durable, and extremely low-cost storage service for data archiving and long-term backup. It is designed to reliably store data for as long as you need. Its main features are optimized for infrequently accessed data where retrieval time of minutes is acceptable. AWS Glacier supports the archiving of data that is not needed in real-time but might be required for future reference or are legally required to be maintained. AWS Glacier is used when there is no immediate need for data and substantial retrieval time is acceptable, due to its low storage cost.
+
+Visit the following resources to learn more:
+
+- [@official@AWS Glacier](https://aws.amazon.com/s3/storage-classes/glacier/)

src/data/roadmaps/aws/content/105-s3/102-storage-types/index.md

@@ -1,3 +1,7 @@
 # Storage Types
 
 Amazon S3 provides three storage classes: S3 Standard, S3 Intelligent-Tiering, and S3 Glacier. `S3 Standard` is designed for frequently accessed data. It delivers low latency and high throughput. `S3 Intelligent-Tiering` is automated storage class that optimizes costs. It moves objects between two access tiers (frequent and infrequent access) based on changing access patterns. `S3 Glacier` is for long-term backup and archives. It has two retrieval modes: Expedited (for quick access) and Bulk (for largest and less time-sensitive retrievals).
+
+Visit the following resources to learn more:
+
+- [@official@Storage Types](https://aws.amazon.com/s3/storage-classes/)

src/data/roadmaps/aws/content/105-s3/index.md

@@ -1,3 +1,7 @@
 # S3
 
 Amazon S3 (Simple Storage Service) is an object storage service offered by Amazon Web Services (AWS). It provides scalable, secure and durable storage on the internet. Designed for storing and retrieving any amount of data from anywhere on the web, it is a key tool for many companies in the field of data storage, including mobile applications, websites, backup and restore, archive, enterprise applications, IoT devices, and big data analytics.
+
+Visit the following resources to learn more:
+
+- [@official@S3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/Welcome.html)

src/data/roadmaps/aws/content/106-ses/100-sandbox-limits.md

@@ -1,3 +1,7 @@
 # Sandbox / Sending Limits
 
 In AWS SES, when your account is in the sandbox (default mode for all new accounts), you can only send emails to verified email addresses and the maximum send rate is 1 email per second. The maximum sending quota is 200 messages per 24-hour period. To move out of this sandbox environment and increase your sending limits, you will need to request a sending limit increase. This is achieved by submitting an SES Sending Limit Increase case in the AWS Support Center. For more details, one can refer to the AWS SES documentation.
+
+Visit the following resources to learn more:
+
+- [@official@Sandbox / Sending Limits](https://docs.aws.amazon.com/ses/latest/dg/manage-sending-quotas.html)

src/data/roadmaps/aws/content/106-ses/101-identity-verification.md

@@ -1,3 +1,7 @@
 # Identity Verification
 
 Amazon Simple Email Service (SES) requires users to verify their identities to ensure they own the email addresses or domains they plan to use as 'From', 'Source', 'Sender', or 'Return-Path' addresses. The verification process prevents unauthorized use of identities. There are two types of identities to verify, email address, and domain. Verifying an email address allows you to send emails from that address. If you verify a domain, you can send emails from any address on that domain. Moreover, while sending an email, the 'From' or 'Return-Path' address must be a verified email or domain.
+
+Visit the following resources to learn more:
+
+- [@official@Identity Verification](https://docs.aws.amazon.com/ses/latest/dg/Welcome.html)

src/data/roadmaps/aws/content/106-ses/102-dkim-setup.md

@@ -1,3 +1,8 @@
 # DKIM Setup
 
 DKIM (DomainKeys Identified Mail) is a standard that prevents email spoofing. It allows an organization to take responsibility for transmitting a message in a way that can be verified by mailbox providers. This verification is made possible through cryptographic authentication. In Amazon SES, you can setup DKIM by adding a set of three CNAME records to the DNS configuration of your sending domain. Each record maps a fictitious subdomain of your sending domain to a domain maintained by Amazon SES. After you add these records and they propagate through the internet's DNS infrastructure, you can start sending authenticated email from your domain.
+
+Visit the following resources to learn more:
+
+- [@official@DKIM](https://dkim.org/)
+- [@article@DKIM - Cloudflare](https://www.cloudflare.com/learning/email-security/dmarc-dkim-spf/)

src/data/roadmaps/aws/content/106-ses/103-feedback-handling.md

@@ -1,3 +1,7 @@
 # Feedback Handling
 
 AWS Simple Email Service (SES) provides a mechanism for handling bounces, complaints, and delivery notifications. This mechanism is called feedback handling. Bounces occur when an email can't be delivered to a recipient. Complaints happen when a recipient marks an email as spam. Delivery notifications are sent when Amazon SES successfully delivers an email to a recipient's mail server. AWS SES enables you to receive these feedback notifications by email, relayed to an Amazon SNS topic, or through Amazon CloudWatch. The process of deciding on what action to take when your emails bounce or are marked as spam is called feedback handling. AWS SES automatically handles all feedback loop (FBL) complaints for you, but when it comes to bounces, you are given the flexibility to choose how you want your system to respond.
+
+Visit the following resources to learn more:
+
+- [@official@Feedbacks](https://aws.amazon.com/ses/faqs)

src/data/roadmaps/aws/content/106-ses/104-configuration-sets.md

@@ -1,3 +1,7 @@
 # Configuration Sets
 
 Configuration Sets in SES (Simple Email Service) of AWS (Amazon Web Services) allow to publish email sending events. These sets are used to group together similar rules that you can apply to emails you send using AWS SES. You can apply a configuration set to an email by including it in the headers of the email. It can be used to specify the dedicated sending IP pools, configure the message delivery parameters, and to enable open and click tracking. AWS SES sends information about each email sent with the set to CloudWatch and Kinesis Firehose which can be later utilized for further analysis or to manage your customer interactions more effectively.
+
+Visit the following resources to learn more:
+
+- [@official@SES](https://docs.aws.amazon.com/ses/latest/dg/using-configuration-sets.html)

src/data/roadmaps/aws/content/106-ses/105-sender-reputation.md

@@ -1,3 +1,7 @@
 # Sender Reputation
 
 Sender reputation in Amazon Web Services (AWS) Simple Email Service (SES) is essentially a measure of your sending practices and how they align with the expectations of ISPs and email recipients. This reputation is determined by factors such as your email bounce rate, complaints, content quality, email volume, consistency of email sending, etc. Maintaining a good sender reputation is crucial as it impacts your email deliverability rate - i.e., whether your emails land in recipients' inbox or spam folder. AWS SES encourages good sending practices to help sustain a positive sender reputation.
+
+Visit the following resources to learn more:
+
+- [@official@Sender Reputation](https://aws.amazon.com/blogs/messaging-and-targeting/the-four-pillars-of-email-reputation/)

src/data/roadmaps/aws/content/106-ses/106-dedicated-ip.md

@@ -1,3 +1,7 @@
 # Dedicated IP
 
 "Dedicated IP" in AWS SES (Simple Email Service) refers to a unique IP address that can be used exclusively by a single AWS SES customer for sending emails. When you choose to use a dedicated IP, you get full control over the reputation of that IP address, which is beneficial when sending large volume of emails. AWS can also pool multiple dedicated IPs enabling high volume senders to spread their sending across multiple IPs to maintain their reputation. It is particularly useful for companies that must comply with strict email policies or send significantly large volumes of email.
+
+Visit the following resources to learn more:
+
+- [@official@Dedicated IP](https://docs.aws.amazon.com/ses/latest/dg/dedicated-ip.html)

src/data/roadmaps/aws/content/106-ses/index.md

@@ -1,3 +1,7 @@
 # SES
 
 Amazon Simple Email Service (SES) is a scalable and cost-effective email sending service tailored for marketers, developers, and businesses. It enables users to send notifications, transactional emails, and marketing communications using a highly reliable infrastructure. Amazon SES eliminates the complexity and challenge of building an in-house email solution or licensing, installing, and managing a third-party service. This service can be easily integrated into your existing applications while ensuring your email reaches the recipient's inbox.
+
+Visit the following resources to learn more:
+
+- [@official@SES](https://aws.amazon.com/ses/)

src/data/roadmaps/aws/content/107-route53/100-hosted-zones/100-private.md

@@ -1,3 +1,7 @@
 # Private
 
-Private Hosted Zones in AWS are DNS -name spaces that exist within one or more Amazon VPCs. You can use private hosted zones to route traffic within your VPCs. The domain and subdomains in a private hosted zone are not resolvable over the internet but only in your VPCs. You can use this feature to have internal domain names such as "internal.example.com" resolved to private IP addresses on your Amazon VPC backends.
+Private Hosted Zones in AWS are DNS name spaces that exist within one or more Amazon VPCs. You can use private hosted zones to route traffic within your VPCs. The domain and subdomains in a private hosted zone are not resolvable over the internet but only in your VPCs. You can use this feature to have internal domain names such as "internal.example.com" resolved to private IP addresses on your Amazon VPC backends.
+
+Visit the following resources to learn more:
+
+- [@official@Private Hosted Zones](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html)

src/data/roadmaps/aws/content/107-route53/100-hosted-zones/101-public.md

@@ -1,3 +1,7 @@
 # Public
 
 In AWS, a "Public Hosted Zone" is set up to route traffic on the internet. This means the DNS namespace of this zone is exposed to the public internet. When you create a "Public Hosted Zone", Amazon Route 53 creates a set of four name servers (also known as delegation set) in that zone. Then, you typically set the corresponding domain's NS records to these Route 53 name servers so that the domain's DNS can be managed in the Route 53 console. These zones include Resources Records Sets, where each record set can include records like A (address), CNAME (canonical name), MX (mail exchange), and so on, which define how the traffic is routed.
+
+Visit the following resources to learn more:
+
+- [@official@Public Hosted Zones](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/AboutHZWorkingWith.html)

src/data/roadmaps/aws/content/107-route53/100-hosted-zones/index.md

@@ -1,3 +1,7 @@
 # Hosted Zones
 
 A **Hosted Zone** in AWS Route 53 is essentially a container that holds information about how you want to route traffic on the internet for a specific domain, such as example.com. Each hosted zone is associated with a set of DNS records, which control the flow of traffic for that domain. AWS Route 53 automatically creates a record set that includes a name server (NS) record and a start of authority (SOA) record when you create a hosted zone. These records provide necessary information about your domain to the DNS system, establishing the basis for routing traffic for that domain to the appropriate IP address in your AWS environment.
+
+Visit the following resources to learn more:
+
+- [@official@Hosted Zones](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-working-with.html)

src/data/roadmaps/aws/content/107-route53/101-routing-policies.md

@@ -12,6 +12,10 @@ AWS Route 53 provides different routing policies to fit various needs:
 
 5. **Geo location Routing Policy**: Routes traffic based on the geographic location of your users.
 
-6. **Geoproximity Routing Policy (Traffic Flow Only)**: Route traffic based on the geographic location of your resources and, optionally, shift traffic from resources in one location to resources in another.
+6. **Geo Proximity Routing Policy (Traffic Flow Only)**: Route traffic based on the geographic location of your resources and, optionally, shift traffic from resources in one location to resources in another.
 
-7. **Multivalue Answer Routing Policy**: Used when you want Route 53 to respond to DNS queries with up to eight healthy records selected at random.
+7. **Multi Value Answer Routing Policy**: Used when you want Route 53 to respond to DNS queries with up to eight healthy records selected at random.
+
+Visit the following resources to learn more:
+
+- [@official@Routing Policies](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html)

src/data/roadmaps/aws/content/107-route53/102-health-checks.md

@@ -1,3 +1,7 @@
 # Health checks
 
 Route53 health checks enable you to monitor the health and performance of your applications, network, and servers. You can create custom health checks that verify the status of specific resources, such as a web server or email server. If the health check fails, Route 53 routes traffic away from the unhealthy resources. Health checks run periodically, at intervals that you specify, to help you detect issues before your end-users do. You can configure alarms to notify you when a resource becomes unhealthy, helping you respond rapidly to potential issues. AWS Route 53 Health Checks also integrates with CloudWatch, providing detailed metrics and graphs for analyzed data.
+
+Visit the following resources to learn more:
+
+- [@official@Route53 Health Checks](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-health-checks.html)

src/data/roadmaps/aws/content/107-route53/index.md

@@ -1,3 +1,7 @@
 # Route53
 
 AWS Route 53 is a scalable and highly available domain name system (DNS) service designed to give developers and businesses an extremely reliable and cost-effective way to route users to Internet applications. This DNS service effectively connects user requests to infrastructure running in Amazon Web Services (AWS) – such as an Amazon EC2 instance, an Amazon Elastic Load Balancer, or an Amazon S3 bucket – and can also be used to route users to infrastructure outside of AWS. Route 53 conceals the complexities of the underlying DNS protocol, offering developers an easy-to-use and cost-effective domain registration service. It features domain transfer capabilities, DNS failover, health checks, and customizable TTLs.
+
+Visit the following resources to learn more:
+
+- [@official@Route53](https://aws.amazon.com/route53/)

src/data/roadmaps/aws/content/108-cloudwatch/101-events.md

@@ -1,3 +1,7 @@
 # Events
 
 AWS CloudWatch Events is a service that provides a streamlined, systematic method to respond to system-wide changes in your AWS environment. This could range from a simple state change, like an EC2 instance being stopped or started, to a more complex series of conditions. You can set an Event Pattern to monitor AWS resources for specific changes or you can schedule cron jobs. The action resulting from the event pattern can be a Lambda function, SNS notification, or auto-scaling policy amongst other options. Essentially, AWS CloudWatch Events helps you automate your AWS services and respond automatically to system events.
+
+Visit the following resources to learn more:
+
+- [@official@Amazon Cloudwatch Events](https://docs.aws.amazon.com/whitepapers/latest/introduction-devops-aws/cloudwatch-events.html)

src/data/roadmaps/aws/content/108-cloudwatch/102-logs.md

@@ -1,3 +1,7 @@
 # Logs
 
 AWS CloudWatch Logs service allows you to monitor, store, and access your log files from Amazon Elastic Compute Cloud (Amazon EC2) instances, AWS CloudTrail, and other sources. It centralizes the logs from all your systems, applications, and AWS services that you use, into a single, highly scalable service. You can then easily view them, search through them, set alarms, and correlate them to other operational data. It also integrates with AWS Lambda, providing the ability to respond quickly to critical operational events.
+
+Visit the following resources to learn more:
+
+- [@official@Amazon Cloudwatch Logs](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/WhatIsCloudWatchLogs.html)

src/data/roadmaps/aws/content/108-cloudwatch/index.md

@@ -1,3 +1,7 @@
 # Cloudwatch
 
 "Amazon CloudWatch" is a monitoring service for AWS resources and applications that you run on Amazon Web Services. You can use Amazon CloudWatch to collect and track metrics, collect and monitor log files, and respond to system-wide performance changes. CloudWatch gives system-wide visibility into resource utilization, application performance, and operational health. It utilizes operational data (logs and metrics) to automatically respond to changes in AWS resources. It allows you to work seamlessly with various AWS services like Amazon EC2, Amazon DynamoDB, Amazon S3, Amazon ECS, AWS Lambda, and many more.
+
+Visit the following resources to learn more:
+
+- [@official@Amazon Cloudwatch](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/WhatIsCloudWatch.html)

src/data/roadmaps/aws/content/109-cloudfront/100-distributions.md

@@ -1,3 +1,7 @@
 # Distributions
 
 In AWS, a CloudFront "distribution" is the globally distributed network system that helps you to accelerate the delivery of your website, API, video content, or other web assets. These distributions are defined by AWS based on the specified configuration settings. It specifies from where CloudFront gets your files that it will distribute, which is primarily your Amazon S3 bucket or an HTTP server. Notably, there are primarily two types of distributions you can create: web distributions, which are typically used for websites, and RTMP distributions, used mainly for media streaming.
+
+Visit the following resources to learn more:
+
+- [@official@Cloudfront Distribution](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-working-with.html)

src/data/roadmaps/aws/content/109-cloudfront/101-policies.md

@@ -1,3 +1,7 @@
 # Policies
 
 Amazon CloudFront works with AWS Identity and Access Management (IAM) and AWS Organizations to provide you with options to implement fine-grained access control over your CloudFront distributions. CloudFront policies allow you to specify the permissions of a resource. You can create a policy to allow an IAM user to create or delete distributions, to allow an AWS account to create a CloudFront origin access identity, or to allow an organization to update the settings for a distribution. You can also use policies to specify which Amazon S3 bucket a CloudFront distribution can access.
+
+Visit the following resources to learn more:
+
+- [@official@Cloudfront IAM](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/security-iam.html)

src/data/roadmaps/aws/content/109-cloudfront/102-invalidations.md

@@ -1,3 +1,7 @@
 # Invalidations
 
 `Invalidations` in AWS CloudFront is a concept where you remove files (objects) from CloudFront cache before it hits the expiration period. AWS CloudFront, like any other CDN, stores copies of your website’s static files in its cache until and unless it reaches its TTL (time to live) duration. But in some situations, you might want to remove or replace these files. For instance, these could be changes in CSS or JS files. This is where Invalidations come to the scene. With this, you can immediately remove objects or files from edge locations.
+
+Visit the following resources to learn more:
+
+- [@official@Invalidations Cloudfront](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html)

src/data/roadmaps/aws/content/109-cloudfront/index.md

@@ -1,3 +1,7 @@
 # Cloudfront
 
 Amazon CloudFront is a fast content delivery network (CDN) service that securely delivers data, videos, applications, and APIs to customers globally with low latency, high transfer speeds all within a developer-friendly environment. It integrates with AWS services including AWS Shield for DDoS mitigation, Amazon S3, Elastic Load Balancing or Amazon EC2 as origins for your applications, and Lambda@Edge to run custom code closer to customers’ users and to customize the user experience. Essentially, it accelerates the distribution of your static and dynamic web content, such as .html, .css, .php, image, and media files, to end users.
+
+Visit the following resources to learn more:
+
+- [@official@Amazon Cloudfront](https://aws.amazon.com/cloudfront/)