Skip to main content

AWS Architecting


Let's not talk about how many times I had to respell Architecting.

Most Secure, High performing, resilient,  efficient

Consistent for evaluating architectures.

Quicker Build and Deploy.
Stop guessing, start automating.

Lower or Mitigate Risks
- What are they?
- Do something about it.





Informed Decisions
- Cause and Effect.
- Not Affect.

Best Practices
- Exist.

Check ‘em out at aws.amazon.com/architecture/well-architected

———————

The Five Gates of Heaven Pillars of Well Architected Framework.

Operational Excellence
- Monitor things, deliver better value.
- Operations as code (scripting, automation)
- Automate documentation (Wow then why are humans here again?)
- Tiny changes for tiny reversals if needed.
- Refine processes
- You will fail. It’s okay. But you can mitigate or remove where you might fail.
- Most important is that you learn from it.


Security
Protect Systems, information, and assets.

- Strong identity foundation
    - Least privilege
    - Seperation of duties.
    - authorize sections of your AWS resources properly
- Traceability
    - audit, audit, audit.
    - And logs.
    - And metrics.

- In-depth security layering, not just the outer wall, so to speak.
- Automate security (lot of automation)

- Is your data encrypted at move and at rest? It should be. Also, don’t let people touch it. No one should be editing it at the home base.
- Run incident response sims.


Reliability
Is it up? And if it’s down, how long will it take to be up again? What happened to data in the process?

- Test in the cloud to validate recovery procedures.
- Monitor KPIs to trigger automation and auto notification about failures and to kick in auto recovery processes.
- Horizontal scaling.
- Out of many, One. But instead, Kill one to make many for better redundancy.
- Don’t guess capacity. Monitor the demand and system resources used.
- Let automation change your infrastructure.


Performance Efficiency

- Deployment. Mass Deployment.
- Take programming (I THINK it’s programming, it mentions NoSQL and Databases) into services.
- Go serverless (Though we know there re still servers)
- Have fun and experiment in a non-work enviroment of course.


Cost Optimization
- Pay as you go, so use as much or as little as you can afford.
- Test it out first. Analyze what you need.
- Stop them when you’re not using them.
- Measure efficiency.
- Don’t pay for data centers
Labels:

Comments

Post a Comment

Popular posts from this blog

Making KPI Dashboards with PowerBI

 While this is the free tier, I cannot share or collaborate with others, nor can I publish content to other people's workspaces, but they will not stop me from screenshooting and recording these self-taught adventures,so! I'm doing this because I idly searched "Mattel careers" and "Information Technology", and seeing a bulletpoint saying the following: Analytical and reporting skills such as creating dashboards and establishing KPIs such as experience with PowerBI, Cognos, Tableau, and Google Data Lake/AWS is preferred And thought "Well, I've used Tableau, and I've heard about PowerBI,  even if its in-demandness is questionable , so how similar is it? And can I write about it?"  First, PowerBI (PIB) does have a downloadable, local version, but apparently Windows-only. I could download the .exe but I couldn't run it / drag it to applications on my MacBook.  Not a problem, we'll use the online SaaS version, and a dataset found here, ...
Post a Comment
Read more

Log Sorting with AWS CloudWatch, AWS CloudWatch Insights

 The cool thing is, I was contracted to make these videos in collaboration with CloudAvail Technology Consulting to help people decide which service they wanted to use for their logging - AWS CloudWatch, AWS CloudWatch Insights, DataDog, or New Relic. I'm searching through nginx logs. I have accompanying videos of each service that you can find on the CloudAvail Youtube page; See these links to go to the DataDog and NewRelic posts.   The idea was to be subjective in the videos, but I can be objective on my personal blog.     CloudWatch     The syntax is odd, but easy to grasp. Sort log data by IP addresses, message codes, and status codes. The simplest query system, but not quite robust.   Insights       The syntax has changed - Vastly. I see major SQL influences. You can see that in how the parse function works - in this case, it's often taken pieces of a pre-existing standard - in this case, message - and breaking them into their own c...
Post a Comment
Read more

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...
Post a Comment
Read more