I'd recommend CloudFormation. It may also be helpful to have your IT team create an AMI for you to reference in your CF template. For example, we build a Windows AMI that includes peripheral software (Notepad++, ArcGIS Pro, Firefox, etc) we want to use. You can then reference that AMI ID when you deploy your CF template. Also make sure you are within ESRI's password guidelines - advice: don't use @ symbols and stay under 29 characters. Those have both caused us heartburn in the past.
You'll need to figure out your VPC + subnet(s), IAM user/role, custom domain+elastic IP (if needed), and load balancer (if needed) ahead of time. You'll also need an SSL .pfx ready to go, along with your ArcGIS Server license file. You can set up an S3 bucket for those.