AWS/DevOps - Revision history

Christoph: /* AWS Config */

2021-02-26T17:56:54Z

‎AWS Config

Christoph: /* Introduction */

2021-02-19T23:01:43Z

‎Introduction

Christoph: /* Configuration Management and Infrastructure as Code */

2021-02-19T22:55:19Z

‎Configuration Management and Infrastructure as Code

Christoph: /* External links */

2021-02-19T00:43:02Z

‎External links

Christoph: /* AWS Trusted Advisor */

2021-02-19T00:12:59Z

‎AWS Trusted Advisor

Christoph: /* AWS Config */

2021-02-19T00:10:12Z

‎AWS Config

Christoph: /* Monitoring and Logging */

2021-02-19T00:08:02Z

‎Monitoring and Logging

Christoph: /* AWS OpsWorks */

2021-02-19T00:00:05Z

‎AWS OpsWorks

Christoph: /* AWS Systems Manager */

2021-02-18T23:58:23Z

‎AWS Systems Manager

Christoph: /* External links */

2021-02-18T23:47:34Z

‎External links

← Older revision		Revision as of 17:56, 26 February 2021
Line 302:		Line 302:

	AWS Config also provides a clear view of the resource change timeline, including changes in both the resource configurations and the associations of those resources to other AWS resources.		AWS Config also provides a clear view of the resource change timeline, including changes in both the resource configurations and the associations of those resources to other AWS resources.
		+
		+	AWS Config is a web service that performs configuration management of supported AWS resources within your account and delivers log files to you. The recorded information includes the configuration item (AWS resource), relationships between configuration items (AWS resources), any configuration changes between resources. The AWS configuration item history captured by AWS Config enables security analysis,
		+	resource change tracking, and compliance auditing.

	When many different resources are changing frequently and automatically, automating compliance can become as important as automating the delivery pipeline. To respond to changes in the environment, you can use AWS Config rules.		When many different resources are changing frequently and automatically, automating compliance can become as important as automating the delivery pipeline. To respond to changes in the environment, you can use AWS Config rules.

@@ Line 221: / Line 221: @@
 # Resource optimization:
 #: AWS Trusted Advisor
 ===AWS CloudFormation===

← Older revision		Revision as of 22:55, 19 February 2021
Line 207:		Line 207:

	===Introduction===		===Introduction===
		+
		+	; Infrastructure as Code (IaC) lifecycle
		+
		+	# Resource provisioning:
		+	#: AWS CloudFormation
		+	# Configuration management:
		+	#: AWS OpsWorks for Chef Automate
		+	#: Amazon EC2 Systems Manager
		+	# Monitoring and performance:
		+	#: Amazon CloudWatch
		+	# Governance and compliance:
		+	#: AWS Config
		+	# Resource optimization:
		+	#: AWS Trusted Advisor

	===AWS CloudFormation===		===AWS CloudFormation===

