AWS development environments for local and cloud deployment can differ significantly, leading to extra complexity and setup during cloud migration. By developing directly within AWS environments, using tools such as Lambda, Cloud9, SageMaker Studio, client VPN connections, or LocalStack, developers can streamline transitions to production and leverage AWS-managed services from the start. This episode outlines three primary strategies for treating AWS as your development environment, details the benefits and tradeoffs of each, and explains the role of infrastructure-as-code tools such as Terraform and CDK in maintaining replicable, trackable cloud infrastructure.
Links
Docker Fundamentals for Development
- Docker containers encapsulate operating systems, packages, and code, which simplifies dependency management and deployment.
- Files are added to containers using either the COPY command for one-time inclusion during a build or the volume directive for live synchronization during development.
- Docker Compose orchestrates multiple containers on a local environment, while Kubernetes is used at larger scale for container orchestration in the cloud.
Docker and AWS Integration
- Docker is frequently used in AWS, including for packaging and deploying Lambda functions, SageMaker jobs, and ECS/Fargate containers.
- Deploying complex applications like web servers and databases on AWS involves using services such as ECR for image storage, ECS/Fargate for container management, RDS for databases, and requires configuration of networking components such as VPCs, subnets, and security groups.
Challenges in Migrating from Localhost to AWS
- Local Docker Compose setups differ considerably from AWS managed services architecture.
- Migrating to AWS involves extra steps such as pushing images to ECR, establishing networking with VPCs, configuring load balancers or API Gateway, setting up domain names with Route 53, and integrating SSL certificates via ACM.
- Configuring internal communication between services and securing databases adds complexity compared to local development.
Strategy 1: Developing Entirely in the AWS Cloud
- Developers can use AWS Lambda's built-in code editor, Cloud9 IDE, and SageMaker Studio to edit, run, and deploy code directly in the AWS console.
- Cloud-based development is not tied to a single machine and eliminates local environment setup.
- While convenient, in-browser IDEs like Cloud9 and SageMaker Studio are less powerful than established local tools like PyCharm or DataGrip.
Strategy 2: Local Development Connected to AWS via Client VPN
- The AWS Client VPN enables local machines to securely access AWS VPC resources, such as RDS databases or Lambda endpoints, as if they were on the same network.
- This approach allows developers to continue using their preferred local IDEs while testing code against actual cloud services.
- Storing sensitive credentials is handled by AWS Secrets Manager instead of local files or environment variables.
- Example tutorials and instructions:
Strategy 3: Local Emulation of AWS Using LocalStack
- LocalStack provides local, Docker-based emulation of AWS services, allowing development and testing without incurring cloud costs or latency.
- The project offers a free tier supporting core serverless services and a paid tier covering more advanced features like RDS, ACM, and Route 53.
- LocalStack supports mounting local source files into Lambda functions, enabling direct development on the local machine with changes immediately reflected in the emulated AWS environment.
- This approach brings rapid iteration and cost savings, but coverage of AWS features may vary, especially for advanced or new AWS services.
Infrastructure as Code: Managing AWS Environments
- Managing AWS resources through the web console is not sustainable for tracking or reproducing environments.
