ecs | Thoughts about entity-component-system | Object-Relational Mapping library

I am trying to run a command to an ecs container managed by fargate. I can establish connection as well as execute successfully but I cannot get the response from said command inside my python script.

I am looking for a way to detect if the device I am using can support Dolby Atmos sounds.

After searching around I found this call.

https://github.com/w3c/media-capabilities/blob/main/explainer.md#spatial-audio

I've been working on a project which so far has just involved building some cloud infrastructure, and now I'm trying to add a CLI to simplify running some AWS Lambdas. Unfortunately both the sdist and wheel packages built using poetry build don't seem to include the dependencies, so I have to manually pip install all of them to run the command. Basically I

1. run poetry build in the project,
2. cd "$(mktemp --directory)",
3. python -m venv .venv,
4. . .venv/bin/activate,
5. pip install /path/to/result/of/poetry/build/above, and then
6. run the new .venv/bin/ executable.

At this point the executable fails, because pip did not install any of the package dependencies. If I pip show PACKAGE the Requires line is empty.

The Poetry manual doesn't seem to specify how to link dependencies to the built package, so what do I have to do instead?

I am using some optional dependencies, could that be interfering with the build process? To be clear, even non-optional dependencies do not show up in the package dependencies.

pyproject.toml:

I have an ECS cluster that will be created by my cdk stack. Before my ECS service stack deployment I have to run a fargate task to generate the build files and configs for my application. I want to run a standalone task inside an existing Ecs cluster.

I am running a Docker image on an ECS cluster to shell into it and run some simple tests. However when I run this:

I would like to launch an interactive shell into a public Docker image on my AWS ECS/Fargate cluster to run network/connectivity tests from inside the cluster.

It seems the official way to do this is with aws ecs run-task followed by aws ecs execute-command [1][2]

I'd like to use existing, public Docker Hub images rather than build custom images if possible.

If I run do run-task with no command or the default command, the task exits and execute-command won't work on an exited task.

I am currently using AWS ECS for my service deployment. For the shared volumes, I am binding some EFS volumes.

Here is my task definition:

Firstly, this is specific to CDK - I know there are plenty of questions/answers around this topic out there but none of them are CDK specific.

Given that best practices dictate that a Fargate deployment shouldn't look for the 'latest' tag in an ECR repository, how could one set up a CDK pipeline when using ECR as a source?

In a multi-repository application where each service is in it's own repository (where those repositories would have their own CDK CodeBuild deployments to set up building and pushing to ECR), how would the infrastructure CDK pipeline be aware of new images being pushed to an ECR repository and be able to deploy that new image to the ECS Fargate service?

Since a task definition has to specify an image tag (else it'll look for 'latest' which may not exist), this seems to be impossible.

As a concrete example, say I have the following 2 repositories:

• CdkInfra
  • One of these repositories would be created for each customer to create the full environment for their application
• SomeService
  • Actual application code
  • Only one of this repository should exist and re-used by multiple CdkInfra projects
  • cdk directory defining the CodeBuild project so when a push to master is detected, the service is built and the image pushed to ECR

The expected workflow would be as such:

1. SomeService repository is updated and so a new image is pushed to ECR
2. The CdkInfra pipeline should detect that a tracked ECR repository has a new image
3. The CdkInfra pipeline updates the Fargate task definition to reference the new image's tag
4. The Fargate service pulls the new image and deploys it

I know there is currently a limit with CodeDeploy not supporting ECS deployments due to CFN not supporting them, but it seems that CodePipelineActions has the ability to set up an EcrSourceAction which may be able to achieve this, however I've been unable to get this to work so far.

Is this possible at all, or am I stuck waiting until CFN support ECS CodeDeploy functionality?

How to enable container insights on already created ECS Fargate? I am running multiple ECS clusters for which container insight was not enabled while creating those. Now I have enabled that option in Account Settings. But it is for only the new cluster which I will create after enabling it. But how do I enable it on my existing cluster. Note I am running ECS Fargate and not ec2 instances.

Any help or documents is appreciated.

Note: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/deploy-container-insights-ECS-cluster.html