This is a demo of CloudEndure tool to migrate on-prem workloads to AWS.
==========================================================

***Hands-on AWS***

# CloudEndure - Hands-on Demo

Product page - features and pricing
[ Ссылка ]
[ Ссылка ]

## 1. Setup Demo Environment (CloudFormation Template)

Cloudformation Template URL (S3 Location) -- [ Ссылка ]

Region: Oregon (us-west-2)

```
CloudEndure IAM User : CloudEndureUser

Bastion host (Windows)
Username : Administrator
Bastion host password : HoA@2021 [your input to Coudformation]

All App and DB servers (Linux):
username : user
password : AWSmid20 [your input to Coudformation]

Cloudformation outputs -- (will vary)
BastionRDP: 52.26.3.147
SubnetTargetPrivate: subnet-09800402a01f57829
SubnetTargetPublic: subnet-02945c195856b5491
TargetSecurityGroup: sg-03bf48fe3ca0bd5b2

```

## 2. Architecture

Application URLs

* Wordpress [ Ссылка ]
* OFBiz ERP [ Ссылка ]
* Username: admin
* Password: ofbiz


## 3. CloudEndure Account

* Register - [ Ссылка ]
* Confirm Email
* Console Login - [ Ссылка ]

## 4. CloudEndure Project

* Create Security Credentials for CloudEndure on AWS

* Create Project on CloudEndure
* Supply AWS Credentials of CloudEndure user
* Replication Settings
- Migration Source - Other Infrastructure
- Migration Target - AWS US West (Oregon)
- Subnet where the Replication Servers will be launched - TargetPublic

## 5. CloudEndure Agent install

Servers

* wordpress-web | `wordpress-web.onpremsim.env`
* wordpress-db | `wordpress-db.onpremsim.env`
* ofbiz-web | `ofbiz-web.onpremsim.env`
* ofbiz-db | `ofbiz-db.onpremsim.env`

- SSH to each server (Putty)
- Steps from CloudEndure console: Download & Install

## 6. CloudEndure Blueprint

- Machine Type: `t3.medium`
- Subnet: `TargetPrivate`
- Security Groups: `TargetSecurityGroup` and `Default`
- Private IP address: Create New
- Public IP (ephemeral): No
- Disks: SSD - gp2

## 7. Migration & Cutover

- Launch Target Machines - Cutover Mode
- Shutdown source environment (app and db servers)
- From SSH/Putty `sudo shutdown -h now`
- Or from Bastion host command line
```bash
ssh user@wordpress-web.onpremsim.env "sudo shutdown -h now"

ssh user@wordpress-db.onpremsim.env "sudo shutdown -h now"

ssh user@ofbiz-web.onpremsim.env "sudo shutdown -h now"

ssh user@ofbiz-db.onpremsim.env "sudo shutdown -h now"
```

- Fetch IP addresses of Target servers
- From cloudshell / cli
```bash
aws ec2 describe-instances \
--filters "Name=tag:Name,Values=*onpremsim*" \
--query "Reservations[].Instances[].[InstanceId,State.Name,PrivateIpAddress,Tags[?Key=='Name'].Value]" \
--output yaml
```

Sample output
```yaml
- - i-08aee74f68263b931
- running
- 10.0.1.224
- - wordpress-web.onpremsim.env
- - i-084d0b14b2879cb62
- running
- 10.0.1.180
- - ofbiz-web.onpremsim.env
- - i-01d341c7d83bc79c2
- running
- 10.0.1.121
- - wordpress-db.onpremsim.env
- - i-00f5a40b00c48deeb
- running
- 10.0.1.216
- - ofbiz-db.onpremsim.env
```

- Update DNS on Target servers

```bash
ADDR=`hostname -I`
HOST=`hostname`
sudo touch /tmp/nsupdate.txt
sudo chmod 666 /tmp/nsupdate.txt
echo "server dns.onpremsim.env" > /tmp/nsupdate.txt
echo "update delete $HOST A" >> /tmp/nsupdate.txt
echo "update add $HOST 86400 A $ADDR" >> /tmp/nsupdate.txt
echo "update delete $HOST PTR" >>/tmp/nsupdate.txt
echo "update add $HOST 86400 PTR $ADDR" >> /tmp/nsupdate.txt
echo "send" >> tmp/nsupdate.txt
sudo nsupdate /tmp/nsupdate.txt
```

- Tip: As an alternative to using Putty tool and logging into each server separately, you can also issue these commands over SSH from commandline of the bastion host.


```bash
ssh user@ipaddress < commands.txt
```

- Alernatively

```bash
putty -ssh user@10.0.1.224
```

свернуть