doc.go 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109
  1. // Code generated by private/model/cli/gen-api/main.go. DO NOT EDIT.
  2. // Package sts provides the client and types for making API
  3. // requests to AWS Security Token Service.
  4. //
  5. // The AWS Security Token Service (STS) is a web service that enables you to
  6. // request temporary, limited-privilege credentials for AWS Identity and Access
  7. // Management (IAM) users or for users that you authenticate (federated users).
  8. // This guide provides descriptions of the STS API. For more detailed information
  9. // about using this service, go to Temporary Security Credentials (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html).
  10. //
  11. // For information about setting up signatures and authorization through the
  12. // API, go to Signing AWS API Requests (https://docs.aws.amazon.com/general/latest/gr/signing_aws_api_requests.html)
  13. // in the AWS General Reference. For general information about the Query API,
  14. // go to Making Query Requests (https://docs.aws.amazon.com/IAM/latest/UserGuide/IAM_UsingQueryAPI.html)
  15. // in Using IAM. For information about using security tokens with other AWS
  16. // products, go to AWS Services That Work with IAM (https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_aws-services-that-work-with-iam.html)
  17. // in the IAM User Guide.
  18. //
  19. // If you're new to AWS and need additional technical information about a specific
  20. // AWS product, you can find the product's technical documentation at http://aws.amazon.com/documentation/
  21. // (http://aws.amazon.com/documentation/).
  22. //
  23. // Endpoints
  24. //
  25. // By default, AWS Security Token Service (STS) is available as a global service,
  26. // and all AWS STS requests go to a single endpoint at https://sts.amazonaws.com.
  27. // Global requests map to the US East (N. Virginia) region. AWS recommends using
  28. // Regional AWS STS endpoints instead of the global endpoint to reduce latency,
  29. // build in redundancy, and increase session token validity. For more information,
  30. // see Managing AWS STS in an AWS Region (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html)
  31. // in the IAM User Guide.
  32. //
  33. // Most AWS Regions are enabled for operations in all AWS services by default.
  34. // Those Regions are automatically activated for use with AWS STS. Some Regions,
  35. // such as Asia Pacific (Hong Kong), must be manually enabled. To learn more
  36. // about enabling and disabling AWS Regions, see Managing AWS Regions (https://docs.aws.amazon.com/general/latest/gr/rande-manage.html)
  37. // in the AWS General Reference. When you enable these AWS Regions, they are
  38. // automatically activated for use with AWS STS. You cannot activate the STS
  39. // endpoint for a Region that is disabled. Tokens that are valid in all AWS
  40. // Regions are longer than tokens that are valid in Regions that are enabled
  41. // by default. Changing this setting might affect existing systems where you
  42. // temporarily store tokens. For more information, see Managing Global Endpoint
  43. // Session Tokens (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html#sts-regions-manage-tokens)
  44. // in the IAM User Guide.
  45. //
  46. // After you activate a Region for use with AWS STS, you can direct AWS STS
  47. // API calls to that Region. AWS STS recommends that you provide both the Region
  48. // and endpoint when you make calls to a Regional endpoint. You can provide
  49. // the Region alone for manually enabled Regions, such as Asia Pacific (Hong
  50. // Kong). In this case, the calls are directed to the STS Regional endpoint.
  51. // However, if you provide the Region alone for Regions enabled by default,
  52. // the calls are directed to the global endpoint of https://sts.amazonaws.com.
  53. //
  54. // To view the list of AWS STS endpoints and whether they are active by default,
  55. // see Writing Code to Use AWS STS Regions (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_enable-regions.html#id_credentials_temp_enable-regions_writing_code)
  56. // in the IAM User Guide.
  57. //
  58. // Recording API requests
  59. //
  60. // STS supports AWS CloudTrail, which is a service that records AWS calls for
  61. // your AWS account and delivers log files to an Amazon S3 bucket. By using
  62. // information collected by CloudTrail, you can determine what requests were
  63. // successfully made to STS, who made the request, when it was made, and so
  64. // on.
  65. //
  66. // If you activate AWS STS endpoints in Regions other than the default global
  67. // endpoint, then you must also turn on CloudTrail logging in those Regions.
  68. // This is necessary to record any AWS STS API calls that are made in those
  69. // Regions. For more information, see Turning On CloudTrail in Additional Regions
  70. // (https://docs.aws.amazon.com/awscloudtrail/latest/userguide/aggregating_logs_regions_turn_on_ct.html)
  71. // in the AWS CloudTrail User Guide.
  72. //
  73. // AWS Security Token Service (STS) is a global service with a single endpoint
  74. // at https://sts.amazonaws.com. Calls to this endpoint are logged as calls
  75. // to a global service. However, because this endpoint is physically located
  76. // in the US East (N. Virginia) Region, your logs list us-east-1 as the event
  77. // Region. CloudTrail does not write these logs to the US East (Ohio) Region
  78. // unless you choose to include global service logs in that Region. CloudTrail
  79. // writes calls to all Regional endpoints to their respective Regions. For example,
  80. // calls to sts.us-east-2.amazonaws.com are published to the US East (Ohio)
  81. // Region and calls to sts.eu-central-1.amazonaws.com are published to the EU
  82. // (Frankfurt) Region.
  83. //
  84. // To learn more about CloudTrail, including how to turn it on and find your
  85. // log files, see the AWS CloudTrail User Guide (https://docs.aws.amazon.com/awscloudtrail/latest/userguide/what_is_cloud_trail_top_level.html).
  86. //
  87. // See https://docs.aws.amazon.com/goto/WebAPI/sts-2011-06-15 for more information on this service.
  88. //
  89. // See sts package documentation for more information.
  90. // https://docs.aws.amazon.com/sdk-for-go/api/service/sts/
  91. //
  92. // Using the Client
  93. //
  94. // To contact AWS Security Token Service with the SDK use the New function to create
  95. // a new service client. With that client you can make API requests to the service.
  96. // These clients are safe to use concurrently.
  97. //
  98. // See the SDK's documentation for more information on how to use the SDK.
  99. // https://docs.aws.amazon.com/sdk-for-go/api/
  100. //
  101. // See aws.Config documentation for more information on configuring SDK clients.
  102. // https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config
  103. //
  104. // See the AWS Security Token Service client STS for more
  105. // information on creating client for this service.
  106. // https://docs.aws.amazon.com/sdk-for-go/api/service/sts/#New
  107. package sts