Help Needed: Streamlining Microcks Deployment for AWS Marketplace #1537
Replies: 2 comments 8 replies
-
Hi @Vaishnav88sk , @yada , I recently worked on deploying applications on AWS. Since this is a frontend deployment, we have multiple options: AWS Amplify, EKS (Elastic Kubernetes Service), or ECS (Elastic Container Service) depending on the architecture and scalability requirements. For a complete AWS deployment, we need to set up the following: 1️⃣ Infrastructure Setup: |
Beta Was this translation helpful? Give feedback.
-
@kurst03 @mondrias @antonio-jimenez-gstock @andresionek91 @nmasse-itix @dhiemaz @Eroyi @cvsudheer108 @lbroudoux @yada Hello everyone! We are working on "Streamlining Microcks Deployment on AWS Marketplace" to create a validated and repeatable SaaS architecture for deploying Microcks on AWS. The goal is to simplify adoption by leveraging AWS-native services while ensuring scalability, security, and compliance with AWS Foundational Technical Review (FTR). Since many of you have deployed Microcks on AWS with services like EKS, IAM, Aurora, DocumentDB, API Gateway, VPC and CloudFormation, your insights would be extremely valuable in shaping this initiative. We'd love to hear your thoughts on: 🚀 Key Questions
🔍 Additional Insights
This initiative aims to enable one-click deployment from AWS Marketplace, with minimal effort, ensuring container scaling on EKS and persistent user data in Aurora PostgreSQL instead of containers. The app will be accessible through API Gateway, with automated infrastructure provisioning. Your experiences and feedback can help us refine this approach and build a shared repository of best practices for the community. Looking forward to your valuable input! 🚀 |
Beta Was this translation helpful? Give feedback.
-
Hello Microcks Community!
I’m Vaishnav Kale, an LFX mentee, and I’m thrilled to be working on "Streamlining Microcks Deployment on AWS Marketplace." As more organizations adopt Microcks, ensuring a simplified, scalable, and production-ready AWS deployment has become a key priority. This project aims to create a validated AWS SaaS architecture for Microcks, making it easier for adopters to deploy and manage within their cloud environments.
🚀 Why This Matters
While the Microcks maintainers focus on core features and security, adopters often face challenges when setting up production environments. Many users have expressed interest in deploying Microcks on AWS, but a standardized, well-documented process is missing. This initiative will help bridge that gap by:
🤝 How You Can Help!
If you’ve deployed Microcks on AWS before, your experience would be incredibly valuable! Here’s how you can contribute:
✅ Have you set up Microcks in an AWS environment? Share your insights on what worked well and what challenges you faced.
✅ What AWS services did you use? If you’ve integrated Microcks with AWS-native tools, we’d love to hear about your architecture and best practices.
✅ Are you interested in reviewing or contributing to the AWS deployment guide? Your feedback will help ensure we create a well-structured, easy-to-follow resource for all adopters.
✅ If you’ve worked on a similar project before, would you be open to sharing your learnings? Your experience can help shape a deployment framework that benefits the entire Microcks community.
This is a collaborative effort, and your input can make a huge impact! Let’s work together to simplify and enhance Microcks’ deployment on AWS. Looking forward to your thoughts, feedback, and contributions! 🚀
Beta Was this translation helpful? Give feedback.
All reactions