![]() ![]() So next comes (in no particular order, CloudFormation can build them asynchronously) the: Once that is built and our new network is in place, it moves on to the securitygroups resource, which orchestrates the creation of the virtual firewalls separating the various bits of infrastructure from each other and the outside world.Īfter that, there's a whole bunch of infra we can build at once, because it all DependsOn the VPC and the Security Groups (SGs) existing. The order is set using DependsOn in the master template, so because the newvpc resource has no dependencies it naturally gets built first, everything else depends on it because it builds a new Virtual Private Cloud (VPC) - a standalone virtual network at AWS. All the resource templates are in our repository, but also on AWS S3 for public use. ![]() Then for each requirement element it loads in a Resource sub-template that does the actual creation of that element. ![]() The master template defines all the parameters CloudFormation needs the end customer to enter in order to build the infrastructure and install Drupal. All the changes I had to make are recorded here in a pull request on GitHub for posterity. So more work that I intended to do - I could've just packed an Amazon Machine Image (AMI) and had done with it, but I decided I wanted to bring this reference architecture into 2021 so I could learn more about CloudFormation and also create a potentially useful "production release" Marketplace product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |