There could be a situation when PowerShell modules have to be used on machine without internet access so here’s quick instruction how to deal with “donor” and “donee” machines:
Packer temporary virtual machine:
- Must be placed in pre-defined Azure VNet’s Subnet (instead of default temporary VNet and Subnet created by Packer)
- Must have Private IP only (instead of defaults with Public IP)
- EC2 instances must be automatically added to Active Directory (AD) on provisioning and removed form AD on termination
- Each EC2 instance must have 3 private IP addresses (required for MS SQL Always-On) assigned by DHCP
- NLB must be used to expose MS SQL Always-On Listener because it’s faster than changing CNAME value
- Dedicated ASG to keep each instance fault tolerant
- Dedicated data disks which are re-attached to new instance in ASG with the same disk letters
When API specification is updated in git (master branch only) it must be updated on Confluence automatically.
Provide sample API specification with CI pipeline for deployment to AWS API Gateway and S3 (only if
petstore.yaml was changed in master branch)
This sample API specification is used by aws-cloudformation-git-confluence-integration sample
If you’ve been working with both AWS and Azure you should have noticed that each of them has some advantages.
Tools like Terraform might be very helpful if you’re not familiar with both CloudFormation and Azure RM.
However don’t consider Terraform as a nonpareil (this is not true at all), it is simple tool for simple tasks.
So in this post I’ll tell you about Terraform terms and concepts and show example with AWS & Azure.
For a bit more complicated infrastructure you’ll have to use CloudFormation and Azure RM
If you’re working with GitHub you definitely should consider Gists for smaller pieces of code, like scripts.
As soon as you start you might want to commit to Gists using SSH, and GUI provides such option:
When you start working with Azure Service Fabric you might be disappointed with customisation possibilities.
So even if you just want to add a few Internal Load balancers you have to customise ARM template.
When you working with ARM templates it might be good idea to split VNet and KeyVaults from computing resources.
To make provision easier you can use PowerShell scripts, like this one for certificates.
Full solution you can find in my GitHub – https://github.com/kagarlickij/azure-fabric-arm
Now let’s see how it can be implemented:
When you’re working on CI/CD security is always important and certificates are quite useful.
Azure Service Fabric management with certificates is very easy, but creating certificate might be a bit confusing.
However, like most everything it can be easily automated with PowerShell and here’s example for you: