forked from quickbooks2018/aws
/
secure-management
165 lines (91 loc) · 4.85 KB
/
secure-management
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
#!/bin/bash
yum install -y docker;systemctl start docker;systemctl enable docker
docker run --name jenkins -d --user=root -v ~/jenkins:/var/jenkins_home -p 0.0.0.0:8090:8080 --restart unless-stopped jenkins/jenkins:lts
# END
# EC2-1
###########################################################################################################################################
# Jenkins-Session -EC2
aws ssm start-session --target "i-0b49305879846941f" \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["22"],"localPortNumber":["9020"]}'
# EC2-2
###########################################################################################################################################
# Windows-Manager-RDP session
aws ssm start-session --target "i-0b49305879846941f" \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["3389"],"localPortNumber":["9010"]}'
############################################################################################################################################
# SSM-Port-forward
#!/bin/bash
# Maintainer: Muhammad-Asim
# Purpose: SSM-PORT-FORWARD
### Requirement ### Please Install the SSM-SESSION MANAGER PLUGIN & then RUN the script & check your instance in AWS SSM available or not
############################################################################################################################
# Download the installer using the following URL:
# https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html
# For Windows
# curl -# -LO https://s3.amazonaws.com/session-manager-downloads/plugin/latest/windows/SessionManagerPluginSetup.exe
# Linux Amazon/Linux/Centos
# curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/linux_64bit/session-manager-plugin.rpm" -o "session-manager-plugin.rpm"
# sudo yum install -y session-manager-plugin.rpm
# Linux Ubuntu/18/16
# curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/ubuntu_64bit/session-manager-plugin.deb" -o "session-manager-plugin.deb"
# sudo dpkg -i session-manager-plugin.deb
#############################################################################################################################
# Add the role to an instance profile before attaching the instance profile to the EC2 instance.
INSTANCE_PROFILE_NAME="ssm-port-forward-instance-profile"
ROLE_NAME="ssm-port-forward-role"
TRUST="ec2-trust-relationship"
AWS_MANAGED_POLICY="arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"
read -p "Hi, there which EC2 you like to do port-forward???, provide me instanceID": INSTANCE_ID
# 1. If you haven't already created an instance profile, run the following AWS CLI command:
aws iam create-instance-profile --instance-profile-name $INSTANCE_PROFILE_NAME
# 2. IAM Role creation & assume role
cat <<EOF >"$TRUST".json
{
"Version": "2008-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Allow",
"Principal": {
"Service": "ec2.amazonaws.com"
},
"Action": "sts:AssumeRole"
}
]
}
EOF
aws iam create-role --role-name "$ROLE_NAME" --assume-role-policy-document file://"$TRUST".json --description "EC2 Access"
# 3. Attaching existing AWS Manager Policy for SSM to the Custom Role created
aws iam attach-role-policy --role-name "$ROLE_NAME" --policy-arn "$AWS_MANAGED_POLICY"
# 4. Run the following AWS CLI command to add the role to the instance profile:
aws iam add-role-to-instance-profile --instance-profile-name "$INSTANCE_PROFILE_NAME" --role-name "$ROLE_NAME"
# 5. Run the following AWS CLI command to attach the instance profile to the EC2 instance:
aws ec2 associate-iam-instance-profile --iam-instance-profile Name="$INSTANCE_PROFILE_NAME" --instance-id "$INSTANCE_ID"
echo -e "\nPlease wait 75 seconds instance is rebooting, to make sure SSM Agent is refreshed & running\n"
for (( i=1; i<=15; i=i+1 ))
do
sleep 1
echo $i
done
# Rebooting the EC2 to make sure, the instance should be quickly a part of SSM
aws ec2 reboot-instances --instance-ids "$INSTANCE_ID"
n=60
while [ $n -gt 0 ]
do
echo "Plese wait your instance with ID "$INSTANCE_ID" is rebooting in "$n" seconds"
sleep 1s
echo " "
((n=$n-1))
done
# SSM Plugin Installation
aws ssm start-session --target "i-0b49305879846941f" \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["22"],"localPortNumber":["9020"]}'
aws ssm start-session --target "i-0928990f5c85d5fdd" \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["3389"],"localPortNumber":["9030"]}'
# Connection Tip SSH/RDP
#ssh -i jenkins-demo ec2-user@localhost -p 9000 -vvv
# END