Skip to main content

Overview and Configuration

This page describes the overview and configuration diagrams for the remote development environment. You can hover over the diagrams to zoom in or out, or open draw.io for direct editing. Note that any edits will not be reflected in the original uploaded file.

Private Subnet Configuration​

This is the recommended configuration that provides high security levels. It's useful when SSH port (22) cannot be used directly, but incurs fixed costs for VPC Endpoints and NAT Gateway.

Public Subnet Configuration​

This is the recommended configuration for ad-hoc verification and environment setup. It's a simple and convenient configuration, but care must be taken to ensure that security group settings are properly configured without any gaps.

Configuration Notes​

The following are key points and special considerations regarding the configuration.

Benefits of Remote Development Configuration​

  • High reproducibility, preventing errors due to OS and environment differences
  • Development convenience when private access to databases is required
  • Improved efficiency through standardization of tools and development practices
  • Advantages over local PC:
    • Not dependent on local specifications
    • No need to install development tools directly
  • Secure sandbox environment that does not use AWS credentials with permissions other than AssumeRole on the local PC

Communication Speed of SSH Port Forwarding via System Manager​

When using SSH Port Forwarding via System Manager, communication speed may be 5-10 times slower than usual. Since it's a remote connection, this is not a significant issue for normal development, and while latency is expected when verifying operation in the local environment, it rarely becomes an issue in backend or Web API development. For frontend development, loading assets and source code in development mode may take time, and if development becomes difficult, you can proceed by developing in the local environment and performing build work and verification on the remote instance using docker.

Precautions​

When using the Public subnet configuration, always verify that Security Group settings are properly configured and only open the minimum necessary port numbers and IP addresses.