@@ Line 551: / Line 551: @@
 * [https://aws.amazon.com/certification/certified-devops-engineer-professional/ AWS Certified DevOps Engineer - Professional]
 * [https://docs.aws.amazon.com/whitepapers/latest/introduction-devops-aws/welcome.html Introduction to AWS DevOps] (whitepapers)
 ; Study tips

← Older revision		Revision as of 00:12, 19 February 2021
Line 388:		Line 388:

	===AWS Trusted Advisor===		===AWS Trusted Advisor===
		+
		+	'''AWS Trusted Advisor''' helps you observe best practices by scanning your AWS resources and comparing their usage against AWS best practices in four categories: cost optimization, performance, security, and fault tolerance. As part of ongoing improvement to your infrastructure and applications, taking advantage of Trusted Advisor can help keep your resources provisioned optimally.
		+
		+	; Checks
		+
		+	Trusted Advisor provides a variety of checks to determine if the infrastructure is following best practices. The checks include detailed descriptions of recommended best practices, alert criteria, guidelines for action, and a list of useful resources on the topic. Trusted Advisor provides the results of the checks and can also provide ongoing weekly notifications for status updates and cost savings.
		+
		+	All customers have access to a core set of Trusted Advisor checks. Customers with AWS Business or Enterprise support can access all Trusted Advisor checks and the Trusted Advisor APIs. Using the APIs, you can obtain information from Trusted Advisor and take corrective actions. For example, a program could leverage Trusted Advisor to examine current account service limits. If current resource usages approach the limits, you can automatically create a support case to increase the limits.
		+
		+	Additionally, Trusted Advisor now integrates with Amazon CloudWatch Events. You can design a Lambda function to notify a Slack channel when the status of Trusted Advisor checks changes. These examples illustrate how the concept of Infrastructure as Code can be extended to the resource optimization level of the information resource lifecycle.
		+
		+	; Best Practices
		+
		+	The best practices for AWS Trusted Advisor are listed below:
		+	* Subscribe to Trusted Advisor notifications through email or an alternative delivery system.
		+	* Use distribution lists and ensure that the appropriate recipients are included on all such notifications.
		+	* If you have AWS Business or Enterprise support, use the AWS Support API in conjunction with Trusted Advisor notifications to create cases with AWS Support to perform remediation.
		+
		+	; Summary
		+
		+	You must continuously monitor your infrastructure to optimize the infrastructure resources with regard to performance, security, and cost. AWS Trusted Advisor provides the ability to use APIs to interrogate your AWS infrastructure for recommendations, thus extending Infrastructure as Code to the optimization phase of the information resource lifecycle.

	===AWS Systems Manager===		===AWS Systems Manager===

@@ Line 281: / Line 281: @@
 ===AWS Config===
 * Delete Config service:
@@ Line 286: / Line 300: @@
 $ aws configservice delete-configuration-recorder --configuration-recorder-name default
 </pre>
 ===Amazon ECS===

@@ Line 303: / Line 303: @@
 ==Monitoring and Logging==
-* Introduction
+===Introduction===
 ===CloudWatch===
 <pre>
 $ aws cloudwatch put-metric-data \
@@ Line 315: / Line 327: @@
 </pre>
-* CloudWatch Custom Metrics
+===CloudWatch Custom Metrics===
-* CloudWatch Events
 ===CloudWatch Logs===
 <pre>
 $ sudo dpkg -i amazon-cloudwatch-agent.deb

← Older revision		Revision as of 00:00, 19 February 2021
Line 296:		Line 296:

	===AWS OpsWorks===		===AWS OpsWorks===
		+
		+	'''AWS OpsWorks for Chef Automate''' brings the capabilities of Chef, a configuration management platform, to AWS. OpsWorks for Chef Automate further builds on Chef's capabilities by providing additional features that support DevOps capabilities at scale. Chef is based on the concept of recipes, configuration scripts written in the Ruby language that perform tasks such as installing services. Chef recipes, like AWS CloudFormation templates, are a form of source code that can be version controlled, thereby extending the principle of Infrastructure as Code to the configuration management stage of the resource lifecycle.
		+
		+	OpsWorks for Chef Automate expands the capabilities of Chef to enable your organization to implement DevOps at scale. OpsWorks for Chef Automate provides three key capabilities that you can configure to support DevOps practices: workflow, compliance, and visibility.

	==Monitoring and Logging==		==Monitoring and Logging==

@@ Line 337: / Line 337: @@
 ===AWS Systems Manager===
-A management service that assists with:
+'''Amazon EC2 Systems Manager''' is a collection of capabilities that simplifies common maintenance, management, deployment, and execution of operational tasks on EC2 instances and servers or virtual machines (VMs) in on-premises environments. Systems Manager helps you easily understand and control the current state of your EC2 instance and OS configurations. You can track and remotely manage system configuration, OS patch levels, application configurations, and other details about deployments as they occur over time. These capabilities help with automating complex and repetitive tasks, defining
 * Collecting software inventory
 * Applying OS patches
@@ Line 348: / Line 351: @@
 Lets you run a given command(s) across all of your EC2 instances (or a group of them).
 ===AWS Organizations===