- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Access keys are long-term credentials for an IAM user or the AWS account ‘root’ user. You can use access keys to sign programmatic requests to the AWS CLI or AWS API (directly or using the AWS SDK).
Access keys are long-term credentials for an IAM user or the AWS account ‘root’ user. You can use access keys to sign programmatic requests to the AWS CLI or AWS API. One of the best ways to protect your account is to not allow users to have multiple access keys.
Perform the following to manage active keys (IAM user console access).
Using the IAM user and access key information provided, choose one access key that is less than 90 days old. This should be the only active key used by this IAM user to access AWS resources programmatically. Test your application(s) to make sure that the chosen access key is working.
Run the following command using the IAM user name and the non-operational access key IDs to deactivate the unnecessary key(s).
aws iam update-access-key
To confirm that the selected access key pair has been successfully deactivated run the list-access-keys audit command again for that IAM User.
aws iam list-access-key
The command output should expose the metadata for each access key associated with the IAM user. If the non-operational key pair(s) Status is set to inactive, the key has been successfully deactivated and the IAM user access configuration adheres now to this recommendation.