#ecs

I'm juggling weekly meal prep and a Unity prototype. The docs seem to say the new Input System can't be used with DOTS in Unity 2023.1 because ECS only supports the legacy Input Manager. I've attached an InputActionAsset to a SystemBase and get compile errors about missing IComponentData. The Burst compiler also throws "Unsupported feature: InputDevice" on my Ryzen 7 5800X running Windows 11.

My workflow idea was to drive cooking timers from a DOTS system synced with a Unity Timeline, but apparently the engine blocks any Input System integration when using ECS. Is this an intentional deprecation in Unity 2023.1, or am I overlooking a required package or scripting define?

• Unity version: 2023.1.15f1
• Packages: Entities 1.0.0-preview.13, Input System 1.3.0
• Target platform: PC (DirectX 12)
• CPU: Ryzen 7 5800X, 16GB RAM

Anyone confirmed this limitation or found a workaround?

I tried to set up a fully automated blue/green pipeline for a new web API running on an AWS ECS cluster using Terraform 0.15 and the AWS CDK modules. Here’s what I did so far:

• Define two ECS services with the same task definition family but different environment variables.
• Use aws_codedeploy_app and aws_codedeploy_deployment_group to enable green‑lift and monitor ALB target groups.
• Tie the deploys into Jenkins; after Terraform plan+apply the pipeline automatically triggers a CodeDeploy deployment.

Now the problem:

1. During a few recent test releases the target group of the new blue version receives 503s before health checks mark it healthy.
2. Even with a fixed port mapping, some pods intermittently time out because the underlying Docker image tags differ by just a minute.
3. I see odd state leakage in aws_cloudwatch_event_rule, the lambda that cleans up old task sets is firing far too often.

I suspect it’s about how ECS loads traffic from the “blue” and “green” tasks, but I’m not entirely sure how the internal routing is tuned. Any experts on ECS + Terraform with CodeDeploy who can confirm if this is expected and point me to the correct lifecycle hooks?

Would appreciate pull requests if you found a simpler config. Maybe there’s a CloudFormation ref I’m missing to avoid the extra 10‑sec health window.