|
| 1 | +# Cloudformation Demo |
| 2 | + |
| 3 | + |
| 4 | +## step 1 to 5 runs on customer AWS account |
| 5 | + |
| 6 | + |
| 7 | +1. upload templates/scripts/license to S3 |
| 8 | + |
| 9 | + - upload needed files to S3 bucket 'cf-templates-blrxgroup-us-west-2', under folder 'development' |
| 10 | +```console |
| 11 | +cd cloudformation |
| 12 | +export AWS_PROFILE=*** |
| 13 | +./s3upload.sh cf-templates-blrxgroup-us-west-2 development |
| 14 | +``` |
| 15 | + |
| 16 | + |
| 17 | +2. create stack to deploy datahub platform in AWS |
| 18 | + |
| 19 | + - choose Oregon region -> Cloudformation -> Create stack |
| 20 | + |
| 21 | + - Template Amazon S3 URL: https://cf-templates-blrxgroup-us-west-2.s3.us-west-2.amazonaws.com/development/templates/datahub-infra-deployment.yaml |
| 22 | + |
| 23 | + - Stack name: datahub |
| 24 | + |
| 25 | + - The AZ's to deploy to: choose 'us-west-2a, us-west-2b, us-west-2c' |
| 26 | + |
| 27 | + - The key pair name to use to access the instances: choose 'developer' |
| 28 | + |
| 29 | + - The CIDR block to allow remote access: YOURIP/32, can find your IP from https://www.whatismyip.com/ |
| 30 | + |
| 31 | + - Stack failure options: choose 'Preserve successfully provisioned resources' (useful when working on development of cloudformation) |
| 32 | + |
| 33 | + - check: |
| 34 | + - "I acknowledge that AWS CloudFormation might create IAM resources with custom names." |
| 35 | + - "I acknowledge that AWS CloudFormation might require the following capability: CAPABILITY_AUTO_EXPAND" |
| 36 | + |
| 37 | + - click "Create stack" |
| 38 | + |
| 39 | + - you will see a stack 'datahub' (this is master stack), and it will invoke nested stacks in order |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | +3. find datahub platform info |
| 44 | + - after Stack Info show Status 'CREATE_COMPLETE', you can find needed info from nested stack <<datahub-AdminStack-***>>'s Outputs |
| 45 | + |
| 46 | + |
| 47 | + |
| 48 | +4. create vpc endpoint |
| 49 | + - wait till datahub-kotsadm network load balancer's status is Active |
| 50 | + - create stack |
| 51 | + - Stack Name: datahub-privatelink |
| 52 | + - Template Amazon S3 URL: https://cf-templates-blrxgroup-us-west-2.s3.us-west-2.amazonaws.com/development/templates/nested/privatelink.yaml |
| 53 | + |
| 54 | + |
| 55 | +5. manually update DNS record |
| 56 | + - find datahub.dev.blrxgroup.com in public hosted zone 'dev.blrxgroup.com', update it to point to new ALB (for example, dualstack.k8s-datahub-***.us-west-2.elb.amazonaws.com.) |
| 57 | + |
| 58 | + - access https://datahub.dev.blrxgroup.com for datahub app |
| 59 | + |
| 60 | + |
| 61 | +## step 6 runs on Acryl AWS account |
| 62 | +6. manually create VPC endpoint |
| 63 | + - under Acryl AWS account, us-west-2 region, find service by service name, for example com.amazonaws.vpce.us-west-2.vpce-svc-*** (get service name from step 4.), select shared vpc, choose 3 private subnets, attach default security group |
| 64 | + |
| 65 | + - access https://{vpc_endpoint_dns} to for kotsadmin, default password: Passw0rd |
0 commit comments