![]() This essentially allows your instance to burst without limits, and you'll be charged for bursting above your baseline. Protect your private key which you've already done.Įnsure your t2 instance is configured for unlimited. MFA and alerts which you've already done. AWS also allows you to choose "My IP" from the source IP drop down in the security group, so you can always use that (it'll do a similar query to or similar to find the public IP). It may change over time, so if you ever find you can't access your instance via SSH, go into the AWS console and update the IP address accordingly. ![]() Go to and grab the IP from there and allow that as the only thing allowed to access SSH. SSH should only be open to your IP and nothing else. By default, they're not created, so don't create them if you don't plan on using them and securing them properly. Essentially, with these 2 pieces of information, you can access the person's account and do anything with the CLI (up to the permissions allowed on that particular account). This is where a lot of breaches occur - people accidentally checking in this information to public source control repos and their account gets breached that way. If you don't know what ACCESS KEYS and SECRET KEYS are, don't ever generate them for your account. Made sure my private key is secure and not shown publiclyĪny suggestions or anything would help, or let me know i'm doing the right thing, Setup MFA on my root account and alerts I've only opened the necessary ports for teamspeak to work and the SSH Port (is it fine for this to be left open?) *Note: I don't care about the physical data on the instance, its just for hosting teamspeak and could get wiped anytime. What would be the best way to secure, i guess the ip or instance, from transferring a lot of Data as I don't want to be charged for it? I've seen posts about people getting their instances/accounts/w.e breached and getting charged because of the amount of Data used (I want to make sure this doesn't happen) ![]() I've been looking into security and stuff as I want to make sure bandwidth cannot be abused so that I don't exceed my monthly limit and get charged for it. ![]() I'm planning to use this 24/7 for my friends and I, which is a relatively small group (I understand if I go over I will be charged, but it would be relatively small, so it's fine). So I recently setup a teamspeak server on a EC2 Instance through AWS (i'm using the 12 month free trial). If you're posting a technical query, please include the following details, so that we can help you more efficiently:ĭoes this sidebar need an addition or correction? Tell us here public IP addresses or hostnames, account numbers, email addresses) before posting! ✻ Smokey says: join us on our journey to a sustainable future! Note: ensure to redact or obfuscate all confidential or identifying information (eg. News, articles and tools covering Amazon Web Services (AWS), including S3, EC2, SQS, RDS, DynamoDB, IAM, CloudFormation, AWS-CDK, Route 53, CloudFront, Lambda, VPC, Cloudwatch, Glacier and more. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |