Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introducing Administrator
  3. Organizations
  4. Licenses
  5. Metering
  6. Source control configuration
  7. Customer-managed encryption keys
  8. Secrets managers
  9. Permissions
  10. Schedules
  11. CLAIRE preferences
  12. Bundle management
  13. Connection Credentials storage location
  14. Service-specific settings
  15. Custom branding
  16. Informatica support access
  17. Event monitoring
  18. Troubleshooting security
  19. Cipher suites used by IDMC

Organization Administration

Organization Administration

Instance profile configuration for AWS Secrets Manager

Instance profile configuration for AWS Secrets Manager

If you access AWS Secrets Manager using instance profile authentication, you need to create an IAM policy that can read secrets, create a role that has this policy, and then attach an instance profile to the AWS resource that hosts the Secure Agent.
  1. Log in to the AWS Management Console.
  2. Navigate to the IAM console.
  3. Under
    Access management
    , select
    Policies
    .
  4. Click
    Create policy
    .
  5. Create an IAM policy with the
    All list actions
    and
    All read actions
    access levels as shown in the following image:
    The image shows an IAM policy named "SecretManagerReadOnly." Under "Permissions defined in this policy," the access levels "Limited: List, Read" are selected for the Secrets Manager service.
  6. Under
    Access management
    , select
    Roles
    .
  7. Click
    Create role
    .
  8. On the
    Select trusted entity
    page, select
    AWS service
    as the trusted entity type and
    EC2
    as the use case, and then click
    Next
    .
  9. On the
    Add permissions
    page, select the policy you created, and then click
    Next
    .
  10. Enter a role name, verify the permissions policy, and create the role, as shown in the following image:
    The image shows an IAM role named "EC2SecretReadOnly" Under "Permissions policies," the policy "SecretManagerReadOnly" is selected.
  11. Navigate to the EC2 dashboard and select the EC2 instance that hosts the Secure Agent.
  12. Click
    Advanced
    .
  13. Under
    IAM instance profile
    , select the IAM role you created, and launch the EC2 instance.

0 COMMENTS

We’d like to hear from you!