mirror of
https://gitea.com/mcereda/oam.git
synced 2026-02-22 19:44:25 +00:00
fix(kb): align to new link format
This commit is contained in:
@@ -1142,7 +1142,7 @@ If one can, prefer just build the image from an EC2 instance.
|
||||
|
||||
### Sources
|
||||
|
||||
- [Constraints for tags][constraints tag]
|
||||
- [Constraints for tags][constraints / tag]
|
||||
- [What is Amazon VPC?]
|
||||
- [Subnets for your VPC]
|
||||
- [What is AWS Config?]
|
||||
@@ -1188,6 +1188,7 @@ If one can, prefer just build the image from an EC2 instance.
|
||||
[config]: #config
|
||||
[detective]: #detective
|
||||
[direct connect]: #direct-connect
|
||||
[ElastiCache]: #elasticache
|
||||
[ELB]: #load-balancing
|
||||
[enterprise discount program]: #enterprise-discount-program
|
||||
[eventbridge]: #eventbridge
|
||||
@@ -1237,7 +1238,7 @@ If one can, prefer just build the image from an EC2 instance.
|
||||
[boto3 resources]: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/resources.html
|
||||
[boto3 sessions]: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/session.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
|
||||
[constraints / tag]: https://docs.aws.amazon.com/directoryservice/latest/devguide/API_Tag.html
|
||||
[creating organization policies with aws organizations]: https://docs.aws.amazon.com/organizations/latest/userguide/orgs_policies_create.html
|
||||
[elastic ip addresses]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html
|
||||
[enable or disable aws regions in your account]: https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html
|
||||
|
||||
@@ -425,7 +425,7 @@ deployments.
|
||||
|
||||
## Capacity providers
|
||||
|
||||
Refer [Capacity providers][upstream capacity providers].
|
||||
Refer [Capacity providers][documentation / capacity providers].
|
||||
|
||||
Clusters can contain a mix of tasks that are hosted on Fargate, Amazon EC2 instances, or external instances.<br/>
|
||||
Tasks can run on Fargate or EC2 infrastructure, as defined by their [launch type] or a capacity provider strategy.<br/>
|
||||
@@ -2416,6 +2416,7 @@ ECS will eventually stop the Task, then launch a replacement to maintain the des
|
||||
[AWS Fargate Pricing]: https://aws.amazon.com/fargate/pricing/
|
||||
[AWS Fargate Spot Now Generally Available]: https://aws.amazon.com/blogs/aws/aws-fargate-spot-now-generally-available/
|
||||
[Centralized Container Logging with Fluent Bit]: https://aws.amazon.com/blogs/opensource/centralized-container-logging-fluent-bit/
|
||||
[Documentation / capacity providers]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html#capacity-providers
|
||||
[ecs execute-command proposal]: https://github.com/aws/containers-roadmap/issues/1050
|
||||
[Effectively Using Spot Instances in AWS ECS for Production Workloads]: https://medium.com/@ankur.ecb/effectively-using-spot-instances-in-aws-ecs-for-production-workloads-d46985d0ae2d
|
||||
[EventBridge Scheduler]: https://docs.aws.amazon.com/scheduler/latest/UserGuide/what-is-scheduler.html
|
||||
@@ -2437,7 +2438,6 @@ ECS will eventually stop the Task, then launch a replacement to maintain the des
|
||||
[troubleshoot amazon ecs deployment issues]: https://docs.aws.amazon.com/codedeploy/latest/userguide/troubleshooting-ecs.html
|
||||
[troubleshoot amazon ecs task definition invalid cpu or memory errors]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-cpu-memory-error.html
|
||||
[Under the hood: FireLens for Amazon ECS Tasks]: https://aws.amazon.com/blogs/containers/under-the-hood-firelens-for-amazon-ecs-tasks/
|
||||
[upstream capacity providers]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clusters.html#capacity-providers
|
||||
[use amazon ebs volumes with amazon ecs]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ebs-volumes.html
|
||||
[use amazon efs volumes with amazon ecs]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/efs-volumes.html
|
||||
[use bind mounts with amazon ecs]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/bind-mounts.html
|
||||
|
||||
@@ -165,7 +165,7 @@ POST _cold/migration/my-index/_cancel
|
||||
|
||||
## Index state management plugin
|
||||
|
||||
Refer [OpenSearch's Index State Management plugin][opensearch index state management] and
|
||||
Refer [OpenSearch's Index State Management plugin][opensearch / index state management] and
|
||||
[Index State Management in Amazon OpenSearch Service].
|
||||
|
||||
Compared to [OpenSearch] and [ElasticSearch], ISM for Amazon's managed OpenSearch service has several differences:
|
||||
@@ -206,7 +206,7 @@ Compared to [OpenSearch] and [ElasticSearch], ISM for Amazon's managed OpenSearc
|
||||
|
||||
## Snapshots
|
||||
|
||||
Refer [Snapshots][opensearch snapshots] and [Creating index snapshots in Amazon OpenSearch Service].
|
||||
Refer [Snapshots][opensearch / snapshots] and [Creating index snapshots in Amazon OpenSearch Service].
|
||||
|
||||
AWS-managed OpenSearch Service snapshots come in the following forms:
|
||||
|
||||
@@ -446,8 +446,8 @@ can manage.
|
||||
[Hot-warm architecture]: ../../opensearch.md#hot-warm-architecture
|
||||
[ElasticSearch]: ../../elasticsearch.md
|
||||
[OpenSearch]: ../../opensearch.md
|
||||
[OpenSearch index state management]: ../../opensearch.md#index-state-management-plugin
|
||||
[OpenSearch snapshots]: ../../opensearch.md#snapshots
|
||||
[OpenSearch / index state management]: ../../opensearch.md#index-state-management-plugin
|
||||
[OpenSearch / snapshots]: ../../opensearch.md#snapshots
|
||||
[S3]: s3.md
|
||||
|
||||
<!-- Files -->
|
||||
|
||||
@@ -198,7 +198,7 @@ Objects in need to be moved to a higher storage class need to be **_recreated_**
|
||||
they will take new metadata.
|
||||
|
||||
Other constraints apply, e.g., objects smaller than 128KiB are not usually transitioned in tier.<br/>
|
||||
See [General considerations for transitions][lifecycle general considerations for transitions].
|
||||
See [General considerations for transitions][lifecycle / general considerations for transitions].
|
||||
|
||||
When multiple rules are applied through Lifecycle configurations, objects can become eligible for multiple Lifecycle
|
||||
actions. In such cases:
|
||||
@@ -214,7 +214,7 @@ actions. In such cases:
|
||||
> Expect a delay of a few minutes before any change in configuration starts taking effect. This includes configuration
|
||||
> deletions.
|
||||
|
||||
Examples: [1][lifecycle configuration examples], [2][s3 lifecycle rules examples]
|
||||
Examples: [1][lifecycle / configuration examples], [2][s3 lifecycle rules examples]
|
||||
|
||||
## Cost-saving measures
|
||||
|
||||
@@ -230,7 +230,7 @@ Examples: [1][lifecycle configuration examples], [2][s3 lifecycle rules example
|
||||
## Further readings
|
||||
|
||||
- [Amazon Web Services]
|
||||
- [Configure notification for lifecycle rules][lifecycle configure notification]
|
||||
- [Configure notification for lifecycle rules][lifecycle / configure notification]
|
||||
- AWS' [CLI]
|
||||
- [Expiring Amazon S3 objects based on last accessed date to decrease costs]
|
||||
- [Understanding and managing Amazon S3 storage classes]
|
||||
@@ -245,8 +245,8 @@ Examples: [1][lifecycle configuration examples], [2][s3 lifecycle rules example
|
||||
### Sources
|
||||
|
||||
- [Amazon S3 Storage Classes]
|
||||
- [General considerations for transitions][lifecycle general considerations for transitions]
|
||||
- [Lifecycle configuration examples][lifecycle configuration examples]
|
||||
- [General considerations for transitions][lifecycle / general considerations for transitions]
|
||||
- [Lifecycle configuration examples][lifecycle / configuration examples]
|
||||
- [CLI subcommand reference]
|
||||
- [Find out the size of your Amazon S3 buckets]
|
||||
- [How S3 Intelligent-Tiering works]
|
||||
@@ -277,9 +277,9 @@ Examples: [1][lifecycle configuration examples], [2][s3 lifecycle rules example
|
||||
[expiring amazon s3 objects based on last accessed date to decrease costs]: https://aws.amazon.com/blogs/architecture/expiring-amazon-s3-objects-based-on-last-accessed-date-to-decrease-costs/
|
||||
[find out the size of your amazon s3 buckets]: https://aws.amazon.com/blogs/storage/find-out-the-size-of-your-amazon-s3-buckets/
|
||||
[how s3 intelligent-tiering works]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/intelligent-tiering-overview.html
|
||||
[lifecycle configuration examples]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html
|
||||
[lifecycle configure notification]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configure-notification.html
|
||||
[lifecycle general considerations for transitions]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html
|
||||
[lifecycle / configuration examples]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html
|
||||
[lifecycle / configure notification]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configure-notification.html
|
||||
[lifecycle / general considerations for transitions]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html
|
||||
[Understanding and managing Amazon S3 storage classes]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html
|
||||
[Understanding your AWS billing and usage reports for Amazon S3]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/aws-usage-report-understand.html
|
||||
[Using S3 Intelligent-Tiering]: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-intelligent-tiering.html
|
||||
|
||||
Reference in New Issue
Block a user