1回答
- 新しい順
- 投票が多い順
- コメントが多い順
1
You can consider many extra access control layers. But, as you know, each access control layer requires a corresponding trade-off (Human resources, extra system, management cost).
- Fine-grained IAM Policy Conditions
- Limit source IP, source VPC, source Account, or something else.
- Strengthen security for Assume Role(Trusted Identity) Policy for IAM Role.
- Limit source IP, source VPC, source Account, or something else.
- Use application-level AWS STS Tokens instead of EC2 Instance Profile
- With a solution for dynamic secret(short-live token) like HashiCorp Vault, you can use several small-scoped STS tokens. And just delete your EC2 Instance Profile.
- Limit access to the EC2 instance with Security Groups and NACLs.
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 1年前
- AWS公式更新しました 4年前
- AWS公式更新しました 1年前
Hello,
What are the different data sources in other AWS accounts?
for eg. Redshift, Athena, RDS, Aurora flavors etc