![]() ![]() ![]() Copy and paste the sample policies provided on this page and apply them to an IAM Group as custom inline policies.Create multiple different users, groups, and roles with permissions specific to the services from which you plan to collect data. ![]() You can apply the policy to the IAM group that is used by the user accounts or the EC2s that the Splunk Add-on for AWS uses to connect to your AWS environment. Use the AWS Policy Generator tool to collect all permissions into one centrally managed policy.There are three ways to manage policies for your IAM roles: If you run this add-on on a Splunk platform instance in your own managed Amazon Elastic Compute Cloud (EC2), then assign that EC2 to a role and give that role the IAM permissions listed here.You then grant those roles the permissions that are required by the AWS account. To let the Splunk Add-on for Amazon Web Services access the data in your AWS account, you assign an IAM role to one or more AWS accounts.If you do not have administrator access, work with your AWS admin to set up the accounts with the required permissions. To configure AWS accounts and permissions, you must have administrator rights in the AWS Management Console. Find an IAM role within your Splunk platform instance.īefore you can configure Splunk Cloud or Splunk Enterprise to work with your AWS data, you must set up accounts in Amazon Web Services.Ĭreate an IAM role and assign it to your AWS account.Create an IAM role and assign it to your AWS account.Read the following sections to do the following: The Splunk Add-on for Amazon Web Services (AWS) can only access the data in your AWS account if your account has an IAM AWS Identity Account Management (IAM) role. Manage accounts for the Splunk Add-on for AWS ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |