Open nkkko opened 3 weeks ago
/bounty $150
/attempt #81
with your implementation plan/claim #81
in the PR body to claim the bountyIf no one is assigned to the issue, feel free to tackle it, without confirmation from us, after registering your attempt. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code.
Please respect others by working on PRs that you are allowed to submit attempts to.
e.g. If you reached the limit of active attempts, please wait for the ability to do so before submitting a new PR.
If you can not submit an attempt, you will not receive your payout.
Thank you for contributing to daytonaio/content!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @Abraham12611 | Aug 28, 2024, 10:57:11 AM | #95 |
🔴 @the-johnwick | Aug 31, 2024, 3:10:27 PM | WIP |
🟢 @Kiran1689 | Sep 2, 2024, 5:04:06 PM | #96 |
/attempt #81
@nkkko Could you please assign me this issue since I have added the aws git provider support on this project?
/attempt #81
Algora profile | Completed bounties | Tech | Active attempts | Options |
---|---|---|---|---|
@the-johnwick | 2 daytonaio bounties + 1 bounty from 1 project |
Cancel attempt |
@the-johnwick this is the AWS provider in question: https://github.com/daytonaio/daytona-provider-aws
@the-johnwick this is the AWS provider in question: https://github.com/daytonaio/daytona-provider-aws
Oh not this one 😅. But I can do it.
/attempt #81
@nkkko Do I need to create a workspace on EC2, or is it just about setting up and configuring providers and targets?
💡 @Abraham12611 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
💡 @Kiran1689 submitted a pull request that claims the bounty. You can visit your bounty board to reward.
@Kiran1689 you have been assigned due to the greater quality and more broader article, also for the inclusion of definitions.
Content Type
Article
Article Description
This article provides an overview of the newly introduced Daytona AWS Provider, which allows Daytona to create and manage workspace projects on Amazon EC2 instances. It will cover the necessary steps for setting up and configuring this provider, including prerequisites such as ensuring the AWS programmatic access user has the AmazonEC2FullAccess permissions. The article will also detail the target options available for customization and provide troubleshooting tips for common issues.
Target Audience
Developers and DevOps professionals who use or plan to use Daytona for managing and deploying workspaces, particularly those leveraging Amazon Web Services (AWS) for their infrastructure. This includes individuals looking to utilize EC2 instances for their development and operations tasks.
References/Resources
Examples
No response
Special Instructions
Provide comprehensive, step-by-step instructions for setting up the AWS Provider, complete with command examples and screenshots where applicable. Include sections on detailed target options and common issues with corresponding troubleshooting tips. Inform readers that the AWS Provider is in alpha release state and mention any known limitations or caveats.