Hologram brings AWS IAM Roles to developer laptops by exposing an EC2-like metadata service for temporary credentials.
Hologram is a tool that enables developers to use temporary AWS credentials on their local machines by emulating the EC2 instance metadata service. It eliminates the need to store AWS keys in source code or environment variables, improving security while maintaining convenience. The system allows development and production environments to use the same credential source, simplifying deployment and reducing the risk of credential leaks.
Developers and DevOps engineers working with AWS who need secure, temporary credentials for local development on non-EC2 machines, particularly in organizations using LDAP for authentication and requiring multi-account or role-based access.
Developers choose Hologram because it provides a seamless bridge between local development and AWS cloud security models, using the same credential workflow as EC2 instances without modifying application code. Its unique selling points include LDAP integration for SSH key authentication, support for role switching and multi-account aliases, and the ability to operate in a serverless mode using the AWS SDK default provider.
Easy, painless AWS credentials on developer laptops.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Removes the need to store AWS keys in source code or environment variables by providing temporary credentials via EC2 metadata service emulation, reducing security risks from credential leaks.
Works with Boto, AWS Java SDK, and GoAMZ without code changes, as SDKs automatically query the local endpoint at 169.254.169.254, ensuring consistency between development and production.
Authenticates users via SSH keys stored in LDAP, centralizing access control and eliminating password management, as noted in the README's prerequisites.
Includes a CLI for switching IAM roles and supports account aliases, making it easy to test different permissions across multiple AWS accounts without manual credential handling.
Requires building from source with Docker, deploying an EC2 instance with IAM permissions, and configuring LDAP, which the README admits involves multiple steps and dependencies.
Explicitly states that no Windows support is planned, limiting usability for mixed-OS environments and forcing alternatives for Windows developers.
Relies on ssh-agent running on workstations, with noted issues on OS X where developers may need to repeatedly add keys using 'ssh-add -K', adding maintenance overhead.