standardize URL format

cfeenstra67 · cfeenstra67 · commit 78f7c15c6fe2 · 2025-07-09T21:42:31.000-04:00
diff --git a/packages/aws/src/components/bucket.ts b/packages/aws/src/components/bucket.ts
@@ -41,16 +41,16 @@
  * ## Related Components
  *
  * Buckets are a foundational component in AWS and integrate with several other components:
- * - [static-site](/components/static-site) - Serves files stored in S3 publicly using Cloudfront as a CDN with support for framework-specific routing.
- * - [s3-firehose](/components/s3-firehose) - Sets up a Kinesis Firehose that can be used to buffer data and write it to S3 in chunks. This can be used to query it efficiently with tools that can read data directly from S3 such as Athena or Apache Spark.
+ * - [static-site](/components/static-site/) - Serves files stored in S3 publicly using Cloudfront as a CDN with support for framework-specific routing.
+ * - [s3-firehose](/components/s3-firehose/) - Sets up a Kinesis Firehose that can be used to buffer data and write it to S3 in chunks. This can be used to query it efficiently with tools that can read data directly from S3 such as Athena or Apache Spark.
  *
  * ## Costs
  *
  * S3 costs are all **usage-based** so you will not be charged if you create a bucket and never use it. S3 costs are broken down by:
  *
  * - **Data Transfer** - This is the component that often makes costs really blow up unless handled carefully. Sending data **to** S3 is always free. However, transferring data **out of** S3 to the internet incurs charges of ~$0.09/GB. If data is transferred from S3 to many clients, this can add up quickly. Consider these cost reduction strategies:
