![]() ![]() With the right permissions set, we can connect to our EC2 instance with an SSH client and run the CloudWatch Logs Agent interactive setup. Step 2: Agent Installation & Configuration In this case, we have an instance we launched with the permissions for the IAM role for all logs actions with the following policy (to learn more about adding a policy to an existing IAM role, see IAM Users and Groups and Managing IAM Policies in Using IAM:) ![]() ![]() In this blog post, we’re using a feature of IAM called IAM Roles for EC2, which lets us associate specific permissions with an Amazon EC2 instance when you launch it. Cloudwatch Logs is also supported on Windows Server, which we’ll cover in another post (for more information, see Configuring a Windows Instance Using the EC2Config Service.) Step 1: PermissionsĬloudWatch uses the Identity and Access Management (IAM) service for authentication and authorization. In this blog post, we’ll show you how easy it is to get started by walking through the installation process on Linux-based systems. You can get started in just minutes using the Amazon CloudWatch Logs agent for Amazon Linux, CentOs, Redhat Linux and Ubuntu. Amazon CloudWatch Logs lets you monitor your applications and systems for operational issues in near real-time using your existing log files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |