What Is an AWS Remote Development Environment?
A remote development environment moves your editor, terminal, runtime and credentials onto cloud compute. You connect from a browser or over SSH, and code and secrets stay in the cloud instead of on individual laptops. Every developer starts from the same setup, close to the AWS services your application uses, including Amazon Bedrock.
AWS closed its Cloud9 IDE to new customers in July 2024, so teams starting today need another way to run one on AWS.
Why Choose Our Development Environment?
Our AWS Bedrock-enabled environments give you control over your development infrastructure and the tools and integrations you need to build AI applications.
Key Takeaway: Deploy and manage development environments in your own AWS VPCs while leveraging DevOpser's powerful GitOps capabilities.
What You Get
- VS Code in the browser: The environment runs code-server: a full VS Code editor and terminal in your browser, protected by a password from your console.
- IP allowlisting: Only the IP addresses you add when configuring the environment can reach it.
- Secrets in AWS Secrets Manager: Enter development secrets in the console. The platform creates them in AWS Secrets Manager and gives you an Environment Template for your .env file.
- An AI app template: Start from the Flask Bedrock template, with sign-up, multi-factor authentication, chat history and an admin panel already built. Tour the template.
- Amazon Bedrock access: Connect your app to Bedrock through a cross-account IAM role that you create in your own AWS account.
- An AI coding assistant: Install the coding assistant extension you prefer inside code-server.
- GitOps to production: Push a feature branch, merge it into staging, then merge into main to deploy to production.
Security and Compliance Built In
Security is built into every layer of our development environments. With NIST CSF compliance and AWS Secrets Manager integration, your credentials and sensitive data stay protected, even in self-managed environments. You sign in to the DevOpser console with GitHub and multi-factor authentication, and only allowlisted IP addresses can reach your development environment.
Key Takeaway: Security controls are pre-configured, so your development environment is secure from day one.
Features and Benefits
Development Control
Deploy and manage development environments in your own AWS VPCs with complete control over dev environment configuration.
Enterprise Security
NIST CSF compliant with AWS Secrets Manager integration and secure credential handling.
How to Launch Your AWS Remote Development Environment
Once you have a site on the DevOpser Platform, you launch its development environment from the console:
- Sign in: Go to app.devopser.io, sign in with GitHub and complete multi-factor authentication.
- Configure development secrets: On your site's detail page, add your Flask secret key, mail app password, allowlisted IPs and any additional secrets.
- Build the environment: Click Rebuild Environment, then Check Status until the build finishes.
- Log in: Copy the code-server password and the Environment Template, then click Login to Development.
- Run your app: Clone your repository, paste the Environment Template into .env and start the frontend and backend.
- Connect Bedrock: Create the cross-account IAM role in your AWS account and save its ARN in the console.
- Ship it: Merge to staging, then to main, and open your Staging and Production URLs from the site detail page.
Each step has a guide with screenshots: launch a development environment, deploy to development, configure Bedrock cross-account access, promote changes and access staging and production.
Flexible Development Options
The DevOpser Platform includes one managed development environment. Larger organizations often need more, or prefer to manage development infrastructure themselves. Our AWS Bedrock AMI lets you deploy and manage additional environments with these capabilities:
- Multiple Environments: Deploy multiple development environments in your own AWS VPCs
- Security Control: Configure network settings and security policies for your development environments
- Customization: Customize development environments to align with your organization's standards
- Integration: Connect development environments to your existing AWS resources
- GitOps Ready: Leverage DevOpser's GitOps workflow while maintaining control of development infrastructure
Key Takeaway: Run multiple development environments under your own control while staying integrated with the DevOpser Platform.
Self-Managed Setup
Prefer to run everything yourself? Set up a self-managed AWS Bedrock development environment in a few steps:
- Clone Repository: Get started with our Bedrock Flask Quickstart repository
- Configure: Set up your AWS credentials and region
- Deploy: Use our automated infrastructure templates
- Develop: Start building your AI application immediately
Ready to Launch? Our environments are optimized for the DevOpser AI Hosting Platform, ensuring a smooth transition from development to production.
Launch Your Development Environment Today
Get our AWS Bedrock development environment AMI through AWS Marketplace and deploy it in your own VPCs.
AWS Remote Development Environment FAQ
What is an AWS remote development environment?
It is a development workspace, including an editor, terminal, runtime and credentials, that runs on AWS instead of your local machine. You connect through a browser or SSH, and your code and secrets stay in the cloud.
How do I access my DevOpser development environment?
Click Login to Development on your site's detail page and enter the code-server password shown in the console. Only IP addresses on your allowlist can connect.
How does my app get access to Amazon Bedrock?
Your DevOpser app reaches Amazon Bedrock through a cross-account IAM role that you create in your own AWS account and register in the console. On a self-managed setup, you add your AWS credentials and region to the .env file.
How are secrets handled?
Secrets are stored in AWS Secrets Manager. Your .env file references them by name, and the console gives you a ready-made Environment Template to paste in.
Can I run development environments in my own AWS VPC?
Yes. The DevOpser Platform includes one managed development environment. To run more, or to keep them in your own VPCs, launch our AMI from AWS Marketplace.
How do changes get from development to production?
Through GitOps. Push a feature branch, open a pull request into staging to deploy there, then merge into main to deploy to production.