- *   - Use S3 endpoints - The [vpc](/components/vpc) component sets up VPC endpoints by default, so requests to S3 from your VPC will be made internally in AWS's network and will not incur data transfer charges.
- *   - Consider CloudFront - Use the [staticSite](/components/static-site) component or create your own CloudFront distribution to serve files publicly. The first 1TB of data transfer out to the internet from CloudFront is free each month; [see CloudFront pricing for details](https://aws.amazon.com/cloudfront/pricing/).
+ *   - Use S3 endpoints - The [vpc](/components/vpc/) component sets up VPC endpoints by default, so requests to S3 from your VPC will be made internally in AWS's network and will not incur data transfer charges.
+ *   - Consider CloudFront - Use the [staticSite](/components/static-site/) component or create your own CloudFront distribution to serve files publicly. The first 1TB of data transfer out to the internet from CloudFront is free each month; [see CloudFront pricing for details](https://aws.amazon.com/cloudfront/pricing/).
  *
  * - **Data stored** - The storage itself is relatively cheap, ~$0.023/GB/month. If you store 100GB of data in S3 and leave it there, you'll be billed ~$2.30 each month. If you delete the data (including all versions, if versioning is enabled) from S3, you will not be charged for its storage anymore.
  *
diff --git a/packages/aws/src/components/certificate.ts b/packages/aws/src/components/certificate.ts
@@ -28,8 +28,8 @@
  * ## Related Components
  *
  * Certificates work together with other Stackattack components:
- * - [load-balancer](/components/load-balancer) - Uses certificates for HTTPS termination
- * - [static-site](/components/static-site) - Uses certificates for secure CloudFront distributions
+ * - [load-balancer](/components/load-balancer/) - Uses certificates for HTTPS termination
+ * - [static-site](/components/static-site/) - Uses certificates for secure CloudFront distributions
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/cluster.ts b/packages/aws/src/components/cluster.ts
@@ -17,10 +17,10 @@
  *
  * ## Usage
  *
- * After deploying a cluster, you can deploy [services](/components/service) into it to run code in docker containers.
+ * After deploying a cluster, you can deploy [services](/components/service/) into it to run code in docker containers.
  *
  * **SSH Access to EC2 Instances:**
- * _NOTE_: if your instances are within a private subnet (as is likely the case), you need a way to access your instances. If you created your vpc with the [vpc](/components/vpc) component, an EC2 instance connect endpoint is set up automatically.
+ * _NOTE_: if your instances are within a private subnet (as is likely the case), you need a way to access your instances. If you created your vpc with the [vpc](/components/vpc/) component, an EC2 instance connect endpoint is set up automatically.
  *
  * ```bash
  * # Connect to an instance using Instance Connect (no key pairs needed)
@@ -32,9 +32,9 @@
  * ## Related Components
  *
  * Clusters work together with other Stackattack components:
- * - [vpc](/components/vpc) - Provides networking foundation with private/public subnets
- * - [service](/components/service) - Runs containerized applications on the cluster
- * - [load-balancer](/components/load-balancer) - Routes external traffic to services on the cluster
+ * - [vpc](/components/vpc/) - Provides networking foundation with private/public subnets
+ * - [service](/components/service/) - Runs containerized applications on the cluster
+ * - [load-balancer](/components/load-balancer/) - Routes external traffic to services on the cluster
  *
  * ## Costs
  *
@@ -52,7 +52,7 @@
  * - Use spot instances for non-critical workloads (up to 90% savings)
  * - Enable cluster auto-scaling to scale to zero during low usage
  * - Monitor instance utilization and rightsize instance types
- * - Use [service](/components/service) placement strategies to maximize instance utilization
+ * - Use [service](/components/service/) placement strategies to maximize instance utilization
  *
  * See [EC2 Pricing](https://aws.amazon.com/ec2/pricing/) for current rates.
  */
diff --git a/packages/aws/src/components/database.ts b/packages/aws/src/components/database.ts
@@ -61,7 +61,7 @@
  * ## Related Components
  *
  * Databases work together with other Stackattack components:
- * - [vpc](/components/vpc) - Provides secure private networking for database access
+ * - [vpc](/components/vpc/) - Provides secure private networking for database access
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/load-balancer.ts b/packages/aws/src/components/load-balancer.ts
@@ -57,9 +57,9 @@
  * ## Related Components
  *
  * Load balancers work together with other Stackattack components:
- * - [vpc](/components/vpc) - Provides public networking for internet-facing load balancers
- * - [service](/components/service) - Receives traffic routed through load balancers
- * - [certificate](/components/certificate) - Enables HTTPS termination at the load balancer
+ * - [vpc](/components/vpc/) - Provides public networking for internet-facing load balancers
+ * - [service](/components/service/) - Receives traffic routed through load balancers
+ * - [certificate](/components/certificate/) - Enables HTTPS termination at the load balancer
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/redis.ts b/packages/aws/src/components/redis.ts
@@ -47,7 +47,7 @@
  * ## Related Components
  *
  * Redis clusters work together with other Stackattack components:
- * - [vpc](/components/vpc) - Provides secure private networking for Redis access
+ * - [vpc](/components/vpc/) - Provides secure private networking for Redis access
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/s3-firehose.ts b/packages/aws/src/components/s3-firehose.ts
@@ -53,7 +53,7 @@
  * ## Related Components
  *
  * S3 firehoses work together with other Stackattack components:
- * - [bucket](/components/bucket) - Buckets are used to store the data that's written to the firehose.
+ * - [bucket](/components/bucket/) - Buckets are used to store the data that's written to the firehose.
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/service-autoscaling.ts b/packages/aws/src/components/service-autoscaling.ts
@@ -47,7 +47,7 @@
  * ## Related Components
  *
  * Autoscaling work together with other Stackattack components:
- * - [service](/components/service) - The autoscaling component is used to scale services based on Cloudwatch metrics.
+ * - [service](/components/service/) - The autoscaling component is used to scale services based on Cloudwatch metrics.
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/service.ts b/packages/aws/src/components/service.ts
@@ -39,15 +39,15 @@
  * ## Related Components
  *
  * Services work together with other Stackattack components:
- * - [cluster](/components/cluster) - Provides compute capacity for running services
- * - [vpc](/components/vpc) - Provides networking foundation with private/public subnets
- * - [load-balancer](/components/load-balancer) - Routes external traffic to services
+ * - [cluster](/components/cluster/) - Provides compute capacity for running services
+ * - [vpc](/components/vpc/) - Provides networking foundation with private/public subnets
+ * - [load-balancer](/components/load-balancer/) - Routes external traffic to services
  *
  * ## Costs
  *
  * ECS service costs depend on the underlying compute resources and are **usage-based**:
  *
- * - **EC2 instances** - If using EC2 capacity providers, you pay for the underlying EC2 instances (~$0.0116/hour for t3.micro). The [cluster](/components/cluster) component manages auto-scaling groups that can scale to zero when no tasks are running.
+ * - **EC2 instances** - If using EC2 capacity providers, you pay for the underlying EC2 instances (~$0.0116/hour for t3.micro). The [cluster](/components/cluster/) component manages auto-scaling groups that can scale to zero when no tasks are running.
  *
  * - **Fargate** - If using Fargate capacity providers, you pay per vCPU-hour (~$0.04048/vCPU/hour) and per GB-hour (~$0.004445/GB/hour). A 0.5 vCPU, 1GB task running 24/7 costs ~$15/month.
  *
@@ -56,7 +56,7 @@
  * - **CloudWatch Logs** - Log storage is ~$0.50/GB/month. Use the `logRetention` parameter to automatically delete old logs and control costs.
  *
  * Cost optimization strategies:
- * - Use the [cluster](/components/cluster) component's auto-scaling features to scale EC2 instances to zero during low usage
+ * - Use the [cluster](/components/cluster/) component's auto-scaling features to scale EC2 instances to zero during low usage
  * - Set appropriate `logRetention` periods (default: 30 days)
  * - Consider spot instances for non-critical workloads through capacity provider configuration
  *
@@ -345,7 +345,7 @@ export interface ServiceArgs extends TaskDefinitionArgs {
   orderedPlacementStrategies?: pulumi.Input<
     pulumi.Input<aws.types.input.ecs.ServiceOrderedPlacementStrategy>[]
   >;
-  /** Specify an auto-scaling configuration for your service. Cannot be used with `replicas`. See the [serviceAutoScaling](/components/service-autoscaling) component for argument documentation. */
+  /** Specify an auto-scaling configuration for your service. Cannot be used with `replicas`. See the [serviceAutoScaling](/components/service-autoscaling/) component for argument documentation. */
   autoScaling?: Omit<ServiceAutoScalingArgs, "service">;
 }
 
diff --git a/packages/aws/src/components/static-site.ts b/packages/aws/src/components/static-site.ts
@@ -61,8 +61,8 @@
  * ## Related Components
  *
  * Static sites work together with other Stackattack components:
- * - [bucket](/components/bucket) - Stores website files in S3
- * - [certificate](/components/certificate) - Provides SSL certificates for HTTPS domains
+ * - [bucket](/components/bucket/) - Stores website files in S3
+ * - [certificate](/components/certificate/) - Provides SSL certificates for HTTPS domains
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/twingate-connector.ts b/packages/aws/src/components/twingate-connector.ts
@@ -27,9 +27,9 @@
  * ## Related Components
  *
  * Twingate connectors work with other Stackattack components:
- * - [vpc](/components/vpc) - Provides the private network where the connector runs
- * - [cluster](/components/cluster) - Provides compute capacity for the connector service
- * - [service](/components/service) - Base service component that runs the Twingate container
+ * - [vpc](/components/vpc/) - Provides the private network where the connector runs
+ * - [cluster](/components/cluster/) - Provides compute capacity for the connector service
+ * - [service](/components/service/) - Base service component that runs the Twingate container
  *
  * ## Costs
  *
diff --git a/packages/aws/src/components/vpc.ts b/packages/aws/src/components/vpc.ts
@@ -27,17 +27,17 @@
  * One important thing you'll need to determine is how you access private resources within your VPC from your local machine--**by default the only connectivity provided to private resources is SSH access to EC2 instances via [EC2 Instance Connect](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect-linux-inst-eic.html)**.
  *
  * Stackattack provides a few options:
- * - [twingate-connector](/components/twingate-connector) - Deploys a Twingate Connector for Zero Trust access access to your resources via the Twingate client app. This is a good option: it's very easy to set up and relatively cheap.
- * - [vpc](/components/vpn) - This sets up an AWS Client VPN endpoint that you can connect to via any OpenVPN client. This provides a way to provision a VPN for access to private resources without any third-party services. However, **this option is quite expensive**. See the [costs](/components/vpn#costs) for the VPN component for details.
+ * - [twingate-connector](/components/twingate-connector/) - Deploys a Twingate Connector for Zero Trust access access to your resources via the Twingate client app. This is a good option: it's very easy to set up and relatively cheap.
+ * - [vpc](/components/vpn/) - This sets up an AWS Client VPN endpoint that you can connect to via any OpenVPN client. This provides a way to provision a VPN for access to private resources without any third-party services. However, **this option is quite expensive**. See the [costs](/components/vpn#costs) for the VPN component for details.
  *
  * ## Related Components
  *
  * VPCs provide the networking foundation for other Stackattack components:
- * - [cluster](/components/cluster) - Requires VPC networking for ECS instances
- * - [service](/components/service) - Runs in VPC private subnets
- * - [database](/components/database) - Deployed in VPC private subnets for security
- * - [load-balancer](/components/load-balancer) - Uses VPC public subnets for internet access
- * - [redis](/components/redis) - Deployed in VPC private subnets
+ * - [cluster](/components/cluster/) - Requires VPC networking for ECS instances
+ * - [service](/components/service/) - Runs in VPC private subnets
+ * - [database](/components/database/) - Deployed in VPC private subnets for security
+ * - [load-balancer](/components/load-balancer/) - Uses VPC public subnets for internet access
+ * - [redis](/components/redis/) - Deployed in VPC private subnets
  *
  * ## Costs
  *

Original file line number	Diff line number	Diff line change
`@@ -41,16 +41,16 @@`
`41`	`41`	`* ## Related Components`
`42`	`42`	`*`
`43`	`43`	`* Buckets are a foundational component in AWS and integrate with several other components:`
`44`		`- * - [static-site](/components/static-site) - Serves files stored in S3 publicly using Cloudfront as a CDN with support for framework-specific routing.`
`45`		`- * - [s3-firehose](/components/s3-firehose) - Sets up a Kinesis Firehose that can be used to buffer data and write it to S3 in chunks. This can be used to query it efficiently with tools that can read data directly from S3 such as Athena or Apache Spark.`
	`44`	`+ * - [static-site](/components/static-site/) - Serves files stored in S3 publicly using Cloudfront as a CDN with support for framework-specific routing.`
	`45`	`+ * - [s3-firehose](/components/s3-firehose/) - Sets up a Kinesis Firehose that can be used to buffer data and write it to S3 in chunks. This can be used to query it efficiently with tools that can read data directly from S3 such as Athena or Apache Spark.`
`46`	`46`	`*`
`47`	`47`	`* ## Costs`
`48`	`48`	`*`
`49`	`49`	`* S3 costs are all usage-based so you will not be charged if you create a bucket and never use it. S3 costs are broken down by:`
`50`	`50`	`*`
`51`	`51`	`* - Data Transfer - This is the component that often makes costs really blow up unless handled carefully. Sending data to S3 is always free. However, transferring data out of S3 to the internet incurs charges of ~$0.09/GB. If data is transferred from S3 to many clients, this can add up quickly. Consider these cost reduction strategies:`
`52`		`- * - Use S3 endpoints - The [vpc](/components/vpc) component sets up VPC endpoints by default, so requests to S3 from your VPC will be made internally in AWS's network and will not incur data transfer charges.`
`53`		`- * - Consider CloudFront - Use the [staticSite](/components/static-site) component or create your own CloudFront distribution to serve files publicly. The first 1TB of data transfer out to the internet from CloudFront is free each month; [see CloudFront pricing for details](https://aws.amazon.com/cloudfront/pricing/).`
	`52`	`+ * - Use S3 endpoints - The [vpc](/components/vpc/) component sets up VPC endpoints by default, so requests to S3 from your VPC will be made internally in AWS's network and will not incur data transfer charges.`
	`53`	`+ * - Consider CloudFront - Use the [staticSite](/components/static-site/) component or create your own CloudFront distribution to serve files publicly. The first 1TB of data transfer out to the internet from CloudFront is free each month; [see CloudFront pricing for details](https://aws.amazon.com/cloudfront/pricing/).`
`54`	`54`	`*`
`55`	`55`	`* - Data stored - The storage itself is relatively cheap, ~$0.023/GB/month. If you store 100GB of data in S3 and leave it there, you'll be billed ~$2.30 each month. If you delete the data (including all versions, if versioning is enabled) from S3, you will not be charged for its storage anymore.`
`56`	`56`	`*`
Original file line number	Diff line number	Diff line change
`@@ -28,8 +28,8 @@`
`28`	`28`	`* ## Related Components`
`29`	`29`	`*`
`30`	`30`	`* Certificates work together with other Stackattack components:`
`31`		`- * - [load-balancer](/components/load-balancer) - Uses certificates for HTTPS termination`
`32`		`- * - [static-site](/components/static-site) - Uses certificates for secure CloudFront distributions`
	`31`	`+ * - [load-balancer](/components/load-balancer/) - Uses certificates for HTTPS termination`
	`32`	`+ * - [static-site](/components/static-site/) - Uses certificates for secure CloudFront distributions`
`33`	`33`	`*`
`34`	`34`	`* ## Costs`
`35`	`35`	`*`
Original file line number	Diff line number	Diff line change
`@@ -17,10 +17,10 @@`
`17`	`17`	`*`
`18`	`18`	`* ## Usage`
`19`	`19`	`*`
`20`		`- * After deploying a cluster, you can deploy [services](/components/service) into it to run code in docker containers.`
	`20`	`+ * After deploying a cluster, you can deploy [services](/components/service/) into it to run code in docker containers.`
`21`	`21`	`*`
`22`	`22`	`* SSH Access to EC2 Instances:`
`23`		`- * _NOTE_: if your instances are within a private subnet (as is likely the case), you need a way to access your instances. If you created your vpc with the [vpc](/components/vpc) component, an EC2 instance connect endpoint is set up automatically.`
	`23`	`+ * _NOTE_: if your instances are within a private subnet (as is likely the case), you need a way to access your instances. If you created your vpc with the [vpc](/components/vpc/) component, an EC2 instance connect endpoint is set up automatically.`
`24`	`24`	`*`
`25`	`25`	* ```bash
`26`	`26`	`* # Connect to an instance using Instance Connect (no key pairs needed)`
`@@ -32,9 +32,9 @@`
`32`	`32`	`* ## Related Components`
`33`	`33`	`*`
`34`	`34`	`* Clusters work together with other Stackattack components:`
`35`		`- * - [vpc](/components/vpc) - Provides networking foundation with private/public subnets`
`36`		`- * - [service](/components/service) - Runs containerized applications on the cluster`
`37`		`- * - [load-balancer](/components/load-balancer) - Routes external traffic to services on the cluster`
	`35`	`+ * - [vpc](/components/vpc/) - Provides networking foundation with private/public subnets`
	`36`	`+ * - [service](/components/service/) - Runs containerized applications on the cluster`
	`37`	`+ * - [load-balancer](/components/load-balancer/) - Routes external traffic to services on the cluster`
`38`	`38`	`*`
`39`	`39`	`* ## Costs`
`40`	`40`	`*`
`@@ -52,7 +52,7 @@`
`52`	`52`	`* - Use spot instances for non-critical workloads (up to 90% savings)`
`53`	`53`	`* - Enable cluster auto-scaling to scale to zero during low usage`
`54`	`54`	`* - Monitor instance utilization and rightsize instance types`
`55`		`- * - Use [service](/components/service) placement strategies to maximize instance utilization`
	`55`	`+ * - Use [service](/components/service/) placement strategies to maximize instance utilization`
`56`	`56`	`*`
`57`	`57`	`* See [EC2 Pricing](https://aws.amazon.com/ec2/pricing/) for current rates.`
`58`	`58`	`*/`
Original file line number	Diff line number	Diff line change
`@@ -61,7 +61,7 @@`
`61`	`61`	`* ## Related Components`
`62`	`62`	`*`
`63`	`63`	`* Databases work together with other Stackattack components:`
`64`		`- * - [vpc](/components/vpc) - Provides secure private networking for database access`
	`64`	`+ * - [vpc](/components/vpc/) - Provides secure private networking for database access`
`65`	`65`	`*`
`66`	`66`	`* ## Costs`
`67`	`67`	`*`
Original file line number	Diff line number	Diff line change
`@@ -57,9 +57,9 @@`
`57`	`57`	`* ## Related Components`
`58`	`58`	`*`
`59`	`59`	`* Load balancers work together with other Stackattack components:`
`60`		`- * - [vpc](/components/vpc) - Provides public networking for internet-facing load balancers`
`61`		`- * - [service](/components/service) - Receives traffic routed through load balancers`
`62`		`- * - [certificate](/components/certificate) - Enables HTTPS termination at the load balancer`
	`60`	`+ * - [vpc](/components/vpc/) - Provides public networking for internet-facing load balancers`
	`61`	`+ * - [service](/components/service/) - Receives traffic routed through load balancers`
	`62`	`+ * - [certificate](/components/certificate/) - Enables HTTPS termination at the load balancer`
`63`	`63`	`*`
`64`	`64`	`* ## Costs`
`65`	`65`	`*`
Original file line number	Diff line number	Diff line change
`@@ -47,7 +47,7 @@`
`47`	`47`	`* ## Related Components`
`48`	`48`	`*`
`49`	`49`	`* Redis clusters work together with other Stackattack components:`
`50`		`- * - [vpc](/components/vpc) - Provides secure private networking for Redis access`
	`50`	`+ * - [vpc](/components/vpc/) - Provides secure private networking for Redis access`
`51`	`51`	`*`
`52`	`52`	`* ## Costs`
`53`	`53`	`*`
Original file line number	Diff line number	Diff line change
`@@ -53,7 +53,7 @@`
`53`	`53`	`* ## Related Components`
`54`	`54`	`*`
`55`	`55`	`* S3 firehoses work together with other Stackattack components:`
`56`		`- * - [bucket](/components/bucket) - Buckets are used to store the data that's written to the firehose.`
	`56`	`+ * - [bucket](/components/bucket/) - Buckets are used to store the data that's written to the firehose.`
`57`	`57`	`*`
`58`	`58`	`* ## Costs`
`59`	`59`	`*`
Original file line number	Diff line number	Diff line change
`@@ -39,15 +39,15 @@`
`39`	`39`	`* ## Related Components`
`40`	`40`	`*`
`41`	`41`	`* Services work together with other Stackattack components:`
`42`		`- * - [cluster](/components/cluster) - Provides compute capacity for running services`
`43`		`- * - [vpc](/components/vpc) - Provides networking foundation with private/public subnets`
`44`		`- * - [load-balancer](/components/load-balancer) - Routes external traffic to services`
	`42`	`+ * - [cluster](/components/cluster/) - Provides compute capacity for running services`
	`43`	`+ * - [vpc](/components/vpc/) - Provides networking foundation with private/public subnets`
	`44`	`+ * - [load-balancer](/components/load-balancer/) - Routes external traffic to services`
`45`	`45`	`*`
`46`	`46`	`* ## Costs`
`47`	`47`	`*`
`48`	`48`	`* ECS service costs depend on the underlying compute resources and are usage-based:`
`49`	`49`	`*`
`50`		`- * - EC2 instances - If using EC2 capacity providers, you pay for the underlying EC2 instances (~$0.0116/hour for t3.micro). The [cluster](/components/cluster) component manages auto-scaling groups that can scale to zero when no tasks are running.`
	`50`	`+ * - EC2 instances - If using EC2 capacity providers, you pay for the underlying EC2 instances (~$0.0116/hour for t3.micro). The [cluster](/components/cluster/) component manages auto-scaling groups that can scale to zero when no tasks are running.`
`51`	`51`	`*`
`52`	`52`	`* - Fargate - If using Fargate capacity providers, you pay per vCPU-hour (~$0.04048/vCPU/hour) and per GB-hour (~$0.004445/GB/hour). A 0.5 vCPU, 1GB task running 24/7 costs ~$15/month.`
`53`	`53`	`*`
`@@ -56,7 +56,7 @@`
`56`	`56`	* - CloudWatch Logs - Log storage is ~$0.50/GB/month. Use the `logRetention` parameter to automatically delete old logs and control costs.
`57`	`57`	`*`
`58`	`58`	`* Cost optimization strategies:`
`59`		`- * - Use the [cluster](/components/cluster) component's auto-scaling features to scale EC2 instances to zero during low usage`
	`59`	`+ * - Use the [cluster](/components/cluster/) component's auto-scaling features to scale EC2 instances to zero during low usage`
`60`	`60`	* - Set appropriate `logRetention` periods (default: 30 days)
`61`	`61`	`* - Consider spot instances for non-critical workloads through capacity provider configuration`
`62`	`62`	`*`
`@@ -345,7 +345,7 @@ export interface ServiceArgs extends TaskDefinitionArgs {`
`345`	`345`	`orderedPlacementStrategies?: pulumi.Input<`
`346`	`346`	`pulumi.Input<aws.types.input.ecs.ServiceOrderedPlacementStrategy>[]`
`347`	`347`	`>;`
`348`		- /** Specify an auto-scaling configuration for your service. Cannot be used with `replicas`. See the [serviceAutoScaling](/components/service-autoscaling) component for argument documentation. */
	`348`	+ /** Specify an auto-scaling configuration for your service. Cannot be used with `replicas`. See the [serviceAutoScaling](/components/service-autoscaling/) component for argument documentation. */
`349`	`349`	`autoScaling?: Omit<ServiceAutoScalingArgs, "service">;`
`350`	`350`	`}`
`351`	`351`
Original file line number	Diff line number	Diff line change
`@@ -61,8 +61,8 @@`
`61`	`61`	`* ## Related Components`
`62`	`62`	`*`
`63`	`63`	`* Static sites work together with other Stackattack components:`
`64`		`- * - [bucket](/components/bucket) - Stores website files in S3`
`65`		`- * - [certificate](/components/certificate) - Provides SSL certificates for HTTPS domains`
	`64`	`+ * - [bucket](/components/bucket/) - Stores website files in S3`
	`65`	`+ * - [certificate](/components/certificate/) - Provides SSL certificates for HTTPS domains`
`66`	`66`	`*`
`67`	`67`	`* ## Costs`
`68`	`68`	`*`