DEV Community

Cover image for Configure a privately hosted Git repository for EMR Studio
Mohamed Radwan for AWS Community Builders

Posted on • Edited on

4 1 1 1 1

Configure a privately hosted Git repository for EMR Studio

By default, you can access GitHub and GitLab from the studio workspace. If you are using a private Git repository, follow these steps:

  1. Create a Studio: You should use a VPC with private subnets that have a NAT gateway to enable communication with the internet.
  2. Ensure that the security group for the default workspace has an outbound rule allowing HTTPS traffic on port 443 to the destination 0.0.0.0/0
  3. Create VPC Endpoint:
  • Make sure the endpoint uses private subnets.

  • Confirm that the security group attached to the endpoint allows inbound rules for HTTPS traffic on port 443 with the source set to either "Your VPC Address" or "0.0.0.0/0".

  • Upload the following configuration file into your Amazon S3 storage location that is used for your Studio in a folder called life-cycle-configuration:
    s3://BUCKET-NAME/life-cycle-configuration/configuration.json

GitServerDnsName - The DNS name of your Git server. For example "git.example.com".

GitServerIpV4List - A list of IPv4 addresses that belong to your Git servers, the example VPC CIDR is 10.0.0.0/16, DNS is 10.0.0.2

[
    {
        "Type": "PrivatelyHostedGitConfig",
        "Value": [
            {
                "DnsServerIpV4": "10.0.0.2",
                "GitServerDnsName": "git.example.com",
                "GitServerIpV4List": [
                    "1.2.3.4"
                ]
            }
        ]
    }
]
Enter fullscreen mode Exit fullscreen mode

"If you are facing issues, you may need to stop the workspace and start it again."

Sentry image

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →

Top comments (0)

Best Practices for Running  Container WordPress on AWS (ECS, EFS, RDS, ELB) using CDK cover image

Best Practices for Running Container WordPress on AWS (ECS, EFS, RDS, ELB) using CDK

This post discusses the process of migrating a growing WordPress eShop business to AWS using AWS CDK for an easily scalable, high availability architecture. The detailed structure encompasses several pillars: Compute, Storage, Database, Cache, CDN, DNS, Security, and Backup.

Read full post