# Get Started

## Accessing the Infra API Server

### Prerequisites

* AWS cli
* kubectl

Apply for AWS dev SSO according to this [doc](https://pingcap.feishu.cn/docx/doxcnylr5yZjtEVkI1xgEOhRXym)


``` shell
aws sts get-caller-identity --profile dbaas-dev # make sure the output contains arn:aws:sts::385595570414:assumed-role/dbaas-dev/botocore-session-xxxx
aws eks --region us-west-2 update-kubeconfig --name dev-base-us-west-2 --profile dbaas-dev
kubectl get secret -n api-server-kubeconfig -ojsonpath='{.data.config}' | base64 -d > dev-infra.kubeconfig
vi dev-infra.kubeconfig # change server url from https://api-server.infra:443 to https://us-west-2.infra.shared.aws.tidbcloud.com:443
kubectl --kubeconfig dev-infra.kubeconfig get cluster -A
```

## Contribute

Note: the infra-provider repo is configured as un-forkable, so for development you have to create a branch and push directly to infra-provider. The branch can be named as `<my-github-username>/<feature-name>`.

``` shell
git clone git@github.com:tidbcloud/infra-provider.git
cd infra-provider
git checkout -b <my-github-username>/<feature-name>
```

For specific component, please refer to the corresponding development guide.