Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Platform Support - AWS ECS #96

Open
aviboru opened this issue Jul 13, 2024 · 1 comment
Open

[FEATURE] Platform Support - AWS ECS #96

aviboru opened this issue Jul 13, 2024 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@aviboru
Copy link

aviboru commented Jul 13, 2024

Detailed description

I would like to request support for AWS Elastic Container Service (ECS) within the Score Specification project. This addition would allow developers to use Score specifications to deploy workloads on AWS ECS, further enhancing the project's platform-agnostic capabilities.

AWS ECS is a highly scalable container orchestration service that many developers use for deploying and managing containerized applications. Integrating ECS support into Score would provide the following benefits:

  • Consistency: Ensure consistent workload configuration across AWS ECS alongside existing platforms like Docker and Kubernetes.
  • Ease of Use: Simplify deployment processes on AWS ECS by leveraging the declarative nature of Score specifications.
  • Broader Adoption: Attract a wider user base who are using AWS ECS for their cloud-native applications.

Context

Support for AWS ECS will complement the existing Docker Compose and Kubernetes integrations, making Score a more versatile tool for cloud-native development.

Possible implementation

Develop a reference implementation that translates Score specifications into ECS Task Definitions and Service configurations. This implementation should:

  • Support defining containers, environment variables, volumes, and networking configurations specific to AWS ECS.
  • Include comprehensive documentation and examples to help users get started quickly.
  • Ensure compatibility with existing Score features and maintain the project's environment-agnostic ethos.

Additional information

Benefits

  • Enhanced developer productivity by reducing the need to write and manage ECS-specific configurations.
  • Streamlined CI/CD processes with consistent configurations across multiple environments.
  • Greater flexibility for developers to choose their preferred cloud-native platform without configuration inconsistencies.

I believe this feature will significantly benefit the community and look forward to seeing it in future releases.

References

Thank you for considering this feature request.

@sujaya-sys
Copy link
Contributor

Hi @aviboru thank you for submitting such a well defined feature request!

At the moment we're focused on supporting the community with building their own Score implementations rather than investing into the creation of further reference implementations.

The idea is that our existing reference implementations for score-compose and score-k8s serve as a blueprint of how to implement the Score specification. That being said, we're still looking to improve our documentation on this, which is why we'd be more than happy to support you if you decide to go ahead and dive into a score-ecs implementation.

BTW this thread here might be interesting for you 🙂 https://cloud-native.slack.com/archives/C07DN0D1UCW/p1714488818982859 (#slack channel in the CNCF slack workspace)

@astromechza astromechza added the help wanted Extra attention is needed label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants