AWS Infrastructure Composer

A very brief look.

The text says;

Drag and drop any CloudFormation resource on a visual canvas
Connect and configure enhanced components to automatically build IaC for an application architecture
Seamlessly transition between authoring workflows visually with Step Functions Workflow Studio and defining resources with Infrastructure Composer
Integrate your browser with your project through “local sync” or use Composer in the AWS Toolkit for Visual Studio Code

Again, there was something similar to this in 2019, using a GUI to build infrastructure that would be converted to code. Nice to know they bought it back.

When you enter the Composer, it's a blank space with a light background with dots, very reminiscent to the screen for Cloud Formation. Infrastructure Objects are in a drawer to the left and you click and drag;

You see I've selected a bucket; I can rename it.

I tried to connect a bucket to a Dynamo DB Table, because Buckets store data, but it's not available yet.

It also lost one of my buckets somewhere in the ether of the GUI. Ah well. It happens. Somehow I couldn't find the outright EC2 instance in the drawer with the options. But I knew how I could bring it up;

I opened a Cloud Formation file I made with an EC2 instance with SSH enabled, a security group, and an imitation Firewall (at the time, Firewalls were implemented but most people found policies to work just fine).

And then I searched again and found it, and added a second Instance to my template.

Selecting the Template button does indeed show the code I created, with the ability to toggle between YAML and JSON.

You'll notice in the image above that there are dots connecting the components.

The just added instance does not have these dots, so I can't connect it to the Security Group.

So I opened the details of the original instance MyEC2Instance and copied the information to the new Instance, which connected it.

I can work on seeing if I can integrate the Firewalls properly now.

Comments

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return. In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now OpenTofu Sometimes, I write articles even when things don't work. It's about showing a learning process. Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach. That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init. As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

RUN TCP/IP | Morgan Lucas is Tech Blogging

Search This Blog