• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Vote What do you think about securing of tokens for access to cloud(s) API?

What do you think about the improvement?

  • I prefer automatic creation of restricted user

    Votes: 5 100.0%
  • I prefer create a restricted user by self

    Votes: 0 0.0%
  • I won't use a restricted user / I don't worry about security

    Votes: 0 0.0%

  • Total voters
    5

AYamshanov

Golden Pleskian
Staff member
Hi everyone,

Some time ago we improved AWS API Authorization form in Amazon Route 53 extension

AWS_API_Authorization_form.png

We added a choice:
  • the extension automatically creates a new IAM-restricted user
  • use user credential that was created by you previously

We'd like to discuss this with you guys -- is it useful or not? What do you think about securing of tokens for access to cloud API?

Could you say what you think about the improvement? Do you prefer to use automatic user creation or do you prefer to create a new user, create a restricted policy, then apply the policy to the user by self? Do you worry about restrict policy or not? Do you worry about protection of access/secret keys for access to clouds API?

Please let us know and vote in the poll. Thanks!
 
  • Like
Reactions: Hex
Back
Top