1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
Hello,
What are the different data sources in other AWS accounts?
for eg. Redshift, Athena, RDS, Aurora flavors etc